MCP Ecosystem Structure

What is it

MCP stands for Model Context Protocol — an open standard, originally introduced by Anthropic in late 2024, that defines how AI models talk to external tools, data sources, and services. Think of it as "USB-C for AI agents": instead of every LLM vendor inventing its own plugin format, MCP gives a single wire protocol so any compliant client (Claude Desktop, Cursor, custom agents) can call any compliant server.

"MCP Ecosystem Structure" refers to the emerging map of that world: the hierarchy of clients, servers, registries, gateways, and tool marketplaces, plus academic attempts to classify what each layer does. The oschina and arxiv signals show two things happening at once — researchers are formally taxonomizing MCP's functional landscape, and shipping products like Termexo are already bundling 19 local MCP tools into a single package.

Business significance: whoever owns the discovery, distribution, or security layer of MCP tools captures recurring revenue from every agent that runs. This is the npm-for-AI moment, except the packages are live tools callable at runtime. That is a far more defensible position than building yet another thin GPT wrapper.

Why now

Three forces converged in 2025-2026. First, protocol maturity: MCP moved from a single-vendor spec to a de facto standard with multiple independent implementations, including OpenAI's adoption of MCP-compatible tool calling. Once a second major lab supports it, the "will this stick?" question dies.

Second, agent demand. Chat assistants are being replaced by autonomous agents that need to do things — read files, query databases, hit APIs, run code. Each capability requires a tool, and each tool needs a protocol. The number of tools is exploding faster than any single vendor can curate, which creates a discovery and packaging problem.

Third, the supply side got cheap. A solo developer can now write an MCP server in an afternoon (TypeScript or Python SDK, ~100 lines). Termexo shipping 19 local tools signals that aggregation — not individual tools — is the emerging product shape. Meanwhile, arxiv papers mapping MCP hierarchy mean the academic vocabulary is stabilizing, which usually precedes enterprise procurement language.

What makes this now and not next year: the tool count is crossing the threshold where manual configuration breaks down. That pain is the wedge. Next year the incumbents will have shipped their own registries; this year the lane is open.

Market Evidence

The evidence base is thin but directionally real. Two independent sources — oschina (a Chinese developer news portal) and arxiv (academic preprints) — picked up the same theme within the same window. Two mentions total, 100% growth rate, stage: nascent, trend score 60/100.

Read that honestly: this is an early signal, not a market. A 100% growth rate on a base of one mention is mathematically trivial. Two sources is the minimum for "not a single-source fluke." The trend score of 60/100 says "interesting, not urgent."

What makes it more than hype is the type of source. Academic taxonomies (arxiv) appear when a technology has enough real deployments to be worth classifying — researchers don't map vaporware hierarchies. Developer news coverage (oschina) appears when practitioners are actually building. Termexo's 19 shipped tools is concrete production evidence, not a roadmap promise.

The counterargument: MCP itself is a standard, and standards don't monetize directly. The opportunity is in the structure around MCP, not MCP. Treat the 2 mentions as a leading indicator for a wave arriving in 6-12 months, and use that window to build distribution before the wave lands. The Opportunity Score of 0/100 reflects that no monetizable product has crystallized yet — which is exactly why an indie developer can still define the category.

Who's Behind It

The whales are clear. Anthropic created MCP and controls the reference implementation and spec evolution. OpenAI adopted MCP-compatible tool calling, which legitimized it across the industry. Cursor and Claude Desktop are the dominant client surfaces today — whoever controls the client controls which servers get discovered.

On the tooling side, Termexo is the notable indie mover, shipping 19 local MCP tools as a bundle. That's a strong signal that aggregation is a viable indie play. Other players include Smithery and Glama (MCP server directories/registries), plus a long tail of solo developers publishing single-purpose servers on GitHub.

The academic contributors mapping MCP hierarchy are less commercially relevant but matter for vocabulary — their taxonomy will likely become how enterprises describe their requirements.

Competitive dynamic worth noting: Anthropic and OpenAI are cooperating on the protocol while competing on the client. That cooperation keeps the standard open, but the client competition means neither will build neutral, cross-client infrastructure. That neutrality gap is the indie opportunity — a registry or gateway that serves all clients is something no whale can credibly own.

TAM & Market Size

Buyers fall into three buckets. Individual developers and indie hackers — hundreds of thousands worldwide, already paying for Cursor ($20/mo), Claude Pro ($20/mo), and API credits. Price tolerance for a tooling add-on: $5-30/month. Small teams and startups building agent products — tens of thousands of companies, budget $100-500/month for infrastructure that saves engineering time. Enterprises adopting agents — thousands of orgs, but 12-18 month sales cycles and procurement overhead no indie should chase yet.

The honest TAM for an indie MCP product in 2026 is the first bucket plus the low end of the second: call it 50,000-200,000 reachable developers, with maybe 2-5% willing to pay for a genuinely useful tool. At $15/month average, that's a $1.5M-$18M annual ceiling for a category leader — real money for an indie, not a venture-scale outcome.

Both the Opportunity Score (0/100) and Demand Score (0/100) reflect that no one is searching for "MCP registry" yet. Demand is latent, not expressed. The buyers exist and have budget, but they don't yet know they need this. That means you can't run ads into existing search demand — you have to create the demand through content and community. Higher CAC, but also no bidding war.

Competitive Landscape

Direct competitors today are thin. Smithery and Glama run MCP server directories — essentially searchable lists. Both are early, both are free, neither has a clear monetization model. That's the tell: the discovery layer exists but nobody has figured out how to charge for it, which means the category is unproven and the pricing is unset.

Adjacent competitors are more dangerous. Anthropic could ship an official MCP registry inside Claude Desktop tomorrow and crush the indie directory plays. GitHub could add an "MCP" tab next to Actions. npm could absorb MCP packages as a namespace. Any of these would take the discovery layer off the table.

The gap: nobody is solving composition and trust. Finding one MCP server is easy. Finding five that work together, don't conflict, are maintained, and are safe to run is hard. Similarly, no one offers a managed gateway that handles auth, rate limiting, and audit logging across multiple MCP servers — the enterprise pain that will matter in 12 months.

Your window: roughly 6-9 months before a whale ships a registry. Differentiation must be in the layer above raw discovery — orchestration, security, or vertical-specific bundles. Competition Score 0/100 means the field is empty, but empty fields attract fast followers. Move now, own a niche, not the generic directory.

Business Model

Recommended: freemium SaaS with a usage-based API tier. The freemium tier (up to 3 MCP servers, community support) drives adoption and SEO. The paid tier ($19/month for individuals, $99/month for teams) unlocks unlimited servers, a hosted gateway, auth management, and audit logs. An API tier ($0.001-0.005 per tool call) captures agent builders whose usage scales unpredictably.

Why this fits: developers expect to try before paying, and MCP tooling is infrastructure they'll only pay for once it's load-bearing in their workflow. Usage-based pricing aligns your revenue with their success — critical in a category with no established willingness-to-pay.

Pricing rationale: $19/month sits just under Cursor's $20 and Claude Pro's $20, so it reads as "one more tool in the stack" rather than a new budget line. $99/month team tier matches GitHub Team and Vercel Pro, familiar anchors. Avoid $9/month — it signals hobbyist and attracts churn.

12-month revenue forecast (assuming launch in month 3):

• Conservative: 500 free users, 3% conversion = 15 paying × $19 = $285 MRR; ~$2,000 annualized.
• Base: 5,000 free users, 5% conversion = 250 paying, blended $30 ARPU = $7,500 MRR; ~$50,000 annualized.
• Optimistic: 20,000 free users, 6% conversion = 1,200 paying, blended $40 ARPU (team tier traction) = $48,000 MRR; ~$300,000 annualized.

CAC estimate: $30-80 via content and community (organic-heavy), $150-250 via paid. Payback period: 2-4 months on the $19 tier if churn stays under 5%/month. Churn is the killer — infrastructure tools that aren't load-bearing get cancelled fast.

MVP Blueprint

Scope: a hosted MCP gateway + registry in 5-7 days.

Core features only:

1. Registry — a searchable, curated list of MCP servers with metadata (capabilities, auth type, maintenance status). Seed it with 50-100 hand-curated entries, not an auto-scraper.
2. One-click connect — a hosted proxy that lets a user add an MCP server to their client via a single URL, handling auth and transport. This is the actual product; the registry is the funnel.
3. Health checks — automated pings that flag dead or broken servers. Trust is the moat.
4. Usage dashboard — calls per server, errors, latency. The hook for the paid tier.

Cut: team management, billing complexity, marketplace payments, self-hosted option, SSO. All of it can wait for paying customers.

Tech stack: Next.js (App Router) + Vercel for the frontend and registry. Supabase for auth, Postgres, and row-level security. A small Node/TypeScript service (Fly.io or Railway) for the gateway proxy — MCP's transport layer (stdio and HTTP/SSE) means you need a persistent process, not just serverless functions. Stripe for billing. Use the official MCP TypeScript SDK to avoid reinventing transport.

Fastest path to launch: Day 1-2, registry UI with hardcoded data. Day 3-4, gateway proxy supporting HTTP/SSE MCP servers with a single shared auth pattern. Day 5, Stripe checkout and usage logging. Day 6-7, polish, seed content, and post to Hacker News, r/LocalLLaMA, and the MCP Discord.

Ship the gateway, not the directory. Directories are commodities; a working proxy that removes configuration pain is a product.

Commercial Opportunities

1. Managed MCP gateway for teams. Target: 5-50 person AI startups running agents in production. They need auth, rate limiting, audit logs, and uptime across a dozen MCP servers, and they don't want to build it. Expected revenue: $99-499/month per team, 20-50 teams in year MRR. Beats a generic directory because it's load-bearing infrastructure with real switching costs.

2. Vertical MCP bundles. Package 10-15 MCP servers tuned for one workflow — e.g., "MCP for e-commerce ops" (Shopify, Stripe, inventory, shipping) or "MCP for data teams" (Postgres, Snowflake, dbt, S3). Target: non-technical operators and small agencies who want agents that just work. Expected revenue: $29-79/month, sold as a product not a platform. Beats horizontal plays because the buyer doesn't have to assemble anything.

3. MCP server monitoring and security. Target: enterprises and security-conscious teams. Scan MCP servers for prompt-injection vectors, excessive permissions, and unmaintained dependencies. Expected revenue: $199-999/month. This is the highest-value direction but the slowest to sell — start it only after you have gateway customers to upsell.

The gateway is the best first move: it's technical enough to build in a week, has a clear pain point, and creates the customer relationship the other two directions monetize.

Product Ideas

🥇 MCP Gateway (hosted proxy + registry). Value prop: "Add any MCP server to any AI client with one URL — no config files, no auth headaches." Target user: developers running Claude Desktop, Cursor, or custom agents who are tired of editing JSON. Why now: MCP client support is broad enough that config pain is universal, but no hosted neutral gateway exists. This is the beachhead.

🥈 Vertical MCP bundles. Value prop: "A complete, tested MCP toolkit for [industry] — install once, everything works together." Target user: ops managers, agency owners, and non-engineers building agents for a specific job. Why now: the long tail of MCP servers is fragmented and untested together; curation is the value. Sell at $49/month.

🥉 MCP Security Scanner. Value prop: "Audit your MCP servers for injection risks, over-permissioning, and supply-chain issues before your agent goes to production." Target user: security engineers at companies deploying agents. Why now: agent security is a known blind spot and no dedicated MCP scanner exists. Price at $299/month; this is a later-stage play once you have distribution.

Rank by build cost and time-to-revenue: the gateway wins on both. Bundles are a content play disguised as a product. The scanner is a trust play that requires credibility you'll earn from the first two.

SEO Opportunity

Search volume for "MCP" is growing fast but from a tiny base; "MCP server" and "Model Context Protocol" are the head terms, already contested by Anthropic's docs and GitHub. SEO difficulty: 0/100 per the data, but treat that as "unmeasured," not "easy" — it reflects an unindexed niche.

Target long-tail keywords with buying intent: "how to add MCP server to Cursor," "MCP server authentication," "best MCP servers for [use case]," "MCP gateway self-hosted," and "MCP server not working." These have low competition and high intent.

Content strategy: publish working tutorials, not thought leadership. Every post should end with a working config or a link to your gateway. Tutorials rank and convert; opinion pieces don't.

Risk Assessment

When this thesis is wrong: if MCP loses to a competing standard (OpenAI's earlier plugin format, or a proprietary alternative) the entire ecosystem map becomes moot. Watch for whether major clients keep shipping MCP support through 2026.

Risk 1 — Platform absorption (tech/market). Anthropic, OpenAI, or GitHub ships a free native registry or gateway. Mitigation: don't compete on discovery; compete on orchestration and security, which platforms are slower to build. If an official registry launches, pivot to being the enterprise layer on top of it.

Risk 2 — Demand never materializes (market). Developers tolerate config pain longer than you expect, and "good enough" free directories kill willingness to pay. Mitigation: validate willingness-to-pay before building — pre-sell the $19 tier to 10 people.

Risk 3 — Execution drag (execution). MCP transport is still evolving; you could spend months chasing spec changes. Mitigation: build on the official SDK and keep the gateway thin.

Cheap validation: spend $0 and one week. Post a landing page offering "hosted MCP gateway, $19/month, early access." Drive 200 visitors from MCP Discord and r/LocalLLaMA. If fewer than 20 people join the waitlist, walk away. If 20+ convert to a paid pre-order, build immediately.

Action Plan

Today: Join the official MCP Discord and r/LocalLLaMA. Read the MCP spec's transport section end to end. List 20 MCP servers you'd personally want to connect and note the config friction for each.

This week (low-cost validation): Ship a one-page landing site describing the hosted gateway. Include a Stripe pre-order button at $19/month with "early access." Post it in three communities with an honest "I'm building this, would you pay?" framing. Target: 200 visitors, 20 waitlist signups, 5 paid pre-orders. Cost: under $50 and 8 hours.

If signal confirms (20+ signups): Build the MVP in 5-7 days per the blueprint. Launch on Hacker News with a working demo, not a waitlist. Instrument everything — signups, activation (first server connected), and conversion.

Timeline:

• Week 1: validation landing page live, community presence established.
• Month 1: MVP shipped, first 10 paying customers, $190+ MRR.
• Month 3: 100+ paying customers, $2,000+ MRR, team tier launched, first enterprise conversation started.

Walk-away trigger: if week 1 produces fewer than 10 waitlist signups from 200 targeted visitors, the pain isn't acute enough. Stop and revisit in six months.

Related Terms

Agent tool calling — the broader capability MCP standardizes; every improvement here expands MCP's addressable surface. MCP server registry — the discovery layer that will either be commoditized by platforms or owned by an indie with better curation; watch it closely as a leading indicator. Agent security / prompt injection — the risk layer that makes a paid MCP gateway defensible, since free directories can't offer trust guarantees. Together these three form the stack: calling (protocol), finding (registry), and trusting (security). MCP Ecosystem Structure is the map that connects them.