IntegrationsVS Code
Deliberately separate from Cursor rather than one 'editor' destination: a customer standardised on one is not a customer standardised on the other, and an environment is what gets sold, revoked and reported on.
Your AI, MCP server or API
Their workspace and approved access
Their entitled capabilities and version
Validation, health and the next action
Available today
Ready for customer deployments with customer-scoped authorization, validation and lifecycle management.
What a forward deployed engineer does by hand today.
No install and no redirect. The customer receives a server URL and a token, and adds an HTTP MCP server. In an organisation this normally lives in workspace settings rather than on each machine.
The person whose calendar decides your go-live date.
Whoever owns the repository or workspace settings the configuration lands in.
Whose identity the product acts as, and where that grant lives.
A token Meetext issues for this environment alone.
The repeatable half, turned into software.
The hosted MCP endpoint, the per-customer token, the frozen package behind it, and revocation.
The half that is theirs and should stay theirs.
Their workspace configuration, and which of their developers it reaches.
How capabilities map onto what the platform will let you do.
Not provider scopes. This customer's entitlement at their approved version.
What has to execute before anyone is told it works.
Proven by connecting, not by being configured.
Rotation, expiry, revocation, and who notices first.
One token per environment, rotatable, and revocable alone.
What happens to this customer when you ship version four.
Per customer, not per server. Publishing does not move an installed customer.
What actually goes wrong, named rather than generalised.
A non-public endpoint, refused at publish. Beyond that, a configuration committed to a repository where the token should not be, which is why the token is per environment and rotatable.
How you learn it broke without the customer telling you.
Token issued, endpoint publicly reachable, and whether the client has ever connected.
Ready for customer deployments with customer-scoped authorization, validation and lifecycle management.
Available for customer deployments, with customer-scoped authorization, validation and lifecycle management.
Connect a source, approve what ships and send your customer an install link. 2 customer environments free. No card required.
