How installation normally works
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 MCP server under Settings, Tools and Integrations.
IntegrationsCursor
Cursor
The same inward shape as Claude, aimed at a different room. Where a customer's engineers already work inside an editor, the vendor's product reaches them there rather than asking them to leave it.
AvailableSee the deployment model
Built once
Your AI, MCP server or API
Your product, in Cursor.
CursorAvailable
- One customer
Their workspace and approved access
- One package
Their entitled capabilities and version
- One record
Validation, health and the next action
Cursor · Available
Available today
Ready for customer deployments with customer-scoped authorization, validation and lifecycle management.
Who has to approve it
The person whose calendar decides your go-live date.
Whoever administers the team's Cursor configuration. In a company this is usually set once centrally rather than by each developer.
Identity and OAuth model
Whose identity the product acts as, and where that grant lives.
A token Meetext issues for this environment alone, separate from the same customer's other connectors.
What Meetext owns
The repeatable half, turned into software.
The hosted MCP endpoint, the per-customer token, the frozen package behind it, and revocation.
What the customer owns
The half that is theirs and should stay theirs.
Their Cursor configuration, and which of their developers it reaches.
Capability and permission model
How capabilities map onto what the platform will let you do.
Not provider scopes. The token reaches this customer's entitlement at their approved version, and nothing else the vendor has published.
Validation
What has to execute before anyone is told it works.
The connector proves itself by connecting. Nothing is marked connected until a request arrives carrying this environment's token.
Credential lifecycle
Rotation, expiry, revocation, and who notices first.
One token per environment, rotatable, independent of every other destination this customer runs.
Deployment versioning
What happens to this customer when you ship version four.
A new vendor version does not move an installed customer. Their editor keeps calling the package approved for them.
Typical failure modes
What actually goes wrong, named rather than generalised.
An endpoint that is not publicly reachable, which fails silently on the customer's side. Refused at publish rather than discovered later.
Operational monitoring
How you learn it broke without the customer telling you.
Token issued, endpoint publicly reachable, and whether the client has ever connected.
Common questions
- Does Meetext support Cursor?
- Yes. Cursor is available for customer deployments. Meetext manages customer-scoped authorization, validation, credentials and deployment lifecycle.
- Who has to approve a Cursor installation?
- Whoever administers the team's Cursor configuration. In a company this is usually set once centrally rather than by each developer.
- What goes wrong with Cursor deployments?
- An endpoint that is not publicly reachable, which fails silently on the customer's side. Refused at publish rather than discovered later.
Current support status
AvailableCursor
Ready for customer deployments with customer-scoped authorization, validation and lifecycle management.
Available for customer deployments, with customer-scoped authorization, validation and lifecycle management.
Your next customer is waiting.You build the product.
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.