Skip to main content
Your MCP client must support a remote server at https://api.bead.run/mcp. The hosted MCP server provides tool discovery and skill resources so your agent can load guidance as it works.

​
Interactive OAuth

Add the endpoint in your MCP client’s remote-server configuration:
Configuration fields vary by client. Choose Streamable HTTP and use the client’s OAuth connection flow. The server’s 401 challenge points to protected-resource metadata. Consent uses GitHub sign-in at app.bead.run, followed by explicit approval of requested client permissions. The authorization server supports dynamic registration and authorization code with S256 PKCE. Access tokens last one hour and target the MCP audience. API device-flow tokens target a different audience.

​
Headless bearer access

Configure a private scoped bead key through your client’s secret or environment support. Send it as Authorization: Bearer on every request. A session ID is not authorization. For an HTTP transport check:
Use a private execution environment and keep request headers out of logs. Your MCP client handles protocol negotiation for normal use.

​
Discover capabilities

Read every tools/list page using its nextCursor. Discovery returns 12 tools per page. Tool schemas and access depend on the server and your credentials. Discovery, skill reads, pricing and enrollment are available without an account key. Purchase tools also support access through privately retained purchase IDs and possession secrets. Other operations require authenticated access and enforce their applicable scope, organization, revocation and funding checks. See tools, skills and retained results, and agent signup.