Skip to main content
You can now connect Claude.ai, ChatGPT, or Cursor to your Bower workspace so your AI assistant can search, read, and write directly to your notes, projects, and experiment data. Wherever you are working, Bird’s workspace knowledge is available without switching context. Shipped 2026-05-31 · Integrations

​
What’s new

  • Claude.ai — add Bower as an MCP connector; native refresh-token support keeps the session alive.
  • ChatGPT — add Bower as a custom MCP connector (Pro plan or higher).
  • Cursor — configure Bower via ~/.cursor/mcp.json or Settings → MCP / Tools.
  • A new AI app access tab in Settings shows which clients have connected and lets you manage access.
All clients connect to the same endpoint: https://app.bowerlabs.ai/mcp.

​
How it works

Connection uses OAuth 2.1 + PKCE. When you add Bower as an MCP server in your client, the client opens a browser tab to Bower’s sign-in page. Sign in with your Bower account and, if you belong to more than one workspace, pick which one to grant the client access to. Bower issues tokens and redirects you back to the client. The whole flow takes under a minute. Tokens are issued and rotated by WorkOS AuthKit, Bower’s identity partner. Refresh tokens rotate automatically, so long-running client sessions stay connected without re-authorisation. Bower stores no credentials of its own. Workspace isolation is server-enforced on every request — a token scoped to workspace A never returns data from workspace B, even if you are a member of both.

​
Privacy

  • Bower never sees your AI client’s credentials. Only OAuth tokens are exchanged.
  • Tokens are issued and rotated by WorkOS AuthKit. Bower stores no access tokens.
  • Workspace isolation is server-enforced — valid tokens for one workspace never surface data from another.

​
Tier limits

AI app access is available on all paid Bower tiers. Restricted-mode workspaces are not yet supported — server-side enforced until the identity provider BAA is in place. AI app access — setup guide