ClawLink
Give your coding agent OAuth-backed access to Gmail, Slack, Notion, GitHub, and 100+ other apps through one ClawLink MCP remote.
Overview
ClawLink is a MCP server for the Build phase that connects AI agents to 100+ apps via one hosted endpoint and OAuth-backed ClawLink API keys.
What is this MCP server?
- 100+ connected apps with one-click OAuth (Gmail, Slack, Notion, GitHub called out)
- Hosted streamable-HTTP MCP at claw-link.dev with required x-clawlink-api-key header
- API keys created at claw-link.dev/dashboard/api-keys
- Open-source client repo on GitHub (hith3sh/clawlink), registry version 0.1.0
- 100+ apps supported per registry description
- Server version 0.1.0
- Required secret header x-clawlink-api-key on MCP remote
Community signal: 130 GitHub stars.
What problem does it solve?
Each SaaS integration means another OAuth app, another MCP server, and another secret to rotate.
Who is it for?
Solo builders who need many SaaS connectors quickly for agent automations and internal tools.
Skip if: Products that require air-gapped-only tooling, fine-grained per-tool MCP control documented locally, or zero third-party SaaS dependency.
What do I get? / Deliverables
One MCP remote and API key lets your agent act across Gmail, Slack, Notion, GitHub, and the rest of ClawLink’s catalog after OAuth.
- Agent-callable tools across authorized ClawLink-connected apps
- Centralized integration surface replacing many per-app MCP entries
Recommended MCP Servers
Journey fit
How it compares
OAuth aggregation MCP hub, not a single-app dedicated MCP or a local stdio-only dev tool.
Common Questions / FAQ
Who is dev.claw-link/clawlink for?
Indie builders and small teams running MCP agents who need broad SaaS access without wiring dozens of separate integrations.
When should I use dev.claw-link/clawlink?
Use it in Build when your agent must read or update real accounts (email, chat, docs, repos) and you want centralized OAuth instead of per-vendor MCP servers.
How do I add dev.claw-link/clawlink to my agent?
Create an API key at https://claw-link.dev/dashboard/api-keys, register remote https://claw-link.dev/api/mcp with header x-clawlink-api-key, then complete OAuth for each app in ClawLink.