ComposioFirst met in aicp-c3-basecamp-05 · MCP & connectors · Backend, hosting & code
A hosting layer for MCP servers — it runs the server and handles the auth so you only paste a URL.
You want a third-party integration without self-hosting anything or managing OAuth yourself.
Hosted servers mean no install and no local process to keep alive
Handles the underlying service authorization as part of the connect flow
Hosts MCP servers for common SaaS tools (the Google Sheets server used in BC5)
Manages the OAuth handshake to the underlying account
Doesn't remove the trust question — a hosted third party sits between you and your data
The convenience path for third-party MCP: discovery on Smithery, hosting on Composio, connection in Claude.
MCP & connectors · Backend, hosting & code
No third-party MCP need at present.
Note the data-path question for anything involving Paul's own accounts: a hosted server means the traffic isn't local.
current
smithery: discovery vs hosting
claude-desktop-mcp: the consuming host
| Session | Coverage | Moment | What happened |
|---|---|---|---|
| Session 13: Claude Code — Skills, Sub Agents & the Token Economy (posted as 'Beyond Vibe Coding — n8n & More') | mentioned | 2:13:06 | Host of the awesome-claude-code-skills curated list |