MCP compatibility guide
Cursor, with evidence.
Read evidence through the local, workspace-scoped MCP server.
Protocol tested · client acceptance pending
Prepare and verify
- Install the local MCP package and create a separate read-only key.
- Configure the client’s stdio server with a private environment.
- Compare a synthetic record with the app, then test key revocation.
Know the boundary.
No writes or automatic repairs. Vendor client configuration must be verified in your installation.
Start with synthetic data. Ropely staging remains restricted; a cloud-hosted recipe needs an accessible, authorized deployment. Account-level acceptance is separate from local SDK tests.