Skip to main content
Claude Code has first-class support for remote MCP servers, so setup is one command - no config files to edit.

​
Prerequisites

  • Claude Code installed and signed in
  • A 2extract API key with the scopes your work needs - see Quick Start

​
Add the server

That registers the server for your user account, so it is available in every project. To scope it to one project instead, add --scope project - the entry lands in .mcp.json in the repository root.
With --scope project the key is written into a file that is usually committed. Either add .mcp.json to .gitignore, or keep the server at user scope.

​
Verify

Inside Claude Code, run:
2extract should appear as connected. Then ask something read-only:
What is my 2extract balance?
A number comes back. You are connected, and nothing was created or charged.

​
Managing the server

​
Troubleshooting

Run claude mcp list to confirm the entry exists. If it does but is not connecting, the URL is probably missing the /mcp path - the endpoint is https://mcp.2extract.com/mcp, not the bare host.
The key is missing, mistyped, or expired. Re-add the server with a fresh key:
That is a scope problem, not a connection problem. The key is missing the scope that tool needs - most often proxies:read on a key that only has proxies:write. See Overview.

​
Next steps

Usage Examples

Full sessions from request to connection string.

Prompts

Four slash commands that ship with the server.