Agents in your terminal

Jupiter Jots can expose its library to an agent running in your terminal. The agent searches, reads, saves and organises through MCP (Model Context Protocol), the standard way tools are offered to Claude Code, Cursor and other MCP clients.

The connection is local to this computer. A small bridge, distributed as the jupiter-jots-mcp npm package, runs on your machine and talks to the extension. There is no account and no Jupiter Jots server in the middle. The agent may still send what it reads to its own model provider, under that provider’s terms.

This is different from Ask Jupiter: Ask Jupiter is the chat inside the extension, using the key you added there. Connected agents are outside programs you already work with. New to Jupiter Jots? Start with the basics: installing, saving and organising.

You need:

• Jupiter Jots installed in Chrome, with the Connected agents feature. The guide covers installing and pinning it.
• Node.js 18 or newer and npm, because the bridge runs from the jupiter-jots-mcp npm package. If Claude Code runs on this machine, its Node.js is enough.
• An MCP client that can launch a local stdio server. The examples below use Claude Code; any client that understands command and args works the same way.
• An internet connection the first time, to download the bridge. Later runs use npm’s cache.

Keep Chrome running while you use the bridge. The extension’s offscreen document holds the local connection; closing Chrome closes it too.

1. In Jupiter Jots, open Settings → Connected agents.
2. Turn on Let outside agents connect.
3. Continue with the next step. If the local bridge is not running yet, the status may say Connecting; it retries until the daemon starts, then changes to Connected. The page can be closed; the bridge keeps running in the extension.

Connected agents is off by default. Turning it on does not install a key or contact an AI provider: it only opens the local door an agent can knock on.

Point your MCP client at the npm package. In Claude Code, add this to the project’s .mcp.json:

{
  "mcpServers": {
    "jupiter-jots": {
      "command": "npx",
      "args": ["-y", "jupiter-jots-mcp"]
    }
  }
}

npx downloads the bridge the first time and runs it as a stdio MCP server. You do not need a checkout of the extension, and there is no separate command to start. For another MCP client, use npx as the command and -y jupiter-jots-mcp as its arguments.

Restart the client or approve the project server when it asks. The client starts the local daemon itself. Once Connected agents is on in the extension, the two sides pair and Bridge status becomes Connected.

Run /mcp in Claude Code. jupiter-jots should show as connected with tools available.

There is no extension ID to configure. The first extension that connects pairs with the local daemon; after that the daemon accepts only that pairing. Use Repair pairing if the extension was reinstalled or its browser data was cleared.

Once connected, you can ask the agent in your own words. It sees the same tools as the app, filtered by your permission settings.

Every request that changes your library waits for you. A Write or Destructive card appears on Connected agents with the agent’s name, the tool and the input. Choose Approve or Deny; nothing changes before you decide.

• Writes wait even when the tool is On. On controls reads, not writes.
• Destructive tools and sharing tools always ask, even if you try to set them to On.
• Closing tabs needs an extra checkbox. Saving tabs with close: true also closes them in Chrome, so Approve stays disabled until you tick it.
• Closing the page does not cancel the request. Reopen Connected agents to decide; turning the bridge off or revoking it denies everything still waiting.

If you are away, calls stay pending. There is no timeout that quietly applies them.

Open Settings → AI tools. Each tool has separate settings for Assistant (Ask Jupiter) and MCP (outside agents):

• Off hides the tool completely. It is not offered to the agent.
• Ask runs it only after you confirm.
• On lets reads run. Writes still come back as proposals or approval cards.

MCP starts stricter than the assistant: most tools start at Ask, while the assistant’s ordinary reads and writes start On. Read-only turns every write and destructive tool off for both callers in one step. You can also set a group of tools off together, or reset everything to its defaults.

Hidden notes and locked notes never reach an agent, whatever its permissions say.

The bridge itself stays on this computer and listens only on loopback. Your pairing token is stored locally, and the bridge’s state files are readable only by your user account. Nothing in the bridge is sent to Jupiter Jots.

An agent can read what its tools return: page titles, addresses, descriptions, your notes, tags and collection names. As with Ask Jupiter, it never receives the text of the pages themselves, hidden notes or locked notes. What the agent does with those results is up to it; if it uses a cloud model, that provider receives what the agent sends, under its own privacy policy.

The privacy policy lists this alongside the rest of the extension’s network activity.

• Turn the toggle off to deny pending calls and disconnect every agent. Your pairing is kept, so you can turn it back on later.
• Revoke closes every agent, denies pending calls, and rotates the pairing token. The extension has to pair again before an agent can reconnect.
• Repair pairing is for a reinstall or cleared browser data. Use it when the bridge is running but refuses this browser.
• If Repair still fails, stop the local daemon and clear its pairing, then use Repair pairing again:

npx -y jupiter-jots-mcp --reset-pairing

Only one browser extension is paired with a bridge at a time. To switch to a second profile or a copied browser, reset the daemon’s pairing with the command above, then use Repair pairing in the browser you want to connect.

The client says “Jupiter Jots is not connected.” The proxy is running but the extension has not paired. Open Jupiter Jots → Connected agents, turn the bridge on, and check that Chrome is running. In Claude Code, claude mcp list or /mcp shows the same state.

The bridge says “pairing mismatch.” Click Repair pairing. If it still fails, run the reset command above and repair again.

The connection works but a tool is missing. Open Settings → AI tools and check that tool under MCP. Off tools are not listed at all.

The agent cannot start the server. Check that Node.js 18 or newer and npm are installed, then run npx -y jupiter-jots-mcp once in a terminal to see its error. The client config must use npx as the command and -y jupiter-jots-mcp as its arguments.

Tools stopped after an update. Disconnect the agent, close any old bridge process, reload the extension, then reconnect with npx -y jupiter-jots-mcp@latest. Upgrading both halves together avoids a bridge speaking an older protocol.