mcp-setup

Configure OpenCode agents with external MCP servers via opencode mcp add.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kamelmh/opencode --skill mcp-setup-kamelmh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-setup
Source: https://github.com/kamelmh/opencode/tree/main/skills/mcp-setup
Command: npx skills add https://github.com/kamelmh/opencode --skill mcp-setup-kamelmh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenCode agents quickly hit limits when you rely only on built-in tools, so MCP Setup solves the problem of extending agent capabilities by configuring external Model Context Protocol (MCP) servers.

Core Features & Use Cases

  • Select and configure MCP servers: Choose from common providers like Context7, Exa Web Search, Filesystem, and GitHub, or add a custom MCP server.
  • Collect required credentials and permissions: Prompts for an Exa API key, a GitHub personal access token, and filesystem directory access as needed.
  • Add servers via OpenCode CLI with correct transport: Uses the opencode mcp add workflow (including stdio or HTTP transport) and supports merging into settings.json automatically.

Use case: Configure Exa for stronger web search and Filesystem for broader tool access, then verify everything with opencode mcp list so all agents can use the added capabilities.

Quick Start

Run mcp-setup and choose the MCP servers you want (for example, Context7, Exa, Filesystem, or GitHub) when prompted.

Frequently Asked Questions about mcp-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure MCP servers for OpenCode agents?

To configure MCP servers for OpenCode agents, run mcp-setup and select providers like Context7, Exa, Filesystem, or GitHub. It uses opencode mcp add to set up each server with the proper transport and credentials, then validates the installation via opencode mcp list.

What is the Model Context Protocol used for in agent tooling?

The Model Context Protocol expands agent tool availability beyond built-in capabilities. It connects OpenCode agents to external servers for enhanced web search, filesystem access, and GitHub integrations, allowing agents to interact with external APIs and data sources.

How do I add an Exa web search API key to my CLI configuration?

To add an Exa web search API key to your CLI configuration, run mcp-setup and select the Exa provider. The setup prompts for your Exa API key, applies the correct transport via opencode mcp add, and merges the required credentials into settings.json automatically.

Does MCP setup support both stdio and HTTP transport?

Yes, MCP setup supports both stdio and HTTP transport. When you use opencode mcp add to configure a server, the workflow applies the correct transport type required by the specific MCP server and merges the configuration into settings.json automatically.

Can I add multiple MCP servers to expand filesystem access and GitHub integration?

Yes, you can add multiple MCP servers to expand filesystem access and GitHub integration. Run mcp-setup to select and configure multiple providers, supplying a GitHub personal access token and filesystem directories as needed, then verify all added capabilities with opencode mcp list.

Why does my OpenCode agent hit limits with only built-in tools?

OpenCode agents hit limits with only built-in tools because native capabilities are restricted. Configuring external Model Context Protocol servers solves this by connecting agents to additional web search, filesystem, and GitHub tools via the opencode mcp add workflow.