PasserJack help

Connect Other MCP clients

Any MCP client that speaks HTTP can reach PasserJack. Most take the URL plus a bearer header.

Uses an API key from Settings.

Before you start

A PasserJack account
A client that speaks MCP over HTTP, or one that needs a stdio bridge
A PasserJack key, unless your client speaks OAuth discovery

Show the visual walkthrough

Other MCP clients, step by step

Step by step

If your client speaks OAuth discovery, give it only the MCP URL and let it sign you in. There is nothing else to do.
Otherwise open PasserJack, then Settings, then Agents and API keys, choose Other MCP clients, press Create a key and fill this in, and copy the block.
Give your client the URL and the Authorization header, in whatever shape its own config file wants.
A client that only speaks stdio needs the bridge command. Save the header line as passerjack-headers.txt and give --header-file its full path.
Shapes differ. Amp refuses secrets as arguments, opencode needs oauth: false beside a header, and Goose wants YAML with extensions and a uri rather than url.

What to paste

HTTP transport

URL: https://passerjack.com/api/mcp
Header: Authorization: Bearer pj_paste-your-key-here

Or a stdio bridge: the command

npx mcp-remote https://passerjack.com/api/mcp --header-file passerjack-headers.txt

And the header file it reads (save as passerjack-headers.txt and give --header-file its full path)

Authorization: Bearer pj_paste-your-key-here

Create your key in Agents and API keys to fill in these blocks.

Preview the PasserJack screens

The PasserJack Agents panel in Settings, with an agent selector and setup instructions for the selected client.

Open Agents and API keys and choose your agent. If you use an API key, each new key is shown exactly once.

The PasserJack consent screen, naming the app asking for access and the permissions it is asking for.

This is the screen a browser sign-in lands on. It names the app that is asking and the permissions it wants, and nothing is granted until you approve it. Read covers your whole ordinary Board, including your attachments. The default edit limit protects items the app did not create from changes; it does not hide them from reads.

Check it worked

Ask the agent: who am I connected as?

A correct answer names your account email, the key or app it is using (for example “Grok - Sep 10, 2026”), and its permissions: read, write if granted, and secrets only if you granted it. If it cannot answer, or names a different account, the connection is not made, so go back through the steps.

Granted write access? Ask it to save a short test note, then confirm that note appears on your board.

Vault reads need both secrets permission and an Unlock for agents window you explicitly open in Vault settings. That permission also includes text and extracted details from sensitive Board images without a Vault window. Review the permission and capture boundaries before granting it.

Manage or disconnect

Open PasserJack, then Settings, then Agents and API keys. That page lists your keys, the apps you have connected and your connector credentials, and you revoke any of them from there.

A revoked key stops working immediately. If a client reports an authentication error, check which account it is signed in to and whether its key was revoked before you create another.