A hosting layer for MCP servers — it runs the server and handles the auth so you only paste a URL.

Pick this when

You want a third-party integration without self-hosting anything or managing OAuth yourself.

What makes it different

Hosted servers mean no install and no local process to keep alive

Handles the underlying service authorization as part of the connect flow

What it does

Hosts MCP servers for common SaaS tools (the Google Sheets server used in BC5)

Manages the OAuth handshake to the underlying account

What it does not do

Common wrong expectations

Doesn't remove the trust question — a hosted third party sits between you and your data

Where it sits in a stack

The convenience path for third-party MCP: discovery on Smithery, hosting on Composio, connection in Claude.

Shelf

MCP & connectors · Backend, hosting & code

Our status · watch

No third-party MCP need at present.

For your projects

Note the data-path question for anything involving Paul's own accounts: a hosted server means the traffic isn't local.

Freshness

current

Related tools

complementsSmitherycomplementsClaude Desktop connectors

smithery: discovery vs hosting

claude-desktop-mcp: the consuming host

Every moment the course touched it (1)

SessionCoverageMomentWhat happened
Session 13: Claude Code — Skills, Sub Agents & the Token Economy (posted as 'Beyond Vibe Coding — n8n & More')mentioned2:13:06Host of the awesome-claude-code-skills curated list

← All tools by category