Who can build a custom MCP server or Claude connector for my company's software?

Four kinds of builder. An integration platform such as Zapier MCP or Composio, when your tools are popular SaaS products it already supports. A freelance developer, for one read-only connection or a proof of concept. A development company that builds MCP servers, such as Reflekt Lab, when the server must sign each user in, respect permissions, write safely, reach in-house or legacy systems and be run in production. Or your own engineering team, with the official MCP SDKs, if it has time to maintain the server as the specification changes. At Reflekt Lab, scoping costs $2,300 to $4,700 and a first workflow in production starts at $17,500.

Can I connect my in-house software to Claude without building an MCP server?

Sometimes. If it is a popular SaaS product, check first for an official connector or an integration platform: Zapier MCP is included in every Zapier plan and uses two tasks per tool call, and Composio has a free tier. For software built in-house, a legacy ERP or a database, nothing off the shelf knows your data model, so someone has to build the server.

What should I require from whoever builds my MCP server?

A remote server Claude can reach over HTTPS; per-user sign-in with OAuth rather than one shared key; tools scoped to the tasks you named, with permissions that match each user; a preview and confirmation before any write; logs of every call; tests; the source code, documentation and accounts in your company's name; and a maintenance plan with a monthly price, because the MCP specification and your own APIs will change.

How much does it cost to have an MCP server built?

Agency cost guides published in 2026 range from about $3,000 to $8,000 for a simple single-tool server, $8,000 to $25,000 and more with authentication and permissions, and $35,000 to $90,000 for several systems with write access. At Reflekt Lab, scoping one workflow costs $2,300 to $4,700, a first workflow in production starts at $17,500, and running it starts at about $470 a month plus $50 to $100 of hosting.

Can our own developers build an MCP server?

Yes. With the official SDKs, a local read-only server over one API is a short project. The weeks go into what production needs: remote hosting, OAuth sign-in, permissions per user, safe writes, monitoring, and keeping up with a specification that was revised three times in 2025 and again in July 2026.

Who Can Build a Custom MCP Server? Your Options (2026)

Four different workbenches around one socket: a box of ready-made plugs, a single craftsman's bench, a small workshop with several stations, and an in-house desk with a manual, all wired to the same port

Four kinds of builder can connect Claude to your company's software: an integration platform, a freelance developer, a development company that builds MCP servers, or your own engineering team. Which one fits depends on two questions: is your software a popular product a platform already supports, and will the AI only read, or also change records for several people? I run a company that builds MCP servers, so weigh what follows accordingly. I have tried to say plainly when you do not need us.

The four options, compared

Builder	What it costs	Good for	Not enough when
An integration platform	Zapier MCP is included in every Zapier plan and uses two tasks per tool call; Composio has a free tier and a $29-a-month plan	Popular SaaS tools the platform already connects	Your software is in-house or legacy, or you need your own permission rules
A freelance developer	Hourly or a fixed package; marketplaces list MCP server packages	One read-only connection, a proof of concept	Several users sign in, the AI writes, or someone must run it next year
A development company	Agency guides quote about $3,000 to $8,000 for a simple server, $8,000 to $25,000 and more with authentication, $35,000 to $90,000 for several systems with writes (sources)	Production: per-user sign-in, permissions, safe writes, in-house systems, monitoring	The job is one tool for one person
Your own team	Engineering time, with the official SDKs	Teams with time to maintain it, and a system they know	Nobody owns it after the first version

The cheapest path is to go down that list only as far as you need. If Claude already has a connector for your tool, or a platform covers it, use that.

When an integration platform is enough

If the software you want Claude to use is a well-known SaaS product, check three things before paying anyone:

An official connector. Many products now ship one: Salesforce hosts its own MCP servers (how to connect them), and QuickBooks Online, GitHub and many other SaaS tools ship official servers or connectors.
An integration platform. Zapier MCP and Composio wrap thousands of apps behind one MCP endpoint, with the sign-in handled for you.
Whether it does the actions you need. A connector that can read invoices but not create them may still leave the important part undone.

A platform stops being enough when the system is yours: an in-house application, a legacy ERP, a database, a desktop product with no web API. No platform knows your data model, your business rules or who in your company may change what.

When you need someone to build it

A built server is worth paying for when at least one of these is true:

The system is in-house or legacy. Nothing off the shelf talks to it, and often there is no clean API either, so the server needs an adapter first.
Several people will use it. Each should sign in as themselves, through OAuth, and see only what their role allows. A shared key is the shortcut that turns into a security incident (what MCP OAuth involves).
The AI will change records. Writes need a preview and a confirmation the person actually reads, and sometimes a question back mid-task.
It has to keep working. The MCP specification was revised in March, June and November 2025 and again in July 2026, and the AI clients follow the newest version. A server nobody maintains eventually stops connecting.

What to require, whoever you hire

Put these in the scope and the contract:

A remote server reachable over HTTPS, so it works in Claude on the web, desktop and mobile, not only on one laptop (what hosting one takes).
Per-user sign-in with OAuth, and permissions that match each person's role in your software.
Tools named for the tasks you listed, with typed inputs, not a generic "run any query" tool.
A preview before every write, and a confirmation step for anything that touches money or customers.
Logs of every call, who made it and what it changed (how we lock servers down).
Tests, including what happens when your system is slow or down.
Ownership: the source code, documentation, hosting accounts and keys in your company's name.
A maintenance plan with a monthly price, covering specification changes and changes to your own APIs.

A builder who cannot show you a server they run in production today is learning on your project. Ask to see one.

What we build

We design, build, host and run MCP servers for other companies' software, and we run our own every day: around 195 tools on one server, for our CRM, an order bot and internal agents (six servers we run, with their real tools). Among them: a catalog server for a travel marketplace, and a pricing server for an online store where prices change only through a sheet a person previews and approves.

Our prices are published: scoping one workflow costs $2,300 to $4,700, a first workflow in production starts at $17,500 and typically takes 2 to 4 weeks, and running it starts at about $470 a month plus $50 to $100 of hosting (the full breakdown). If an official connector or a platform already covers what you need, we will tell you on the first call.

If you would rather build it yourselves, our step-by-step guide builds one in Go, and adding it to Claude takes three steps.

Who Can Build a Custom MCP Server or Claude Connector?

Four kinds of builder can connect Claude to your company's software, and they are not interchangeable. Here is what each costs, what each is good for, and the list of things to require whoever you hire.