anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-23 10:45:33 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #2289] fix: mcp client name #10256

New Issue
Closed
opened 2026-02-16 18:14:52 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:14:52 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/2289

State: closed
Merged: Yes

Currently, Opencode uses the MCP config server name as the MCP clientInfo.name, which prevents MCP servers from easily identifying that the client is actually Opencode. This fix changes the clientInfo.name to a hardcoded value: "opencode". This ensures the Opencode MCP client is clearly identifiable by MCP servers, allowing them to adapt the features exposed based on supported specification features.

We are working on a package to address this, as the protocol does not support it yet. We would like to add Opencode, but without this change, we cannot: https://github.com/apify/mcp-client-capabilities

For example, if you configure opencode.json like this, the clientInfo.name in the MCP initialize request will be "testing-client" instead of a consistent identifier such as "opencode". Since each MCP client supports a different feature set, this makes it impossible to reliably identify Opencode.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "testing-client": {
      "type": "remote",
      "url": "http://localhost:3001",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer MY_API_KEY"
      }
    }
  }
}

MCP initialize request with this config, which cannot be easily identified as Opencode:

{"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"testing-client","version":"1.0.0"}},"jsonrpc":"2.0","id":0}

MCP initialize request with this config patched, now clearly identifiable by the "opencode" client name:

{"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"opencode","version":"1.0.0"}},"jsonrpc":"2.0","id":0}
**Original Pull Request:** https://github.com/anomalyco/opencode/pull/2289 **State:** closed **Merged:** Yes --- Currently, Opencode uses the MCP config server name as the MCP `clientInfo.name`, which prevents MCP servers from easily identifying that the client is actually Opencode. This fix changes the `clientInfo.name` to a hardcoded value: "opencode". This ensures the Opencode MCP client is clearly identifiable by MCP servers, allowing them to adapt the features exposed based on supported specification features. We are working on a package to address this, as the protocol does not support it yet. We would like to add Opencode, but without this change, we cannot: https://github.com/apify/mcp-client-capabilities For example, if you configure `opencode.json` like this, the `clientInfo.name` in the [MCP initialize request](https://modelcontextprotocol.io/specification/2025-06-18/schema#initializerequest) will be "testing-client" instead of a consistent identifier such as "opencode". Since each MCP client supports a different feature set, this makes it impossible to reliably identify Opencode. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "testing-client": { "type": "remote", "url": "http://localhost:3001", "enabled": true, "headers": { "Authorization": "Bearer MY_API_KEY" } } } } ``` MCP initialize request with this config, which cannot be easily identified as Opencode: ```text {"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"testing-client","version":"1.0.0"}},"jsonrpc":"2.0","id":0} ``` MCP initialize request with this config **patched**, now clearly identifiable by the "opencode" client name: ```text {"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"opencode","version":"1.0.0"}},"jsonrpc":"2.0","id":0} ```
yindo added the pull-request label 2026-02-16 18:14:52 -05:00
yindo closed this issue 2026-02-16 18:14:52 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#10256
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?