Skip to navigation
Apps and API

MCP server

Start, follow and steer AOSplane sessions from Claude Code, Cursor or any other MCP client
View as Markdown

The AOSplane MCP server lets the AI tools you already use start sessions, follow them, send messages and answer permission requests. You add one URL to your client and sign in with your AOSplane account. There’s no key to copy.

The server address is https://mcp.aosplane.io/mcp.

The server acts as you, in the organization you sign in to, with your role. It can’t do anything you couldn’t do in the dashboard.

Add it to your client

Run this, then type /mcp in Claude Code to sign in:

claude mcp add --transport http aosplane https://mcp.aosplane.io/mcp

Any other client that supports remote MCP servers over HTTP with OAuth sign-in works the same way.

Sign in

1

Check the request

Your client opens a browser page called Connect followed by the client’s name and to AOSplane? It lists what the client will be able to do and where you’ll be sent back.

2

Continue

Choose Continue to sign in. Choose Cancel if you didn’t start this from an app you trust.

3

Sign in with AOSplane

Sign in as you do on the web. If you belong to more than one organization, pick the one the client should work in under Choose an organization.

4

Go back to your client

The browser returns you to the client, which can now use the AOSplane tools.

Try asking your client: “List my AOSplane projects, then start a session in acme/web that fixes the failing test.”

What your client can do

GroupTools
SessionsList projects, agents, repositories and sessions, get one session, start a session, fork it, send a message, switch its agent, pause, resume, cancel and archive it.
FollowWait for a session to finish its turn or need you, read its conversation, read its changes, list tasks it delegated, and get a link to a QA check video.
ApprovalsList and answer an agent’s permission requests, and list or revoke saved approvals.
PreviewShare a port the sandbox serves as a private preview link, list previews and stop sharing them.
  • Read only: list_projects, list_agents, list_repositories, list_runs, get_run, wait_for_run, get_transcript, get_run_diff, list_child_runs, get_qa_recording, list_permission_requests, list_permission_grants, list_ports.
  • Change something: start_run, fork_run, send_message, switch_agent, pause_run, resume_run, archive_run, answer_permission_request, revoke_permission_grant, expose_port, unexpose_port.
  • Can’t be undone: cancel_run stops a session for good, along with any tasks it delegated.

Good to know

  • Sessions started from your client show up in the dashboard like any other, so you can open them there too.
  • Your client answers a permission request once. It can’t save an “always allow”. Questions from the agent and plan approvals are answered in the dashboard.
  • To give a client fewer tools, add ?read_only=true to the URL to leave out every tool that changes something, or ?toolsets=sessions,follow to pick groups (sessions, follow, approvals, preview). This keeps the list short, but it isn’t a security boundary.
  • Each person can make 120 requests a minute and have 4 waits open at once. A wait lasts up to 5 minutes, then your client simply waits again.
  • If you sign out of AOSplane or are removed from the organization, the client stops working until you sign in again.