PasserJack help

Connect opencode

Add PasserJack to opencode.json. opencode starts browser sign-in when you first use the server.

Signs in through your browser.

Before you start

A PasserJack account
opencode installed
Access to your opencode.json

Show the visual walkthrough

opencode, step by step

Step by step

Paste the opencode.json block below into your opencode.json.
Start opencode and use PasserJack. opencode starts browser sign-in automatically when authentication is needed.
Keep opencode running and approve access in a browser on the same computer. Once connected, use its tools without running another sign-in command.
Only if PasserJack is not connected and no sign-in is waiting, use the manual sign-in command below in a terminal.

What to paste

opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "passerjack": {
      "type": "remote",
      "url": "https://passerjack.com/api/mcp",
      "enabled": true
    }
  }
}

Skip this if browser sign-in already succeeded.

Only if not connected: in a terminal

opencode mcp auth passerjack

Use an API key instead

Open Agents and API keys, choose opencode, then expand Use an API key instead to create your key. These examples carry a placeholder.

Prefer a key? Open PasserJack, then Settings, then Agents and API keys, choose opencode, expand Use an API key instead, press Create a key and fill this in, and copy the block, then paste it into opencode.json.
The key block carries oauth: false beside the header. Without it opencode goes off to sign in and never uses the header, which looks exactly like a bad key.

opencode.json with a key: oauth: false is required beside the header

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "passerjack": {
      "type": "remote",
      "url": "https://passerjack.com/api/mcp",
      "oauth": false,
      "headers": {
        "Authorization": "Bearer pj_paste-your-key-here"
      },
      "enabled": true
    }
  }
}

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.