Browse documentation
Claude Code
One command, and the eleven tools are in the session.
Add it
claude mcp add --transport http unlob https://api.unlob.com/mcp \
--header "x-api-key: ${UNLOB_API_KEY}"
Then check:
claude mcp list
You should see unlob connected. Inside a session, /mcp shows the server and its tools.
Scope
claude mcp add takes --scope:
| Scope | Stored in | Use it for |
|---|---|---|
local (default) | Your user settings, this project only | Trying it out |
user | Your user settings, every project | Your own machine |
project | .mcp.json in the repository | Sharing with a team |
For a team, project scope with the key from the environment:
claude mcp add --transport http --scope project unlob https://api.unlob.com/mcp \
--header "x-api-key: ${UNLOB_API_KEY}"
That writes .mcp.json, which is meant to be committed — so make sure the header
interpolates an environment variable rather than baking in a literal key. Everyone on the
team then needs UNLOB_API_KEY in their own environment.
By hand
.mcp.json in the project root:
{
"mcpServers": {
"unlob": {
"type": "http",
"url": "https://api.unlob.com/mcp",
"headers": { "x-api-key": "${UNLOB_API_KEY}" }
}
}
}
Using it
Just ask. Claude will reach for the tools when the question needs them:
Find the three most independently corroborated accounts of the Acme acquisition, and tell me which single source everything else is echoing.
That is one web_search with min_independent_sources, one corroborate, and a read —
rather than a page of links you then have to triage.
Worth putting in your CLAUDE.md if you use this a lot:
When researching with unlob:
- Use `assemble_context` for "what should I know about X"; `web_search` for
"find the page that says Y".
- Run `corroborate` before stating anything as established fact.
- If a search returns `partial: true`, the answer is incomplete — say so, or retry.
Removing it
claude mcp remove unlob
If it does not connect
claude mcp list # is it listed, and does it say connected?
Then the one curl command that says which step failed. The usual
causes are a key that has not propagated yet (wait a minute, retry) and a shell that did
not expand ${UNLOB_API_KEY} because it was not exported.
Next
- MCP tools — what the eleven do
- Tool use, directly — the same tools through the Messages API
- Troubleshooting