Skip to main content
Context’s MCP server is a remote server at:
It speaks Streamable HTTP and answers each request with JSON. Tools act on the workspaces of the account you signed in with, or that owns the API key.

Authentication

There are two ways in. Both send Authorization: Bearer … with every request.

Sign in with Jabrod

Add the server without a key. The first time your client connects, it opens Jabrod’s sign-in page, auth.jabrod.com, in your browser: sign in, and allow the app to use your account. The token it gets works only for this server. In Claude Code:
Then run /mcp in Claude Code, choose jabrod-context, and sign in. This needs a client that supports MCP authorization. Sign in with Jabrod explains the flow.

API key

For clients that can’t sign in, make a personal API key at jabrod.com/app/keys. It starts with jbd_sk_ and is shown once. Send it with every request:
Make one key per app, so you can revoke one without breaking the others. A revoked key stops working at once.

Client configuration with an API key

Tools

Notes

  • Adding sources is asynchronous. add_document returns at once with status: "queued". Call list_documents until the source is ready or failed.
  • search writes no answer. It returns the passages retrieval finds, so your own model can use them.
  • ask can refuse. When the sources don’t cover the question, refused is true and the answer says so. See Refusals.
  • Questions asked over MCP are saved with the workspace, but are not offered as Evals test cases.

Errors

A problem you can fix comes back as a tool result with isError: true and a sentence saying what to do, such as “That workspace wasn’t found.” Requests without a valid key get HTTP 401.