Overview

Jussora sits between your agent and the tools it calls on your customers’ behalf. Your customers connect their own accounts to Jussora, such as their GitHub, and choose which tools your agent may call. Your agent calls those tools through Jussora over MCP. You never hold your customers’ credentials, and they can see and change what your agent may do at any time.

New here? The Quickstart takes about 15 minutes and walks you through a whole call, from adding an agent to approving its call yourself.

What happens on a call

Say your agent calls GitHub’s create_issue tool for a customer you know as cust_4412:

1. Your agent sends the call to https://app.jussora.com/mcp, with its API key and the header Jussora-Account: cust_4412.
2. Jussora finds the person you call cust_4412, and what they chose for that tool.
3. What happens next is the customer’s choice:
   • Allow. Jussora calls GitHub with the customer’s own token and hands back GitHub’s answer.
   • Ask. Jussora calls nothing yet. It answers “Waiting for approval” with a request id, and emails the customer. When they approve, Jussora calls GitHub. Your agent collects the result with Jussora’s check_approval tool.
   • Block, or a tool they never gave your agent. Jussora refuses the call and calls nothing.
4. Jussora records every call and every decision.

Because Jussora is the one holding the customer’s token, an approval is the call itself, and a rejection cannot be worked around.

Words these docs use

• Agent. What you build. You add it in the console, where it gets an API key and a list of the providers it may use. You name providers, never tools: which tools it gets is up to each customer.
• Customer. A person your agent acts for. They have their own Jussora account, which they sign in to at app.jussora.com.
• Your identifier. Whatever you already call a customer in your app: a user id, a username, an email address. Your agent sends it in the Jussora-Account header, and Jussora never reads meaning into it. It is printable ASCII with no spaces, up to 255 characters.
• Connection link. A one-time link you make for one of your identifiers and show to that customer inside your app. It expires after five minutes, and whoever opens it connects their Jussora account to that identifier.
• Tool access. What a customer chose for each tool: Allow, Ask or Block. Every tool starts at Ask when they connect. A tool they have not chosen for is not available to your agent.
• Request. What a call to a tool at Ask creates. It waits until the customer answers, and never expires.

Endpoints

Endpoint	What it is for	Credentials
POST https://app.jussora.com/mcp	Your agent’s tool calls, over MCP	API key and Jussora-Account
POST https://app.jussora.com/v1/connection-links	Making a connection link for a customer	API key
POST https://app.jussora.com/v1/connections/status	Checking whether calls for an identifier will land	API key
POST https://app.jussora.com/v1/connections/release	Giving up one of your identifiers	API key

Jussora speaks MCP 2026-07-28, and the 2025-11-25 and 2025-06-18 versions through initialize. A client that declares MCP’s tasks extension gets a call at Ask back as a task, which completes when the customer answers, instead of the “Waiting for approval” text.

Providers

Today your agent can use GitHub, Linear and Notion. It can also use Jussora’s own provider, whose one tool lets your agent ask the customer a question and get their answer back, which needs no account anywhere else.

What it costs

Every developer account gets $20 of free credit each calendar month, in UTC, which does not carry over. A call that succeeds costs $0.001. Nothing else is charged: not listing tools, not collecting an outcome, not a refused or failed call. Once the month’s credit is used up, new calls are refused until the next month begins. There are no paid plans yet.

Where things are

• The console, at console.jussora.com, is yours: agents, API keys, links, your customers’ identifiers, and every call your agents made.
• The app, at app.jussora.com, is your customer’s: connecting accounts, choosing tool access, and approving requests.