Docs
MCP
Point an OAuth-capable MCP client at the workspace endpoint. The person approves the client in the browser. No API key is pasted into the assistant.
Endpoint
The server is stateless Streamable HTTP. Discovery, dynamic client registration and token exchange live on the same host.
https://api.flipbird.io/mcp How a person connects
The client opens a browser. The person chooses their workspace, signs in at the workspace's own address with any sign-in method it allows, and approves the scopes. The client never sees a password or session, and can never do more than the person's role allows.
What the assistant can do
Tools are generated from the public API. A tool is offered only when the grant's scopes and the workspace plan both allow it. Destructive tools ask for an explicit confirmation. Plans without MCP access refuse the connection.