Ref
Search public and your team's private technical documentation through the Ref MCP server.
Connect it with: MCP. Ref's own documentation: https://docs.ref.tools/install.
What agents can do
Connect Ref so the agents working your tasks can reach it. With it connected, they can:
- Search documentation for an API, library or service before writing code against it.
- Read the exact documentation page a search found, trimmed to what the task needs.
- Search your team's private documentation that was added to Ref.
Before you start
- A Ref account (https://ref.tools); its plan decides how many searches agents may run.
- An Org Owner or Admin adds the secret and selects Connect to sign in to Ref once, then links it on each project's MCP tab.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Ref
Ref's MCP server signs you in itself, so connecting needs no key and no app of your own.
- In Jaah, open Secrets and select New.
- Search for Ref and select its card.
- Name the secret and choose who can use it (see Who can use it).
- Select Connect Ref, sign in to Ref in the window that opens, and approve the access it lists.
- You land back in Jaah on the new secret. Then link it to the projects whose agents should use it (see Use it in an agent session).
Connect with an API key
Ref has no API key option in Jaah: connect with the sign-in above.
Use your own OAuth app
Not needed: Ref's MCP server registers Jaah itself when you connect, so there is no app of your own to create.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Ref 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 signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
Tell the agent in your task description which secret to use, for example “use the Ref secret org/ref”.
Link Ref's MCP server to a project
Ref also runs an MCP server, which gives agents ready-made Ref 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 Ref secret, and confirm.
- New tasks on the project start with the Ref 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:
- Reconnect: when Ref ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Ref's side too, revoke Jaah in Ref's settings.
Limitations
- Ref counts every search against the signed-in account's plan.
- Agents act as the signed-in Ref user and see only the private documentation that user can see.
- Agents get Ref only in the projects the secret is linked to.
- Agents can do only what the connected Ref account and its granted scopes allow.
Troubleshooting
Test says Ref rejected the token (401)
The sign-in expired or was revoked. Select Reconnect on the secret and sign in to Ref again.
The secret shows Needs reconnect
Ref ended the grant. Select Reconnect on the secret and sign in to Ref again.
New tasks on the project have no Ref tools
Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with, and an agent marked Not supported on that tab cannot load MCP servers.
Still stuck? Select Test and read the result: it names the value Ref refused and the status it answered.
FAQ
Can I paste a Ref API key instead of signing in?
No. Ref takes its API key in its own header, which a linked MCP connection does not send; signing in gives the same access.
What does Test do?
It opens an MCP session with Ref's server and lists its tools, then closes the session. It reads and changes nothing in your Ref account.
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 Ref account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.