Skip to main content
Cursor supports MCP via its own JSON config.

​
Global config

Add the server to ~/.cursor/mcp.json to make it available in every project:
Or open the command palette and choose Cursor Settings > MCP > Add new global MCP server.

​
Project config

For a per-project setup, create .cursor/mcp.json at the project root with the same content. Project config takes precedence over global config.

​
Remote (hosted HTTP)

Prefer not to run anything locally? Point Cursor at Versuno’s hosted server, sending your key as a bearer token:
The hosted server provides the read/query tools only — pull_asset and push_asset need local disk access, so use the npx config above for those.

​
Enabling the server

Cursor picks up config changes without a restart, but you may need to toggle the server off and on again from Cursor Settings > MCP. A green dot next to “versuno” means it’s connected.

​
Using it

Open the chat panel and mention Versuno in your prompt. Cursor will invoke the MCP tools as needed:
“Search my Versuno assets for anything related to customer support and load the top match into context.”
Cursor asks you to approve each tool call the first time. Keep this enabled. See Security for why.

​
Troubleshooting

If the server shows red in Settings > MCP, click it to see the stderr output. The most common issues are a missing or invalid API key. See the generic Troubleshooting guide.