GUIDE
How to deploy your first MCP server in five minutes
A walkthrough of getting your first server online, from npx command to Claude Desktop connection. No infrastructure, no Docker, no headaches.
// BLOG
THE MCP STACK, DOCUMENTED.
Deployment patterns, transport tradeoffs, auth strategies, and infrastructure decisions — written by engineers shipping production MCP servers.
DEEP DIVE
Transports compared: stdio vs SSE vs HTTP vs WebSocket
Four transports, four sets of tradeoffs. A practical comparison of stdio, SSE, HTTP, and WebSocket: when each one is the right choice and where they break.
RELEASE
Toolcall v0.2: resource support, audit logs, team workspaces
Resource support for static data, audit logs for every tool call, and team workspaces with role-based access. What's in v0.2 and what's coming next.
FIELD NOTE
What 50 startups taught us about hosting MCP servers
Patterns we've seen across the first 50 customers. What works, what doesn't, and why most teams underestimate the operational cost of running their own MCP infrastructure.
DEEP DIVE
The hidden cost of running your own MCP infrastructure
A real cost breakdown for self-hosting MCP servers at scale. Compute, auth, monitoring, and the engineering hours nobody budgets for.
GUIDE
Authentication patterns for MCP: API keys, OAuth, JWT
Three auth patterns for MCP servers and when to pick each. API keys, OAuth flows, and JWT-based scoped tokens, with the tradeoffs nobody documents.
// FAQ
MCP is an open standard from Anthropic for connecting AI models to external tools and data. Toolcall hosts MCP servers so you don't have to manage the infrastructure yourself.
No. The SDK abstracts the protocol details. If you can write a Python or TypeScript function, you can build a Toolcall server.
Any MCP-compatible client: Claude Desktop, Cursor, Cline, Continue, Zed, Windsurf, Codex CLI, and any custom client built against the MCP spec.
The core runtime is open source under Apache 2.0. Self-hosting is available on the Team plan with our deployment guides.
Hobby and Pro plans pause until the next billing cycle. Team plans auto-scale and bill the overage at $0.50 per 1,000 calls.
Team and Enterprise plans support custom transport implementations and OIDC, SAML, or custom auth providers.
// READY TO SHIP
START YOUR FIRST MCP SERVER
IN UNDER FIVE MINUTES
No credit card required. Hobby plan is free forever.