Skip to content

Zed SAP MCP Server coingecko_getTokenInfo

How to: Zed SAP MCP Server coingecko_getTokenInfo

client:Zed transport:streamable-http tool:coingecko_getTokenInfo

Add SAP MCP Server to Zed

  1. 01

    Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.

{
  "context_servers": {
    "sap-mcp": {
      "url": "https://mcp.sap.oobeprotocol.ai/mcp"
    }
  }
}
  1. 02

    Save the file and restart Zed.

  2. 03

    Ask for something coingecko_getTokenInfo does. Zed lists the server's tools on connect and calls coingecko_getTokenInfo itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that SAP MCP Server's identifier in your config matches the one above exactly.

Merge this into your existing settings object — do not replace the file. Zed docs

Set these first

SAP MCP Server will not start until these are set, so coingecko_getTokenInfo never becomes available.

  • SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE
  • SAP_LOG_LEVEL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.