DocumentationConnect Claude Code to Rivul Atlas
Public guide
Connect Claude Code to Rivul Atlas
Connect Claude Code to Rivul Atlas MCP for verified AI research-paper search, citation metadata, usage checks, and revocable access.
On this page
Verification status
Status: Verified for browser OAuth. Claude Code 2.1.273 discovered search_papers and usage_status, returned a bounded three-result search for Attention Is All You Need, read the approved workspace's usage, then lost access after the grant was revoked.
Status: Verified for a dedicated MCP key. A separate temporary key discovered and called both tools, returned the same bounded search with the correct first result, and read 992 remaining MCP credits. After revocation, Atlas showed 0 of 5 active keys and the retained call failed with HTTP 401 Invalid Rivul Atlas key.
The test key, temporary Claude configuration, shell state, and clipboard value were removed after verification. No credential, token, callback code, or account detail is retained in this guide.
Add Atlas and sign in
Use a verified Pro or Ultimate Rivul AI account and open the Atlas workspace you intend to approve.
Add the production remote HTTP server at user scope. Omit an Authorization header to use browser OAuth.
Start login. Claude Code opens Rivul, where you choose one workspace and approve the two read-only scopes.
claude mcp add --scope user --transport http rivul-atlas https://rivul.ai/mcp
claude mcp login rivul-atlas
claude mcp listConnect with a dedicated key
Create a new MCP key in Rivul Atlas for this Claude Code connection only. Copy it once into a private environment variable; do not reuse a production automation key.
Add a separate Claude server entry whose Authorization header references the environment variable. Keep the complete key out of commands, project files, logs, screenshots, and shell history.
Confirm the server discovers search_papers and usage_status, then run the same bounded three-result search and one usage read.
claude mcp add --scope user --transport http rivul-atlas-key https://rivul.ai/mcp --header 'Authorization: Bearer ${RIVUL_ATLAS_MCP_KEY}'
claude mcp get rivul-atlas-key
claude mcp listRevoke and verify the key
In Atlas Access keys, revoke the temporary key immediately after the two tool calls pass.
Repeat usage_status through the retained Claude entry. The verified run returned HTTP 401 Invalid Rivul Atlas key after revocation.
Confirm Atlas shows 0 of 5 active MCP keys, remove the Claude entry, unset the environment variable, and clear any temporary clipboard value.
claude mcp remove rivul-atlas-key
unset RIVUL_ATLAS_MCP_KEYDisconnect browser access
In Rivul Atlas, open Authorized applications and disconnect the Claude grant.
Ask Claude Code to call usage_status again. The verified cleanup returned authorization required after revocation.
Remove the local server entry when you no longer want Claude Code to offer Atlas tools.
claude mcp remove rivul-atlasTroubleshooting and official references
If the browser completes consent but the CLI does not reconnect, remove the incomplete grant in Atlas and rerun login. Claude uses a temporary localhost callback port; current Rivul OAuth accepts that standards-defined loopback behavior without relaxing non-loopback redirects.
If the wrong workspace was approved, disconnect the grant and sign in again. Never paste a Rivul password into Claude Code or store a complete token in a tracked project file.
Something here wrong or missing? Email support@rivul.ai.