Enterprise MCP

An MCP server is not a deployment.

The protocol is the easy part. Meetext adds the customer identity, frozen tool set, entitlements, credentials, validation and lifecycle an enterprise install needs.

Your existing code

Connect a source. Choose what ships.

Meetext / Customer deploymentExample

Capabilities, with boundaries.

MCP → customer-scoped tools

get_accountsReadApproved
update_accountWriteReview
delete_accountDestructiveBlocked

A source change never silently widens access.

Only what you approve goes out.
Illustrative capability review

The shape the problem actually has

One endpoint with your credential is what everybody builds first. It cannot scope, revoke or freeze anything per customer.

What most products shipOne endpoint, one credential
/mcp
Your API keyEvery tool

Every customer reaches the same surface with the same credential.

What Meetext servesOne endpoint per customer
/mcp/products/acme·Nike
workspace T04F212 tools
/mcp/products/acme·Adidas
workspace T7B916 tools
/mcp/products/acme·Visa
tenant 9c1e24 tools

Their grant, their entitled subset, their frozen version.

What is actually hard

One endpoint per customer, not one per product

Each customer environment gets its own MCP endpoint, so a token that belongs to Nike cannot list Adidas's capabilities.

The customer's grant, not yours

Meetext refreshes the customer's OAuth grant before expiry, per environment, and the customer revokes it when they choose.

Entitlement is not authentication

A customer who bought twelve capabilities sees twelve, which also narrows the permissions they are asked to grant.

A frozen tool list

A customer's tool set is frozen at install, so a new product version changes only what new customers get.

Schema changes revoke approval

If your upstream server changes a tool's input schema, the capability's approval is revoked rather than carried forward.

Proving it works

initialize succeeding proves the protocol works, not that a capability executes against your system with this customer's credentials.

Where MCP fits

MCP is one of several ways to describe what your product can do. Meetext normalises each into the same capability format, so adding a source later is an addition rather than a rewrite.

Hosted connectors are not yet proven

The endpoint speaks the protocol hosted assistants consume, and compatibility assertions are in the test suite. The hosted path itself, which needs a public URL and an OAuth authorization server, has not been exercised end to end.

Questions

Is Meetext an MCP host?
Hosting is one thing it does, and it is not the point. Meetext hosts a per-customer MCP endpoint because that is the cleanest way to enforce isolation and entitlement, but the product is the deployment lifecycle around it: authorization, security review, validation, versioning, health and operations. A host that gives you a URL has solved the smallest part of the problem.
Which protocol versions do you support?
Streamable HTTP, negotiated per client, currently 2025-06-18, 2025-03-26, 2024-11-05. A client asking for a version Meetext does not know is answered with a version it does, rather than being refused.
I already run an MCP server. What does Meetext add?
Your server is one endpoint with your credentials. Meetext turns it into one endpoint per customer, each with that customer's own grant, their entitled subset of your capabilities, a frozen version, a validation record and an operational history. Your server stays exactly as it is; Meetext points at it.
Do my customers need to know what MCP is?
No. They install an application into their workspace the way they install any other. MCP is how your capabilities travel; it is not something the customer's administrator should have to learn to approve.
Your next customer is waiting.

You build the product.
We take it from here.

Connect a source, approve what ships and send your customer an install link. 2 customer environments free. No card required.