ToolBridge
Every business running AI agents needs custom MCP servers to connect them to their internal systems. You can build those. $2,000 per server, $299/month to maintain, first client in a week.
The Idea
Model Context Protocol (MCP) is Anthropic's open standard for connecting AI agents to external data sources and tools. Every major AI coding tool now supports it: Claude, Cursor, GitHub Copilot. A company running Claude internally can connect it to their CRM, internal database, customer support tickets, or proprietary API through an MCP server, making their AI agent genuinely useful instead of just clever. The problem: most businesses want this capability but have no idea how to build an MCP server. ToolBridge is a boutique MCP development agency. You build custom MCP servers for businesses, charge $1,500 to $3,000 per build, and $299/month per server for hosting and maintenance. Clients get an AI agent that actually knows their business. You collect recurring revenue for keeping it running.
Why Now
The MCP ecosystem went from zero to critical mass in under 18 months. Anthropic released the protocol in November 2024. By April 2026, there are over 5,000 MCP servers in public registries. Claude Code, Cursor, and GitHub Copilot all have native MCP support. Enterprise demand is spiking: McKinsey estimated in February 2026 that companies with AI tools deeply integrated into internal systems see 3 to 4 times the productivity gains versus generic AI deployments. That integration layer is MCP. The skillset to build MCP servers well is still rare; it requires understanding both the protocol internals and the business system being connected. Most developers are still learning the spec. The window where this skill commands premium rates is open now and will narrow in 12 to 18 months as the tooling matures and the skill becomes commoditised.
How to Build
The MCP SDK is the foundation, available for TypeScript and Python. An MCP server exposes tools (functions the AI can call), resources (data the AI can read), and prompts (templated interactions). For a CRM integration, you'd expose tools like search_contacts, create_deal, and update_status, alongside a customer_history resource. A typical server is 200 to 400 lines of TypeScript. Week one: build two portfolio MCP servers, one connecting to a popular tool like HubSpot or Shopify orders, and one connecting to a generic SQL database. Publish both to GitHub. This is your portfolio. Week two: outreach to small businesses running Claude or Cursor and offer a free discovery call. Document their workflow gaps and propose a custom MCP server to close each one. Scope each project to 3 to 5 tools and one resource endpoint. That is a clean deliverable and a 3 to 5 day build. Claude itself writes most of the boilerplate once you give it the target API documentation.
Revenue Model
Setup fee of $1,500 to $3,000 per MCP server depending on complexity and number of tools exposed. Monthly maintenance at $199 to $399 per server covering hosting on Railway or Fly.io, monitoring, and updates when the client's underlying API changes. At 10 maintained servers, that is $2,000 to $4,000 per month in recurring revenue before any new builds. Passive income channel: publish generic MCP servers (HubSpot, Shopify, Notion integrations) to the Apify marketplace and mcpize.com. Apify's pay-per-event model pays on usage, with 85% revenue share on MCPize. A popular generic integration generates $200 to $800 per month in passive income with zero ongoing work once published.
Effort
1 week to first paying client. Day 1 to 2: build the HubSpot and SQL portfolio servers. Day 3: set up a simple landing page with two portfolio examples and a "book a discovery call" CTA. Day 4 to 5: outreach. Search LinkedIn for "Head of Operations" or "CTO" at 10 to 50 person companies that mention Cursor, Claude, or Copilot in recent job listings. That signals active AI adoption. Send 20 personalised messages referencing one specific workflow gap you suspect they have. Close at least one discovery call. Day 6 to 7: scoped proposal and first build begins. The documentation work is minimal because Claude can generate the MCP server boilerplate from API documentation in under an hour.
Risk
Two real risks. First, the commoditisation timeline is aggressive. In 12 to 18 months, no-code MCP builders will exist and the barrier to entry collapses. Build recurring maintenance revenue now and move upmarket to complex enterprise integrations before the commodity tier cannibalises the simple work. Second, client dependency on your custom server creates retention but also support burden. If their CRM updates an API endpoint and your server breaks, you get a call at 10pm. Solid monitoring via Uptime Robot or Better Stack, clear SLAs in the contract, and a 48-hour response guarantee make this manageable rather than chaotic.
How to Market It
Cold outreach on LinkedIn is the primary channel. Search for "Head of AI", "AI Engineer", or "CTO" at 10 to 100 person companies. Check their job listings for mentions of Claude, Cursor, or Copilot: that signals they are already buying into the ecosystem. Opening line: "I noticed you're running [tool]. I build custom MCP servers that connect it to your internal systems in 3 to 5 days. Happy to share what I built for two similar companies." Attach a portfolio screenshot. Second channel: the MCP and AI agent communities. Post your portfolio servers to r/ClaudeAI and r/cursor, the Anthropic developer Discord, and the Cursor community Discord. A genuinely useful server with clean documentation gets upvotes and inbound DMs from people who immediately see the business application. Third, publish your generic servers to Apify and mcpize.com. Each published server is a distribution node: developers who find it on a marketplace become warm leads for custom work. Fourth, write one blog post per week on a specific integration (HubSpot MCP server tutorial, Shopify MCP walkthrough). These rank fast for low-competition terms like "Claude HubSpot integration" and bring inbound leads with zero ongoing effort. Budget: zero for month one. The portfolio, the Discord posts, and the LinkedIn outreach are all free.
The MCP ecosystem is at the exact inflection point where specialist knowledge commands premium rates. The build is scoped, the client is identifiable, and the first project can close within a week of starting outreach. Maintenance revenue stacks quickly once you have 5 to 10 clients. The window narrows as the tooling matures, so move fast, document your process, and push upmarket toward complex enterprise integrations before the commodity tier eats the simple work. The passive income channel via marketplace-published servers is a genuine bonus. Build this.