Give your agents a login, not a password

Connect the way your agent already works

Make an agent in your workspace, pick the identities it may use, and copy its key. Keys start with jp_live_ and are shown once.

{
  "mcpServers": {
    "joinpane": {
      "url": "https://mcp.joinpane.com/northlight",
      "headers": { "Authorization": "Bearer YOUR_AGENT_KEY" }
    }
  }
}

# Open a window in an identity
curl https://api.joinpane.com/v1/windows \
  -H "Authorization: Bearer jp_live_…" \
  -d '{ "identity": "studio-uploads" }'

# Read what’s on the page
curl https://api.joinpane.com/v1/windows/win_4Fq8/page \
  -H "Authorization: Bearer jp_live_…"

What an agent gets, and what it doesn’t

It asks a person first

When an agent reaches a step that can’t be undone, it stops and asks. The question goes to the people you pick, all at once or one after another, and the first answer is the one used.

1. Publish

   UploaderPaused
   1Agent pauses

   Uploader reaches Publish, stops, and writes down why it needs a person.

2. JoinpanenowUploader asks: publish episode 13?

   Publish
   2Phones get the question

   Mei and Rin get a push with the agent’s screenshot and its question.

3. MLMei said yes, publish14:31RKRin: answered by Mei
   3First answer wins

   Mei answers first. Rin’s phone updates to show it’s handled.

4. UploaderWorkingPublished episode 13, approved by Mei
   4Agent carries on

   Uploader publishes, and the audit log records who said yes.