OpenCode

OpenCode uses a remote MCP server entry with the hosted Zephex URL only. There is no Bearer header in the config: OpenCode discovers the OAuth-protected resource, opens the browser flow, and stores the token automatically.

OVERVIEW

OpenCode is an open-source terminal AI coding agent built by the SST team with 140K+ GitHub stars and 6.5M monthly active developers. It supports 75+ AI model providers and uses the standard MCP remote server protocol for tool integrations. Zephex connects via the `type: remote` SSE transport with OAuth handled automatically through Dynamic Client Registration, so the config only contains the URL.

CONFIG FILE LOCATION

~/.config/opencode/opencode.json. This is a global config. There is no per-project config file for OpenCode MCP servers.

PREREQUISITES

OpenCode installed from https://opencode.ai or via `npm install -g opencode`.
A Zephex account at zephex.dev/signup.
No API key needed. Authentication is handled through the OAuth browser flow.

CONFIG

Paste the JSON exactly as shown. Keep the server name as `zephex`. The config contains only the URL because OpenCode expects OAuth discovery instead of a pasted Bearer key.

Do not add an Authorization header to this config. When OpenCode connects without one, it hits Zephex's `/.well-known/oauth-protected-resource` metadata, opens the browser sign-in flow, and stores the token automatically.

~/.config/opencode/opencode.json

{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "zephex": {      "type": "remote",      "url": "https://zephex.dev/mcp"    }  }}

AUTH

Save ~/.config/opencode/opencode.json.
Start OpenCode by running `opencode` in your terminal.
Zephex returns a 401 on the first connection.
OpenCode automatically detects that response and initiates the OAuth flow.
A browser window opens. Log in to your Zephex account.
After login, OpenCode stores the token and reconnects.
If the browser flow does not auto-trigger, run `opencode mcp auth zephex`.

VERIFY

Verify the server from inside an OpenCode session before relying on it in normal prompts.

Run `/mcp` inside OpenCode.
You should see "zephex" listed as connected.
Ask OpenCode: "what tools are available from zephex?" You should see all 10 tools listed.

COMMON ISSUES

"type: remote only supports SSE"

This is expected. OpenCode remote MCP uses SSE transport. Zephex serves both SSE and Streamable HTTP from the same `/mcp` endpoint, so you do not need to change the config.

Auth browser window did not open

Run `opencode mcp auth zephex` manually to trigger the OAuth browser flow.

Connected, but requests fail with API key limit or stale auth errors

OpenCode may still be using an old stored Bearer credential instead of the OAuth token for Zephex. Clear the saved Zephex MCP auth in OpenCode, make sure your config does not include an Authorization header or API key, then run `opencode mcp auth zephex` again to force a fresh OAuth login.

"invalid_client" error

Dynamic Client Registration usually failed. Update to the latest OpenCode version and try again. Older builds may not support DCR correctly.

Token expired after restart

Re-run `opencode mcp auth zephex` to refresh the stored token.

If the editor still does not connect, return to Quickstart or check Connection Issues.