Every operation becomes a capability
An operation without an operationId is named from its method and path rather than skipped.
OpenAPI to MCP
Meetext discovers every operation, classifies its risk and freezes the approved subset into a customer deployment.
Connect a source. Choose what ships.
OpenAPI → customer-scoped tools
get_accountsReadApprovedupdate_accountWriteReviewdelete_accountDestructiveBlockedA source change never silently widens access.
An operation without an operationId is named from its method and path rather than skipped.
Path parameters, query parameters and the request body are normalised into a single JSON Schema, so the caller sees arguments.
GET is read. POST, PUT and PATCH are write. DELETE is destructive and cannot be published until somebody approves it explicitly.
If the document changes and an approved capability's schema changes with it, the approval is revoked rather than carried forward.
curl -X POST https://api.meetext.xyz/v1/products/{id}/sources \
-H "authorization: Bearer $MEETEXT_API_KEY" \
-d '{"type": "openapi",
"config": {"url": "https://api.acme.com/openapi.json"}}'
# Operations are imported and classified.
# Enable the ones customers should get, approve the
# destructive ones explicitly, then publish.A tool list is not a deployment. It has to run in each customer's workspace, under their grant, and keep working as you ship.
Watch that happen on one deployment · What enterprise MCP actually requires
Connect a source, approve what ships and send your customer an install link. 2 customer environments free. No card required.