Quickstart

Preview. You will mint a key, point one client at the server, and watch a model call a tool against your own workspace.

1. Mint a key with `mcp:connect`

In the dashboard, Developers → API keys → Create key. The key is a workspace credential with the tgcc_ prefix, and it is shown once.

scope

required

Reaching the transport at all. Without it, POST /mcp is 403.

scope

Each tool demands its own scope on top — agents:read to list agents, documents:create to upload one, and so on.

mcp:connect on its own authorises nothing. A key holding only that scope connects and lists every tool — and calls none of them. That is deliberate: connecting is one decision, and what a model may then do with your workspace is another. Grant the per-tool scopes you actually intend, and no more.

2. Check the endpoint answers

The transport is JSON-RPC 2.0 over POST to one URL. initialize needs no arguments worth writing down, and it is what every shipping MCP client sends today:

curl https://api.impellabs.tech/mcp \
  -H "Authorization: Bearer tgcc_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-06-18",
      "capabilities": {},
      "clientInfo": {"name": "curl", "version": "1.0"}
    }
  }'

import httpx

r = httpx.post(
    "https://api.impellabs.tech/mcp",
    headers={
        "Authorization": "Bearer tgcc_xxxxxxxxxxxx",
        "MCP-Protocol-Version": "2025-06-18",
    },
    json={
        "jsonrpc": "2.0",
        "id": 1,
        "method": "initialize",
        "params": {
            "protocolVersion": "2025-06-18",
            "capabilities": {},
            "clientInfo": {"name": "probe", "version": "1.0"},
        },
    },
)
print(r.json()["result"]["protocolVersion"])   # 2025-06-18

const r = await fetch("https://api.impellabs.tech/mcp", {
  method: "POST",
  headers: {
    "Authorization": "Bearer tgcc_xxxxxxxxxxxx",
    "Content-Type": "application/json",
    "MCP-Protocol-Version": "2025-06-18",
  },
  body: JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "initialize",
    params: {
      protocolVersion: "2025-06-18",
      capabilities: {},
      clientInfo: { name: "probe", version: "1.0" },
    },
  }),
});
console.log((await r.json()).result.protocolVersion);   // 2025-06-18

A 200 carrying "protocolVersion": "2025-06-18" means the credential is good and the server is reachable. A 401 means the key was not recognised; a 403 means it lacks mcp:connect. Both are covered in Authentication.

If your client speaks `2026-07-28`

There is no handshake to run — that revision removed it. server/discover answers the same question, and the request declares its own revision instead of agreeing one:

curl https://api.impellabs.tech/mcp \
  -H "Authorization: Bearer tgcc_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "MCP-Protocol-Version: 2026-07-28" \
  -H "Mcp-Method: server/discover" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "server/discover",
    "params": {
      "_meta": {
        "io.modelcontextprotocol/protocolVersion": "2026-07-28",
        "io.modelcontextprotocol/clientCapabilities": {}
      }
    }
  }'

import httpx

VERSION = "2026-07-28"

r = httpx.post(
    "https://api.impellabs.tech/mcp",
    headers={
        "Authorization": "Bearer tgcc_xxxxxxxxxxxx",
        "MCP-Protocol-Version": VERSION,
        # Mirrored so a gateway can route without parsing the body. It is
        # checked against the body, and a mismatch is -32020.
        "Mcp-Method": "server/discover",
    },
    json={
        "jsonrpc": "2.0",
        "id": 1,
        "method": "server/discover",
        "params": {
            "_meta": {
                "io.modelcontextprotocol/protocolVersion": VERSION,
                "io.modelcontextprotocol/clientCapabilities": {},
            }
        },
    },
)
print(r.json()["result"]["supportedVersions"])   # every revision we answer on

You do not need this to connect. The 2025-06-18 calls above are the default path and will stay one — the era is chosen by the MCP-Protocol-Version header alone, and an absent header still means 2025-03-26. Protocol revisions covers what a modern client must send on every request, and the error codes it gets for leaving a piece out.

3. See what the key may call

tools/list is the honest answer to “what exists” — it is filtered by nothing, so a key holding only mcp:connect still sees the whole catalogue. The registry is curated and still growing, so this call, not a table in these docs, is what is current for your connection.

curl https://api.impellabs.tech/mcp \
  -H "Authorization: Bearer tgcc_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -d '{"jsonrpc": "2.0", "id": 2, "method": "tools/list"}'

curl https://api.impellabs.tech/mcp \
  -H "Authorization: Bearer tgcc_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -H "MCP-Protocol-Version: 2026-07-28" \
  -H "Mcp-Method: tools/list" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/list",
    "params": {
      "_meta": {
        "io.modelcontextprotocol/protocolVersion": "2026-07-28",
        "io.modelcontextprotocol/clientCapabilities": {}
      }
    }
  }'

The modern result carries the same tools array plus ttlMs and cacheScope, the freshness hints that revision requires — worth honouring, because this server declares listChanged: false and can never tell you the catalogue moved.

4. Point a client at it

Claude

A custom connector on claude.ai or Claude Desktop.

Claude Code

claude mcp add, and a .mcp.json the team shares.

ChatGPT

Connector in the chat UI, or the Responses API mcp tool.

Grok

A custom connector, or the xAI API’s remote MCP tool.

Cursor

One mcp.json entry.

VS Code

One .vscode/mcp.json entry, agent mode on.

Something else?

Windsurf, Zed, Cline, Continue, Goose, Junie, LibreChat, Warp and n8n all connect, and so does anything built on an MCP SDK. Nothing here checks which client is calling.

5. Ask for something

List the agents in my workspace.

The model calls a read tool, gets a JSON payload, and reads it back to you. Then try something that spends:

Upload this contract and pull out the parties, the term and the notice period.

That one uploads a document, waits for it to parse, starts an extraction and polls a job. It also costs credits — see Credits. The scopes the set can ever need are advertised separately, and need no credential at all:

curl -s https://api.impellabs.tech/.well-known/oauth-protected-resource \
  | jq '.scopes_supported'

Four kinds of work never answer inline. Extractions, reports, knowledge ingestions and jobs all hand back a job id instead of a result, and the model has to poll. A client that reports “started” and stops is behaving correctly; ask it to check the job. Tools explains why.

Get started

Connect a client

Reference

1. Mint a key with `mcp:connect`

2. Check the endpoint answers

If your client speaks `2026-07-28`

3. See what the key may call

4. Point a client at it

Claude

Claude Code

ChatGPT

Grok

Cursor

VS Code

Something else?

5. Ask for something

​1. Mint a key with mcp:connect

​2. Check the endpoint answers

​If your client speaks 2026-07-28

​3. See what the key may call

​4. Point a client at it

Claude

Claude Code

ChatGPT

Grok

Cursor

VS Code

Something else?

​5. Ask for something

1. Mint a key with `mcp:connect`

2. Check the endpoint answers

If your client speaks `2026-07-28`

3. See what the key may call

4. Point a client at it

5. Ask for something