The MCP question to add to every SaaS renewal call this year

Most SaaS buyers spent the last decade asking their vendors three questions on the renewal call. Price, contract term, what is in the next release. The fourth question most teams should be asking in 2026 is missing from almost every procurement playbook I have seen this year, and the cost of not asking it is going to show up in the integration line of your engineering budget for the next twelve months.

The question is about the Model Context Protocol. The public MCP server registry grew from roughly 1,200 servers in the first quarter of 2025 to more than 9,400 by April 2026. Anthropic's SDK is doing nearly 100 million monthly downloads. Forrester is projecting that 30% of enterprise application vendors will publish their own MCP servers before the end of this year. The early ones have already shipped. GitHub, Stripe, Notion, Slack, Microsoft 365, Google Drive, Zendesk, Intercom, Snowflake, Datadog, Linear. Most of them are not selling it as a feature on their marketing pages yet, because they are still treating it as a developer story.

It is not a developer story. It is a procurement story. And almost nobody is asking about it on the renewal call.

What MCP actually changes for a buyer

Skip the protocol spec. The thing a buyer needs to understand is that the integration cost for an MCP-compliant SaaS tool is roughly an order of magnitude lower than for a tool without one. Before MCP, connecting a new agent or AI workflow to a SaaS system meant writing a custom connector, maintaining it, updating it when the vendor changed their API, and paying an engineer or a consultant to do all of that. Realistic cost floor on a real integration was four to six weeks of engineering time. Realistic ongoing cost was a few hours a month of maintenance per integration.

With a vendor-shipped MCP server, the same integration is configuration. An afternoon to wire it into your agent platform. Auth comes from OAuth. The tool list, the descriptions, and the schemas come from the server itself. Updates roll out server-side. You do not maintain a connector. You consume one.

That difference does not show up in your monthly SaaS bill. It shows up in your engineering capacity. Every MCP-compliant tool in your stack is one fewer connector your team has to own. Every tool that does not have an MCP server is one more piece of custom plumbing you are betting will still work twelve months from now.

The renewal call is the leverage moment. The contract is open. The vendor is paying attention. Asking the question costs nothing. Not asking it sets your integration budget on a path that is going to look very different a year from now than the path your competitor is on.

The question to add

Three parts, in this order, on every renewal call.

One. When is your MCP server shipping?If the answer is "it already shipped," get the URL and the date it went GA. If the answer is "on the roadmap for this year," get the quarter and the named owner. If the answer is "we have no plans," mark the contract.

Two. What is the auth model?OAuth is the right answer in 2026. If the answer is API keys, that is a yellow flag. If the answer is "static client secret," ask whether SSO integration is on the roadmap, because every enterprise IT team is going to require it within twelve months and the vendors that lag will get repriced or replaced. Anthropic's 2026 MCP roadmap calls out SSO-integrated auth as the top enterprise request, and it is going to settle into the protocol fast.

Three. What scopes does the server expose? This is where most renewal conversations end abruptly, because most vendors who shipped an MCP server last year exposed one scope and called it done. The current state of the protocol is that OAuth scopes authorize access to the server, not to individual tools inside it. That means if your agent has a credential good enough to read your invoices, the same credential is good enough to issue refunds. Vendors who are taking this seriously are moving to per-tool scoping or capability tokens. Vendors who are not, are leaving you with the same broad-permission problem that wiped a production database in nine seconds last month. Ask the question on the renewal call. Write down the answer.

How to read the answer

Three shapes, three different procurement responses.

The shipped, OAuth-with-scopes answer. Renew with confidence. Get the URL into your tool registry. Add the MCP server to your agent setup in the afternoon you have free this quarter. The vendor is on the right side of where the market is moving. Their integration cost curve is collapsing in your favor.

The roadmap-this-year answer. Renew, but put the vendor on a six-month watch. Note the named owner and the committed quarter. If you do not see the server ship by the date they gave you, escalate before the next renewal. A clear roadmap with an owner usually ships. A roadmap from a vendor who could not name an owner usually does not.

The silence answer. Start looking. A vendor with no MCP plan in mid-2026 is making a bet that their existing API and their existing market position will hold long enough to wait out the protocol. Sometimes that bet is right. More often the vendor is running a different playbook than the one your stack will be on next year. Spend an hour evaluating one or two alternatives in the same category. You do not have to switch. You have to know the cost of staying.

What to do when the critical tool is in the silence column

Most stacks have one or two systems of record that cannot be swapped easily. A CRM with seven years of data in it. An ERP. A custom-fit vertical SaaS that does something nobody else does. If one of those is in the silence column, the right move is not to switch. It is to bridge.

Three options, in order of cost.

Build a thin connector yourself. A read-only MCP wrapper around the vendor's REST API is a one-day project for a senior engineer. The MCP SDK does most of the work. You get the integration shape you want without waiting for the vendor.

Pay a consultancy to do it. A few thousand dollars buys you a maintained connector with auth and scoping handled correctly, plus updates when the vendor's API changes. Cheaper than your own engineer if the integration is not part of your core product.

Wait, and use the renewal as leverage next cycle. Tell the vendor on the next renewal call that the missing MCP server is a competitive risk for them. Most product teams hear that for the third time and put it on the roadmap.

Pick one. The wrong answer is to keep maintaining the bespoke connector you already have, hoping the vendor catches up before it breaks.

A 30-minute exercise to run this week

Open a spreadsheet. List your top ten SaaS tools by annual spend. For each one, write the answer to one question: does it have a public MCP server today?

Three buckets. Shipped, on roadmap, silent. The shipped column is easy to confirm, either from the vendor's docs or from the public MCP registry. The roadmap column is harder, because most vendors have not made a public commitment yet. Email your account manager. The silent column is the one to count.

Count the silent column. If it is zero or one, your stack is on the right side of where things are moving and the renewal calls this year are routine. If it is three or more, your integration budget is going to feel slow inside a year, and the renewal calls coming up are the leverage you have. Use them.

The buyers who are asking this question on their renewal calls right now are setting up their integration cost curve for the next two years to bend in their favor. The ones who are not, are paying for the gap with engineering time. The question takes less than a minute to ask. The answer shapes the next twelve months of your stack.

If you're heading into a renewal cycle and want a second pair of eyes on the MCP posture of your top vendors, or if you're trying to figure out whether to build a thin connector or wait, reach out. We run this check for clients before contract calls.