Connect over MCP

Partybus exposes a remote MCP server using the Streamable HTTP transport. Any MCP-compatible client can connect.

Endpoint & auth

The endpoint is https://files.partybus.ai/api/mcp. Authenticate with a bearer token - either a Partybus developer token (pb_…) or an Auth0 access token issued for the configured audience.

Authorization: Bearer pb_YOUR_TOKEN

Claude Desktop / Cursor

Add a server entry to your client's MCP configuration:

mcp.json

{
  "mcpServers": {
    "partybus": {
      "url": "https://files.partybus.ai/api/mcp",
      "headers": { "Authorization": "Bearer pb_YOUR_TOKEN" }
    }
  }
}

OAuth clients

Clients that support OAuth can discover the authorization server via the protected resource metadata at /.well-known/oauth-protected-resource and run the standard flow. After a 401, the client fetches that metadata, authenticates, and retries with the issued access token.

Available tools

list_files - list files in your account.
read_file(name) - read UTF-8 text contents.
write_file(name, content) - create or overwrite a text file.
delete_file(name) - delete a file.

Every call is scoped to the account that owns the token, with credential-layer isolation - an agent can never read across accounts.