Custom MCP server
Connect any remote MCP server by its URL, open or protected by a bearer token or OAuth, so agents can use its tools.
Connect it with: MCP. Custom MCP server's own documentation: https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization.
What agents can do
Connect Custom MCP server so the agents working your tasks can reach it. With it connected, they can:
- Use every tool the MCP server exposes, in the projects you link the connection to.
- Reach a service through its own hosted MCP server even when Jaah has no built-in card for it.
- Share one server definition with the whole organization, so each member connects with their own token or sign-in.
Before you start
- The server's MCP URL, from its provider's documentation.
- If the server is protected: a bearer token, or an account to sign in with when the server supports MCP OAuth.
- To define a server the whole organization can reuse: an Org Owner or Admin. Open Secrets, select Add secret, pick the Custom category, then Add custom on the Custom MCP server card. Give it a name, the server URL, the transport and how it authenticates (none, bearer token or OAuth). Once saved every member sees it as its own card in the Custom category.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Custom MCP server
Jaah connects to Custom MCP server with an access token, not with a sign-in button.
Connect with an API key
Find each value first:
- Server URL: The server's MCP endpoint as its provider documents it, usually ending in /mcp (or /sse for an older server). It must be https:// and reachable from the internet.
- Transport (optional): streamable_http for current MCP servers, sse for older ones that publish an /sse endpoint. Leave it blank for streamable_http.
- Bearer token (optional): For a server that takes an API key or token: paste it here. Leave it blank for an open server, or to press Connect and sign in with OAuth.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Custom MCP server card.
- Name the secret and choose who can use it.
- Fill in Server URL, Transport, Bearer token.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Custom MCP server with an access token, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Custom MCP server with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: url, transport, bearer_token.
Tell the agent in your task description which secret to use, for example “use the Custom MCP server secret org/custom-mcp”.
Link Custom MCP server's MCP server to a project
Custom MCP server also runs an MCP server, which gives agents ready-made Custom MCP server tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:
- Open the project and its MCP tab.
- Select Link, pick the Custom MCP server secret, and confirm.
- New tasks on the project start with the Custom MCP server tools. Tasks already running keep the tools they started with.
Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Custom MCP server once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Custom MCP server's side too, revoke the token at Custom MCP server.
Limitations
- Only https:// servers on the public internet can be connected; a server inside a private network is not reachable from Jaah's control plane.
- A connection reaches a task only in the projects you link it to.
- OAuth works with servers that publish MCP authorization metadata; a server that does not needs a bearer token instead.
- Agents can do only what the connected Custom MCP server account allows.
Troubleshooting
The Test says the server rejected the token (401)
The bearer token is wrong or revoked, or the server expects OAuth. Paste a new token, or clear it and press Connect.
The Test cannot complete the MCP handshake
Check the URL and the transport: an older server publishes /sse and needs transport sse; a current one takes streamable_http on /mcp.
Saving says the Server URL is refused
The host resolves to a private, loopback or cloud-metadata address, or it is not https. Use the server's public https address.
Still stuck? Select Test and read the result: it names the value Custom MCP server refused and the status it answered.
FAQ
Does Jaah run the MCP server?
No. Jaah connects to a server someone else hosts; agents call its tools over the network with your connection.
Can another organization see our custom MCP servers?
No. A custom MCP server belongs to the organization that defined it.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Custom MCP server account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.