In brief: A partner-built MCP server costs ~$100K–$300K for a level-1 read-only single-client app and ~$300K–$700K for a level-2 actions app; a second client adds 1.4–1.7×, and a level-3 agent-resident build starts at $1M+. In-house equivalents run 60–80% of partner cost in raw spend before opportunity cost. The number is driven by auth complexity, tool-surface size, your own product's complexity, multi-client overhead, and embedding depth – not by the server code itself. Budget $5K–$25K/month for ongoing maintenance on top of the build.
Building an MCP server costs between $100K and $1M+ in 2026, and the single biggest factor is how much the server is allowed to do. A read-only connector to one AI client runs $100K–$300K. A server that takes actions on a user's behalf runs $300K–$700K. An agent-resident rebuild starts at $1M. The server code itself is the cheap part – auth, audit, the safety story, and distribution are where the budget actually goes.
MCP servers are almost never priced as a license – the protocol is open and no major AI client has first-class paid-app billing yet – so "MCP server pricing" means the build ($100K–$1M+ by scope), the retainer that follows it ($5K–$25K/month), and the underlying API and token costs that land on whoever uses it.
| What you are pricing | 2026 figure |
|---|---|
| Level-1 read-only server, one client, partner-built | $100K–$300K |
| Level-2 actions server, one client, partner-built | $300K–$700K |
| Second client | 1.4–1.7× the single-client total ($420K–$1.2M at level 2) |
| Security and auth line items in a level-2 build | OAuth $60K–$120K · audit log $40K–$80K · third-party pen test $30K · first-time SOC 2 Type II $50K–$150K |
| Ongoing maintenance | $5K–$25K/month retainer, plus ~$20K/year hosting |
| Fee to install or use the server | None – the cost is the underlying service's API plan, the AI client's token bill, and hosting; see MCP server pricing below |
Those ranges come from the same place every figure in this guide does: real 2026 partner engagements and in-house builds, cross-checked against our MCP build vs buy analysis. This guide breaks the number down – what you are paying for, how scope moves it, what it looks like in-house versus with a partner, and three worked examples at different sizes. If you are still deciding whether to ship to AI clients at all, start with the MCP strategy decision framework; if you have decided and are choosing who builds it, see how to evaluate an MCP build partner.
The Estimate That Wrecks the Budget
Almost every blown MCP budget starts with an undersized estimate. A serious MCP server shipped to one client at actions depth is not a two-week sprint and not a single-engineer project. Teams that scope it that way routinely discover by month three that they are short two engineers and a designer, and by month six that the first ship will not clear the safety bar enterprise procurement asks about. The number below is what it costs to do it once, correctly, instead of twice.
What Goes Into an MCP Server Build
When you budget for an MCP server, you are budgeting for seven things, and only one of them is the server. A complete level-2 (actions) build for a single client is one to two quarters of work for a properly staffed team. The scope:
- Server implementation – the process, hosting, observability, and deployment pipeline, built to the MCP spec (JSON-RPC 2.0 over stdio, SSE, or streamable HTTP).
-
Tool surface design – the
create_,update_,search_, andget_operations, each named and documented with the precision of a public API, because an agent reads the names to decide what to call. - Auth implementation – OAuth 2.1 + PKCE, typically with Dynamic Client Registration and authorization-server metadata, plus a scope taxonomy, token lifetimes, refresh, and revocation. This is one of the largest line items, and it is covered in depth in MCP auth and security.
- Audit and logging surface – per-invocation logs, parameter capture, session reconstruction, and a customer-admin-facing view of what the agent did.
- Safety story – idempotency keys, reversibility patterns (soft delete, revision history), and intent-preview-friendly parameter shapes. The depth required here scales with embedding level: read-only barely needs it, actions cannot ship without it.
- Distribution package – submission to the host client's marketplace, store metadata, screenshots, documentation, and a support workflow.
- Maintenance commitment – keeping up with the host client's spec, auth, and distribution-policy changes, plus your own evolving tool surface, indefinitely.
That list is the work for one client. The server code – item one – is genuinely the cheap part. Auth, audit, and the safety story are where a six-figure budget is spent, because they are the difference between a prototype that demos well and a product that survives a security review.
Cost Ranges by Scope
Scope is the master lever. "Scope" here means two things: how much the server is allowed to do (its embedding level) and how many AI clients you ship to. The rough envelopes for partner-built MCP servers in 2026:
| Scope | Calendar time | Partner cost (USD) | In-house (raw spend) |
|---|---|---|---|
| Level-1 read-only, single client | ~1 quarter | $100K–$300K | $80K–$240K |
| Level-2 actions, single client | ~2 quarters | $300K–$700K | $200K–$520K |
| Level-2 actions, two clients | ~2.5–3 quarters | $420K–$1.2M | $300K–$900K |
| Level-3 agent-resident | Multi-quarter program | $1M+ | $700K+ |
Level-1 read-only lets an agent search and retrieve from your product but never change anything. The safety surface is small, so this is the cheapest serious ship. The bottom of the range – roughly $100K–$150K – buys a single client, 5–10 carefully chosen tools, OAuth 2.1 + PKCE + DCR, and basic audit logging.
Level-2 actions lets the agent create, update, and delete on the user's behalf. That single capability change roughly doubles the cost, because every write operation needs idempotency, reversibility, and an intent-preview-friendly shape, and the audit log moves from nice-to-have to mandatory.
Two clients is not double the work, but it is not free either. A second client adds 1.4–1.7× the single-client cost – different auth, different distribution, different terminology, different review process. You are porting a working design, not rebuilding it, but each surface wants to be excellent on its own terms.
Level-3 agent-resident is a different category: rebuilding the product so an agent can operate it end to end. It is a multi-quarter program starting at $1M, and most teams should not start here. The embedding types guide covers when level-3 is justified – almost always only when the company is rebuilding around an agent-first thesis.
Line-Item Cost Breakdown
Ranges are useful for a board slide; line items are what you negotiate against. Here is a representative breakdown for a level-2 single-client partner build at the middle of its range (about $500K total):
| Component | Typical cost (USD) | What it covers |
|---|---|---|
| Discovery, design, scope taxonomy | $40K–$80K | Posture review, embedding-level decision, scope design, tool-surface specification |
| Server implementation, hosting, observability | $50K–$100K | MCP spec implementation, transport, hosting infra, monitoring |
| Tool surface (10–25 tools) | $80K–$180K | Implementation, validation, testing, and documentation per tool |
| OAuth implementation, scope design | $60K–$120K | OAuth 2.1 + PKCE + DCR, scope taxonomy, token lifecycle, revocation |
| Audit log + customer-admin surface | $40K–$80K | Per-invocation logging, tamper-evident storage, admin UI |
| Safety story | $60K–$120K | Idempotency keys, soft-delete and restore, revision history, intent preview |
| Marketplace submission, distribution polish | $20K–$50K | Listing copy, screenshots, review iteration, documentation |
| Project management, knowledge transfer, contingency | $40K–$80K | PM overhead, runbooks, pairing engagements, buffer |
The two line items that dominate are the tool surface and the safety story. The tool surface is expensive because each tool is a small public API – it gets implemented, validated, tested, and documented, and an agent's willingness to call it depends on how well the last two are done. The safety story is expensive for the same reason auth is: it is invisible when it works and catastrophic when it does not. A proposal that lists these two as small numbers is a proposal that has not thought about write operations.
Questions to Ask a Proposal
Ask any partner to break the build into line items matching the table above. What does "auth design complete" mean as an acceptance criterion? Is the third-party penetration test in scope or extra? Who owns the code, and from what date? Does the safety story include reversibility for every write tool, or only some? A transparent, line-itemed proposal is a real estimate. A vague lump sum is padding or guessing – and you cannot tell which until it is too late.
In-House vs Partner and Break-Even
The instinct is that in-house must be cheaper, and in raw dollars it is – about 60–80% of partner cost. (If the partner route wins for you, how to choose an AI development partner covers the selection side.) Here is the same level-2 scope, staffed internally:
| Component | Typical cost (USD) |
|---|---|
| 1 PM @ 75% × 26 weeks | $50K |
| 1 tech lead @ 75% × 26 weeks | $60K |
| 2 senior backend engineers × 26 weeks | $130K |
| 1 mid backend engineer × 20 weeks | $50K |
| Designer @ 30% × 16 weeks | $20K |
| Security engineer @ 30% × 12 weeks | $15K |
| DevOps @ 25% × 16 weeks | $15K |
| Technical writer @ 30% × 8 weeks | $10K |
| Hosting + tooling | $20K |
| Penetration test (third party) | $30K |
| Total | ~$400K |
So in-house lands near $400K against a $500K partner mid-point – a real gap of $100K in raw spend. The catch is that the gap closes, and often reverses, once opportunity cost is counted. Those four-plus engineers are not idle; they are pulled off the roadmap. If the delayed features, missed customer commitments, and slowed pipeline add up to more than ~$100K in value, the partner wins on total cost. For most growth-stage SaaS companies, they do. For more mature companies with genuine slack capacity, in-house wins.
There is also a calendar-time gap the dollars hide: a partner ships in roughly six months, an in-house team running its first MCP build in seven to eight. The full build-versus-buy decision – including the hybrid models that consistently work – is the subject of MCP build vs buy. The cost framing here is the input to that decision, not a substitute for it.
The False Economy
The most expensive MCP build is the one staffed thinly to "save money." One engineer, part-time, no security review, audit log as a TODO. By month three the team has half a server. By month six the company is hiring or hiring a partner anyway, and the rework – roughly 30–50% of the in-progress code – is on top of the original spend. Picking the right path before staffing is the cheapest decision in the whole project. Picking it after is the most expensive.
Three Worked Examples
Ranges land better against concrete shapes. Three teams, three budgets.
Small SaaS shipping a read-only Claude connector. A 30-person SaaS wants its data searchable inside Claude – no writes, one client, a focused tool surface of 6–8 read tools. This is the cheapest serious ship: level-1, single client, OAuth 2.1 + PKCE + DCR, basic audit logging. Budget $100K–$150K partner-built, one quarter of calendar time. The temptation is to add write tools "while we're in there." Resist it – that decision moves the project into the next tier.
Mid-market SaaS shipping level-2 actions to Claude and ChatGPT. A 200-person SaaS wants agents to create and update records, and it wants to be in both Claude and ChatGPT at launch. That is level-2 actions across two clients. Build the first client fully ($300K–$700K), then add the second at 1.4–1.7× the single-client cost. Plan for $420K–$1.2M and 2.5–3 quarters. Ship the strategic client first and port what works rather than abstracting across both from day one – the cross-client abstraction is what produces a server that is mediocre on every surface.
Enterprise SaaS shipping level-2 to Microsoft Copilot via AppSource. A large SaaS wants actions inside Microsoft Copilot, distributed through AppSource. The build itself is level-2 single-client: $300K–$700K. Two enterprise-specific costs sit on top. First, the AppSource review and listing process adds calendar time – plan for a 6–12 week review window, per the MCP client comparison, and budget the iteration. Second, enterprise procurement will ask for SOC 2; first-time SOC 2 Type II attestation typically runs $50K–$150K over 6–9 months, per MCP auth and security. If you are not already attested, that is part of the true cost of shipping to an enterprise client.
Ongoing Operational Costs
The build is a one-time number. The MCP server is not. Three recurring costs outlive the launch:
- Hosting and tooling – roughly $20K/year for a single-client production server, scaling with traffic and client count.
- Maintenance retainer – $5K–$25K/month, depending on complexity and number of clients. A good retainer covers host-client spec changes, auth-model changes, distribution-policy changes, security patches, and minor feature work. Watch for a retainer that covers nothing actionable – maintenance that is real work, not a line item.
- Spec-change upkeep – the host clients you ship to keep changing. New spec versions, new auth requirements, new marketplace policies. A partner whose business is MCP absorbs these across many clients; an internal team treats each as an unplanned project. This is a cost either way; the only question is whether it is amortized or absorbed.
The honest framing: an MCP server is a product with an indefinite maintenance commitment, not a project that ends at launch. Budget for the retainer from day one, because the alternative – letting the server drift out of spec until it breaks – is more expensive and worse for the buyers who came to depend on it.
MCP Server Pricing: Do MCP Servers Cost Money to Use?
Most MCP servers are free to install and the protocol itself costs nothing – Anthropic open-sourced it in November 2024, and as of 2026 no major AI client has shipped a first-class paid-app billing pathway (see the MCP client comparison). So "MCP server pricing" is almost never a license fee. The money lands in three other places. First, the underlying service: the server is a thin door into a product, and that product's API is often gated to a paid plan or metered per call, so the API keys behind the server carry the real price. Second, tokens in the AI client: every tool definition and every tool result is fed to the model as input, billed at the model provider's per-token rate on each turn – roughly $3 per million input tokens for a frontier model, per the run-cost math in the AI implementation cost guide. A server with thirty verbose tools taxes every conversation it is installed in, whether or not a tool is called. Third, hosting, if the server is remote – small for a local stdio server, ~$20K/year for a production single-client server as above. If you are the vendor, the fourth cost is this guide: the build and the retainer.
| Where the money goes | Who pays | Typical shape |
|---|---|---|
| Protocol and server software | Nobody | Open spec; most servers open-source or bundled free |
| Underlying service API | The user's company | Paid plan tier or per-call API metering |
| Tokens in the AI client | The user's model bill | Per-token; tool definitions + results count as input on every turn |
| Hosting (remote servers) | The vendor | ~$20K/year for a production single-client server |
| Build and maintenance | The vendor | $100K–$1M+ build, $5K–$25K/month retainer |
What Drives MCP Server Cost Up or Down
Five levers move the number more than any others. Knowing them lets you keep a build at the bottom of its range instead of the top:
- Auth complexity. Basic OAuth with a handful of scopes is cheap. Fine-grained scopes, enterprise SSO, and per-client auth paths are not. Fine-grained scopes cost more up front but move enterprise procurement faster – a trade-off, not waste.
- Tool-surface size. Each tool is implemented, validated, tested, and documented. Ten well-chosen tools cost far less than thirty mediocre ones, and agents call a tight surface more reliably.
- Underlying product complexity. A clean, well-modeled product is cheap to expose. A tangled data model or brittle internal API means the MCP build pays to work around it – sometimes more than the server itself costs.
- Multi-client overhead. Every additional client is a partial rebuild at 30–60% of the first ship. Shipping to one client excellently is cheaper and better than shipping to three clients adequately.
- Embedding depth. Read-only is cheap; actions roughly double it; agent-resident is a different category entirely. The single largest decision you make about cost is how much the server is allowed to do.
The teams that come in at the bottom of the range are not cutting corners – they are scoping deliberately: one client, a tight tool surface, the embedding level the use case actually needs, and a clean product underneath. The teams that come in at the top usually got there by abstracting across clients too early or shipping write tools without a safety story, then paying to fix both.
Related Guides
- MCP Build vs Buy: Should You Hire a Partner or Build In-House? – The decision this cost model feeds into
- How to Embed Your App in AI Clients with MCP – The complete build playbook for product leaders
- MCP Embedding Types: Read-Only vs Actions vs Agent-Resident – The embedding-level decision that drives most of the cost
- MCP Auth and Security – Why auth is one of the largest line items
- MCP Client Comparison – Per-client distribution, review timelines, and monetization
- How to Evaluate an MCP Build Partner – Pressure-testing a quote against defensible ranges
- AI Implementation Cost: A Buyer's Cost Model – The broader AI budget this sits inside
Frequently Asked Questions
How much does it cost to build an MCP server?
In 2026, a partner-built MCP server costs $100K–$300K for a level-1 read-only single-client app and $300K–$700K for a level-2 actions app. A second client adds 1.4–1.7×, and a level-3 agent-resident build starts at $1M+. In-house equivalents run 60–80% of partner cost in raw spend.
How much does an MCP server cost?
The build ranges from $100K to $1M+ depending on scope. Read-only single-client sits at the bottom ($100K–$300K), actions in the middle ($300K–$700K), and agent-resident at the top ($1M+). On top of the build, plan $5K–$25K per month for ongoing maintenance.
What's the cheapest way to build an MCP server?
Level-1 read-only, a single client (usually Claude or ChatGPT), 5–10 carefully chosen tools, OAuth 2.1 + PKCE + DCR, and basic audit logging. Partner-built, that is the bottom of the range at roughly $100K–$150K. In-house with experienced staff, less in raw spend but with longer calendar time.
How much does a level-2 (actions) MCP server cost?
A level-2 actions MCP server for a single client costs $300K–$700K partner-built, with a representative mid-point around $500K. The two largest line items are the tool surface ($80K–$180K) and the safety story ($60K–$120K) – idempotency, reversibility, and intent preview for write operations.
Is it cheaper to build an MCP server in-house or hire a partner?
In-house is cheaper in raw spend – about 60–80% of partner cost – but the gap narrows once you count the opportunity cost of pulling engineers off the roadmap. If that opportunity cost exceeds ~$100K, the partner usually wins on total cost. For most growth-stage SaaS teams, it does.
How much does MCP development cost per client?
The first client carries the full build cost. Each additional client adds roughly 30–60% of the first ship – different auth, distribution, terminology, and review process per client. Two clients at level-2 typically land at 1.4–1.7× the single-client cost, or about $420K–$1.2M.
What are the ongoing costs of running an MCP server?
Hosting and tooling (roughly $20K/year), plus a maintenance retainer of $5K–$25K/month covering host-client spec changes, auth changes, distribution-policy changes, security patches, and minor feature work. The maintenance is indefinite – the clients you ship to keep changing their specs.
Do MCP servers cost money to use?
Usually not as a license fee – the protocol is open and no major AI client has first-class paid-app billing yet. The real costs are the underlying service's API plan, the tokens the AI client spends on tool definitions and results every turn, and hosting for remote servers. Vendors additionally pay to build and maintain the server.
What drives MCP server cost up?
Five things: auth complexity (fine-grained scopes, enterprise SSO), tool-surface size (more tools, more testing), the complexity of your own product, multi-client overhead (each client is a partial rebuild), and embedding depth (read-only is cheap, actions and agent-resident are not).
Originally published at launchdayadvisors.com. Launch Day Advisors is a buyer-side advisory firm: we help companies select AI, software, and design partners, and we are paid only by the buyer.
Top comments (0)