Connect once. Use from any agent.
These are the services Propolis ships with today. Each is authorised in your browser and brokered so your agent only ever holds a Propolis token.
Gmail, Calendar, Drive and Docs through an MCP server Propolis hosts itself. Read, search and draft without the agent ever holding a Google token.
Pull frames, components and design context from Figma's hosted MCP into your agent's workflow.
Search, read and update pages and databases through Notion's hosted MCP with the OAuth dance handled for you.
Slack's hosted MCP, brokered. Bring your own Slack app keys or use ours; Propolis keeps the workspace grant.
Jira issues and Confluence pages via Atlassian's hosted MCP, scoped to the sites you authorised.
Let an agent read issues, events and traces from Sentry's hosted MCP to debug with real production context.
Run cross-browser and device tests, pull results and manage test cases through BrowserStack's hosted MCP without handing agents your access key.
Route Claude Code through Propolis so your Pro or Max OAuth token stays on the server instead of on every machine.
Same forwarder, backed by a console API key — hand out revocable Propolis tokens instead of the key itself.
Claude Design's MCP, reached with the same OAuth flow Claude Code uses, brokered so agents share one grant.
Three ways a call is brokered
- MCP server hosted by Propolis
- Propolis runs the MCP server itself and talks to the service's REST API with your grant. Used for Google Workspace, where no first-party MCP exists.
- Brokered hosted MCP
- The service publishes its own MCP server that demands OAuth. Propolis stands in front of it, swaps your Propolis token for the upstream grant, and passes the MCP conversation through.
- API forwarder
- For Anthropic's own API: Propolis forwards requests with the stored key attached, streaming included, so a Claude Code instance can run without the key on its machine.
Missing one you need? Tell us; the connector contract is small.
Create a free account