DocumentationConnect Cursor to Rivul Atlas
Public guide
Connect Cursor to Rivul Atlas
Cursor authorized and discovered Atlas, but the retained run is blocked because its agent runtime did not load the Rivul tool namespace.
On this page
Current status
Status: Blocked. Cursor completed browser OAuth and discovered search_papers and usage_status against the production Atlas endpoint, but its agent runtime did not expose the discovered Rivul tool namespace for calls.
This page documents the supported setup and retained failure boundary. It does not claim verified Cursor interoperability. Retest when Cursor loads the discovered namespace into its runtime; publish a verified claim only after bounded search, usage read, revocation, and denied-after-revocation checks pass.
Add the remote server
Add this URL-only entry to your personal ~/.cursor/mcp.json or the project's .cursor/mcp.json.
Open Cursor Settings, then Tools & MCP, and confirm Rivul Atlas appears.
Choose Authenticate, or start the browser flow from Cursor's agent CLI.
{
"mcpServers": {
"rivul-atlas": {
"url": "https://rivul.ai/mcp"
}
}
}
agent mcp login rivul-atlasInspect before relying on it
List the server's tools and confirm search_papers and usage_status are discovered.
Ask Cursor Agent to call search_papers with a limit of 3. A prose answer without a tool invocation is not a passing Atlas test.
Ask it to call usage_status and confirm the selected workspace. In the retained run, the runtime stopped before steps 2 and 3 even though discovery passed.
agent mcp list-tools rivul-atlasClean up a blocked attempt
Open Rivul Atlas and disconnect every temporary Cursor grant created during the attempt.
Remove the Rivul Atlas entry from the personal or project mcp.json file if you do not want Cursor to retry it.
Restart Cursor so cached tool state cannot be mistaken for a current connection.
Retest condition and official references
Retry after a Cursor release or runtime refresh that exposes the already-discovered Rivul namespace to the agent. A passing retest must show actual Atlas tool calls, not only an authenticated server and tool list.
Keep project files free of literal credentials. If you deliberately choose key mode, use Cursor's documented environment expansion in a private configuration and revoke the dedicated Atlas key after the test.
Something here wrong or missing? Email support@rivul.ai.