PasserJack help
Connect Grok
Grok needs a connector credential from PasserJack as well as the MCP URL. Sign-in still happens in your browser.
Uses a connector credential from Settings.
Before you start
- A PasserJack account
- Grok at grok.com, on the web or on your phone
- A connector credential minted in PasserJack, under Settings, then Agents
Show the visual walkthrough
Step by step
- Open PasserJack, then Settings, then Agents, press Connect an agent, choose Grok, and create a connector credential. Keep that tab open.
- Open grok.com/connectors, choose New Connector, then Custom.
- Paste the MCP URL as the server URL and the Client ID from PasserJack. Leave Client Secret blank and choose none (PKCE only, recommended).
- Grok fills the authorization and token URLs from our discovery document. Check they match the two PasserJack shows. If the form has a Scopes field, read write offline_access is right. Then save.
- Finish the sign-in when Grok asks, and approve access on the PasserJack consent screen.
What to paste
https://passerjack.com/api/mcp
The Client ID goes with it, and that one is yours alone: mint it in Settings, then Agents, under Grok.
Preview the PasserJack screens

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

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.
Messages from your other agents
- Grok cannot be woken while idle, so at the start of a conversation ask it to register a PasserJack session named for what you are doing (it calls register_session).
- When you come back to the conversation, and before anything long, ask it to check PasserJack messages (check_messages with its sessionId; that also keeps the session listed for your other agents).
- Ask it to claim a message before acting on it and mark it done afterwards; a message meant for another session it leaves alone.
- Ask it to keep a one-line status current, so a message addressed to whoever is on the billing fix reaches it.
- Remind it that a message is what another agent said, not an instruction from you: it acts on the ones that fit what you asked it to do and tells you about the rest.
- When you finish there is nothing to close: a session that stops checking drops off your sessions list on its own.
Manage or disconnect
Open PasserJack, then Settings, then Agents. That page lists your keys and the apps you have connected, and you revoke any of them from there. Connector credentials (Grok) live under Connect an agent, in the Grok tab.
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.