Connect your first agent

1. Create your account

Open my.sallyport.cloud. Press “Continue with Google”, or sign up by email: press “Continue with email”, enter your email and press “Continue”. For a new email, fill in “First name”, “Last name” and “Password” and press “Create account”. Then enter the 6-digit code from your inbox and press “Confirm email”.

The person who signs up owns the organization and its first workspace. Adding keys and agents takes the owner or admin role.

2. Save a service key

Open Add a credential. This guide uses GitHub: type it into “Service from the catalog” and pick GitHub API. Keep “Live” under “Environment”.

Under “How to connect GitHub API”, choose “Access token”. Press “Create the key at GitHub API”, create a token at GitHub and paste it. Press “Save the credential”.

Sallyport checks the token with GitHub as it saves it. From that moment every agent of the workspace can use the key. The other way, “Sign in with GitHub”, sends you to GitHub to approve; the form says what it needs.

3. Create an agent

Open Agents and press “New agent”. Type a “Name”, such as laptop-claude, and press “Create agent”. The agent’s page opens.

Its “Access” list already holds the GitHub key. New rows run every call without asking.

4. Connect Claude Code

On the agent’s page, “Connect this agent” has Claude Code selected. Press “Copy for Claude Code”. Sallyport creates a token and copies the whole command with it.

export SP_AGENT_TOKEN='<agent-token>'
claude mcp add --transport http --scope user sallyport https://mcp.sallyport.cloud/mcp --header "Authorization: Bearer $SP_AGENT_TOKEN"

Run it in a terminal, then restart Claude Code. The copied command carries the token itself; the sample above reads it from SP_AGENT_TOKEN. Once added, claude mcp list shows sallyport.

The token is shown once and is listed under “Tokens” on the agent’s page. For Cursor, Codex, Claude, ChatGPT and other clients, see MCP clients and remote servers.

5. Make the first call

Ask the agent: “Read my GitHub profile through Sallyport.” It finds GitHub among its tools and calls github_read with these arguments:

{
  "method": "GET",
  "path": "/user"
}

Sallyport adds the token, calls api.github.com and returns GitHub’s answer. The agent never sees the token. The call and its result appear in Activity.

6. Answer your first approval

Calls run without asking until you decide otherwise. On the agent’s page, in the “Access” list, turn on “Ask every call” in the GitHub row.

Ask the agent to read the profile again. The call waits, and its card appears in Approvals and on any open console page. If the wait runs long, the agent shows you the card’s link.

Press “Approve”: the call runs and the agent gets the answer. “Refuse” stops it, and the agent reads the reason you give. Cards can also reach this browser, Telegram or email: turn that on in Notifications. More in Approvals.

Without a key, the agent asks for one

An agent can reach a public service you have not connected. It calls http_request with the full URL, or request_access with the service name and a purpose: one sentence on why it needs the service. Sallyport answers with a link for you.

{
  "method": "GET",
  "url": "https://api.stripe.com/v1/balance"
}

The link opens the request in Needs a key. Add the key or sign in, then press “Grant access”. Every agent of the workspace gets the key, and the agent repeats its call.