opencode-mcplisted

Use this skill when adding Model Context Protocol (MCP) servers to OpenCode, configuring local or remote MCP servers, setting up OAuth authentication for MCP, managing MCP server permissions per agent, or troubleshooting MCP connection issues. Covers local/remote server types, OAuth flows, tool management, overriding remote defaults, and common MCP server examples.
Timmy6942025/opencode-builder-skill · ★ 1 · AI & Automation · score 72

Install: claude install-skill Timmy6942025/opencode-builder-skill

# OpenCode MCP Servers > **📚 Official Docs:** For the latest information, always refer to the official documentation: > [https://opencode.ai/docs/mcp-servers/](https://opencode.ai/docs/mcp-servers/) Add local and remote MCP tools to OpenCode using the *Model Context Protocol* (MCP). MCP is a standard protocol that lets you connect external tool servers to AI applications. OpenCode supports both local servers (child processes) and remote servers (HTTP). Once added, MCP tools are automatically available to the LLM alongside OpenCode's built-in tools. --- ## Context Caveat When you use an MCP server, it adds tokens to the context. Every tool the MCP server exposes is described in the context window, which consumes tokens. This can quickly add up if you have a lot of tools from multiple MCP servers. Be careful with which MCP servers you enable. - Certain MCP servers, like the GitHub MCP server, tend to add a lot of tokens and can easily exceed the context limit. - Each additional MCP server multiplies the tool definitions injected into context. - Monitor your context window usage and be selective about which servers you enable. --- ## Enable / Disable MCP servers are defined in your [OpenCode Config](https://opencode.ai/docs/config/) (`opencode.json` or `opencode.jsonc`) under the `mcp` key. Each server gets a unique name used to reference it in prompts and tool management. ```jsonc { "$schema": "https://opencode.ai/config.json", "mcp": { "name-of-mcp-server":