2extract Developer Documentation

Every client differs in where it keeps its configuration. None of them differ in what the configuration has to contain.

The three values


URL	`https://mcp.2extract.com/mcp`
Transport	Streamable HTTP
Header	`Authorization: Bearer 2xt_YOUR_API_KEY`

Wherever your client asks for a remote or custom MCP server, those go in. If it offers a choice of transports, pick Streamable HTTP - not stdio, and not the deprecated HTTP+SSE.

Keep the /mcp path. The bare host https://mcp.2extract.com serves a web page, not the protocol.

The two shapes you will meet

Most clients use one of these. If yours is not documented here, try the first.

{
  "mcpServers": {
    "2extract": {
      "type": "http",
      "url": "https://mcp.2extract.com/mcp",
      "headers": {
        "Authorization": "Bearer 2xt_YOUR_API_KEY"
      }
    }
  }
}

{
  "servers": {
    "2extract": {
      "type": "http",
      "url": "https://mcp.2extract.com/mcp",
      "headers": {
        "Authorization": "Bearer 2xt_YOUR_API_KEY"
      }
    }
  }
}

Variations you may run into: serverUrl instead of url, streamableHttp instead of http, headers as a list of strings rather than an object. The values stay the same.

Clients that only speak stdio

Some older clients launch local processes and cannot reach a remote server. Bridge to it with mcp-remote, which runs locally and forwards to us:

{
  "mcpServers": {
    "2extract": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.2extract.com/mcp",
        "--header",
        "Authorization: Bearer 2xt_YOUR_API_KEY"
      ]
    }
  }
}

Requires Node.js. Use the direct HTTP form whenever your client supports it.

Testing without a client

Useful when you want to know whether the problem is us or your editor. Open a session:

curl -i -X POST https://mcp.2extract.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer 2xt_YOUR_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-06-18",
      "capabilities": {},
      "clientInfo": { "name": "curl", "version": "1" }
    }
  }'

A healthy server replies 200 with an mcp-session-id response header and the server’s capabilities in the body.

initialize succeeds even without a valid key - authentication is checked when a tool actually runs. To test the key itself, call a tool: pass the returned mcp-session-id back as a header, send notifications/initialized, then call tools/call with getAccountBalance. A bad key returns error_code: unauthorized.

Checklist when it will not connect

Is the path there?

https://mcp.2extract.com/mcp, not the bare host.

Is the transport right?

Streamable HTTP. If the client only lists SSE, it is likely too old for this server.

Is the header exactly right?

Bearer, one space, then the key. Watch for a trailing newline from copy-paste.

Did the client reload?

Most need a restart, not just a new conversation.

Does the key have the scopes?

If some tools work and others do not, it is scopes - not the connection. See Overview.

Introduction

MCP Server

MCP Clients

Use Cases

For AI Agents

Other Clients

The three values

The two shapes you will meet

Clients that only speak stdio

Testing without a client

Checklist when it will not connect

Next steps

FAQ

Tools

​The three values

​The two shapes you will meet

​Clients that only speak stdio

​Testing without a client

​Checklist when it will not connect

​Next steps

FAQ

Tools

The three values

The two shapes you will meet

Clients that only speak stdio

Testing without a client

Checklist when it will not connect

Next steps