Connect your client

Any MCP client can connect if it supports remote servers over Streamable HTTP and lets you set a custom Authorization header. Clients that only offer an OAuth sign-in can't connect yet.

Every client needs the same two settings:

The connection token is your API key, a colon, then your API secret. See Account setup.

Claude Code

claude mcp add --transport http wellat https://mcp.mywellat.com/mcp \
  --header "Authorization: Bearer <connection token>"

Check it with /mcp inside a session. Remove it with claude mcp remove wellat.

Cursor

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "wellat": {
      "url": "https://mcp.mywellat.com/mcp",
      "headers": { "Authorization": "Bearer <connection token>" }
    }
  }
}

Keep a file that holds the token out of source control.

VS Code

Add the server to .vscode/mcp.json. The inputs entry makes VS Code ask for the token when the server starts, so the file itself holds no secret:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "wellat-token",
      "description": "Wellat connection token",
      "password": true
    }
  ],
  "servers": {
    "wellat": {
      "type": "http",
      "url": "https://mcp.mywellat.com/mcp",
      "headers": { "Authorization": "Bearer ${input:wellat-token}" }
    }
  }
}

MCP Inspector

To test the connection and call tools by hand:

npx @modelcontextprotocol/inspector

Choose Streamable HTTP, enter the URL, add the Authorization header, then connect and list the tools.

Connection details