Connecting VS Code

Add the Subscriby MCP server to VS Code, by signing in or with a personal access token.

Requirements

VS Code 1.99 or newer, with MCP servers enabled (chat.mcp.enabled), or the Claude Code extension.
A Subscriby account. VS Code signs you in; a personal access token is only needed when you want a connection narrower than your own reach.

Run MCP: Add Server from the command palette, choose HTTP, and enter https://mcp.subscriby.net with the name subscriby. VS Code writes it to .vscode/mcp.json (workspace) or your user profile:

{
  "servers": {
    "subscriby": {
      "type": "http",
      "url": "https://mcp.subscriby.net"
    }
  }
}

When the server starts, VS Code asks to authenticate with Subscriby and opens your browser. Sign in if you are not already, read the consent screen and press Authorize; VS Code stores the connection in its secret storage, never in the config file.

Using the Claude Code extension instead? Open its terminal and run claude mcp add --transport http subscriby https://mcp.subscriby.net, then /mcp → Authenticate.

Use it

Open the chat panel in agent mode and prefix prompts with "using subscriby" when you want MCP calls to run. Example:

Using subscriby, list my five most recent subscribers on project "Research Premium".

The panel shows each tool invocation inline with an approve / deny prompt. Approve per call or pin auto-approve on the subscriby namespace; tools that change or delete data are marked so the prompt always appears for them.

Using a personal access token instead

Mint a token in Settings → API Tokens with the abilities you want the assistant to exercise and send it as a header; VS Code then skips the sign-in:

{
  "servers": {
    "subscriby": {
      "type": "http",
      "url": "https://mcp.subscriby.net",
      "headers": {
        "Authorization": "Bearer sbt_live_YOUR_TOKEN"
      }
    }
  }
}

Prefer an input variable over a literal token in a workspace file that is committed.

Workspace vs. user scope

Put the config in the workspace .vscode/mcp.json if the Subscriby access should only apply to a specific repo. Keep it in your user profile if every VS Code window should have access.

Troubleshooting

Never asked to sign in: the URL must be exactly https://mcp.subscriby.net; check View → Output → MCP for the server's log.
Server fails to connect: the same output panel shows the handshake; a 401 there means the stored connection lapsed — run MCP: Reset Trust or remove and re-add the server to sign in again.
Tool 403s with a personal access token: the error envelope names the missing ability — mint a new token with it.