Claude Code

Claude Code supports both custom authorization headers and OAuth for remote Streamable HTTP MCP servers. A Bearer token is recommended for ongoing use.

Recommended: Bearer token

Create or copy your Plushcap API key from your account, export it in the environment where Claude Code runs, and add this server to .mcp.json:

export PLUSHCAP_API_KEY="your-api-key-here"

{
  "mcpServers": {
    "plushcap": {
      "type": "http",
      "url": "https://mcp.plushcap.com/mcp",
      "headers": {
        "Authorization": "Bearer ${PLUSHCAP_API_KEY}"
      }
    }
  }
}

The configuration contains only an environment-variable reference. Do not commit the key itself. Claude Code supports local, project, and user scopes; choose user scope when you want Plushcap available across projects.

OAuth quick start

Add the remote server:

claude mcp add --transport http --scope user plushcap https://mcp.plushcap.com/mcp

Start Claude Code, run /mcp, select Plushcap, and complete the browser authorization. Plushcap advertises offline_access, so Claude Code can refresh OAuth tokens automatically, although reauthorization can eventually be needed.

Verify

claude mcp list

Then run /mcp and confirm that Plushcap has connected tools. Try:

Use Plushcap to list trend reports and summarize the newest one.

For 401 Unauthorized, confirm that the environment variable is set in the shell that launched Claude Code and that the API key is still active.

Official documentation

• Claude Code MCP documentation

Last verified: July 29, 2026.