Your tools,
inside every conversation.
Connect GitHub, Slack, Notion and 19 more services. Keys stay in your Keychain, and every tool is approved by you before the model can use it.
GitHub Connected
Slack Connected
Notion Connected
LinearConnect
FigmaConnect22 services,
a list small enough to audit.
Where a provider runs an official MCP endpoint the app connects to it directly (12 of 22); otherwise through a broker.
Productivity5
- NotionSearch and work with your Notion workspaceOfficial MCPmcp.notion.com
- LinearIssues, projects and product planningOfficial MCPmcp.linear.app
VercelProjects, deployments and runtime logsOfficial MCPmcp.vercel.com
Google CalendarEvents, schedules and availabilityVia broker
Outlook CalendarMicrosoft 365 events and schedulesVia broker
Communication5
- SlackSearch conversations and collaborateOfficial MCPmcp.slack.com
Microsoft TeamsMessages, meetings and team contextVia broker
GmailSearch mail and work with conversationsVia broker- Outlook EmailMail, folders and Microsoft 365 contextVia broker
ZoomMeetings, recordings and transcriptsVia broker
Storage4
DropboxFind and work with files in Dropbox (beta)Official MCPmcp.dropbox.com
BoxSearch and work with enterprise contentVia broker
Google DriveFind and work with Drive filesVia broker
SharePointSites, documents and Microsoft 365 contentVia broker
Developer tools3
SupabaseDatabases, projects, functions and docsOfficial MCPmcp.supabase.com · read-only- GitHubRepositories, issues and pull requestsOfficial MCPapi.githubcopilot.com
OpenAI DevelopersOpenAI platform documentation and developer resourcesOfficial MCPdevelopers.openai.com
Creativity2
- FigmaDesign context, assets and canvas workflowsOfficial MCPmcp.figma.com
CanvaCreate, find and export Canva designsOfficial MCPmcp.canva.com
Business2
StripePayments, customers and subscriptionsOfficial MCPmcp.stripe.com
HubSpotCRM, contacts and sales activityVia broker
Research1
ConsensusEvidence-backed academic researchOfficial MCPmcp.consensus.app
Connecting
takes five steps — all of them yours.
The engine runs the sign-in but never opens a browser itself — you approve on the provider's page.
- 01
Pick a service
From a fixed, reviewed list — or paste a public HTTPS MCP address of your own.
- 02
Sign in on its own page
A native-app OAuth flow with PKCE and a one-shot loopback listener that waits 300 seconds, then closes.
- 03
Keys stay in your Keychain
Tokens live in the macOS Keychain as connector.<name> — never in the database, never in a file.
- 04
Approve each tool
A tool reaches the model only after you approve it at its current definition.
- 05
Turn plugins on per run
Approved tools are offered only in the runs you switch plugins on for.
One guarded client
for every plugin call.
Plugin traffic goes from your Mac to the provider through one guarded client. Its rules live in the engine, not in a settings page.
- Address
- Public HTTPS only, port 443 — every resolved address must be public
- Shape
- No credentials, fragment or query in the URL
- DNS
- The checked answer is pinned, so it can't be resolved again mid-request
- Routing
- No proxy, no redirects
- Tokens
- Refreshed when fewer than five minutes remain; never logged or returned
- Results
- Treated as untrusted data — redacted and size-bounded
- Timeouts
- A call with no answer in time is recorded as an unknown outcome and never retried
Extend it
without handing over more authority.
Teach the agent a procedure, or give it a tool of your own.
Skills
A skill is guidance placed in the task's message — never a system instruction. Only you add them. A skill is up to 16 KiB, a task can use up to four, and each version is kept. A skill can't add tools, grant permissions or change the model.
MCP servers
Servers you add run in a sandbox container with no network, no capabilities, a read-only root and your workspace mounted read-only. Each tool is approved at a pinned schema, and every call is recorded.