mcp.swiss.software │ JSON-RPC 2.0 over Streamable HTTP │ Bearer auth │ protocol: 2024-11-05 │ uptime: live

$ swiss --help ask

support agent in your IDE.

Plug Swiss Software's docs-grounded support agent into Claude Desktop, Cursor, Continue, Zed, or any other MCP-aware AI tool. Your license key authenticates against https://mcp.swiss.software; once connected, your AI can call ask to get answers cited to the actual plugin documentation, or browse the docs as MCP resources.

Building plugins? The same MCP server hosts review_pr for grounded code review → /mcp/review

endpoint & auth

URLhttps://mcp.swiss.software

TransportStreamable HTTP (single endpoint, JSON-RPC 2.0)

AuthBearer token in Authorization header — the token is your license key

ProtocolMCP 2024-11-05

Your keyYOUR-LICENSE-KEY

client configs

claude desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Create the file if it doesn't exist:

jsonclaude_desktop_config.json

{
  "mcpServers": {
    "swiss-support": {
      "transport": "streamable-http",
      "url": "https://mcp.swiss.software",
      "headers": {
        "Authorization": "Bearer YOUR-LICENSE-KEY"
      }
    }
  }
}

Restart Claude Desktop. A "swiss-support" indicator appears once connected.

cursor

Settings → MCP → Add server, or edit ~/.cursor/mcp.json:

json.cursor/mcp.json

{
  "mcpServers": {
    "swiss-support": {
      "url": "https://mcp.swiss.software",
      "headers": { "Authorization": "Bearer YOUR-LICENSE-KEY" }
    }
  }
}

continue (vscode / jetbrains)

yaml~/.continue/config.yaml

mcpServers:
  - name: swiss-support
    url: https://mcp.swiss.software
    headers:
      Authorization: Bearer YOUR-LICENSE-KEY

zed

json~/.config/zed/settings.json

"context_servers": {
  "swiss-support": {
    "command": {
      "path": "npx",
      "args": ["-y", "@modelcontextprotocol/server-fetch-bridge", "https://mcp.swiss.software"],
      "env": { "MCP_AUTH": "Bearer YOUR-LICENSE-KEY" }
    }
  }
}

Zed currently uses stdio MCP transport, so it goes through a small bridge. Most users prefer Claude Desktop or Cursor for direct HTTP support.

raw json-rpc (curl)

For scripts, CI, or just sanity-checking:

bashtest.sh

# list available tools
curl -sS -X POST https://mcp.swiss.software/ \
  -H "Authorization: Bearer YOUR-LICENSE-KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

# ask a question
curl -sS -X POST https://mcp.swiss.software/ \
  -H "Authorization: Bearer YOUR-LICENSE-KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{
        "name":"ask",
        "arguments":{"question":"How do I configure the API key?"}
     }}'

once connected — what your AI can do

tools

ask(question, plugin_slug?, locale?) — get a docs-grounded answer with source citation. Counts as 1 question against monthly quota.
list_plugins() — see which plugins your license covers and your current usage.
review_pr(pr, focus?, post?) — code review for plugin authors. setup →

resources

swiss-support://<plugin_slug>/<file>.md — every documentation file is browseable as an MCP resource. Drag-and-drop into chat to attach as context, or reference by URI.

troubleshooting

"Authentication required" — check the Bearer token spelling. License keys are SW-XXXX-XXXX-XXXX-XXXX, no spaces.

"Quota exceeded" — your monthly question allowance is used up. Resets on the 1st. Check usage with list_plugins.

Tool calls hang > 30s — first call after a cold start can take 5–10s while the prompt cache warms. Subsequent calls in the same plugin are typically <2s.