DocumentationConnect Meta Muse Code to Rivul Atlas
Public guide
Connect Meta Muse Code to Rivul Atlas
A Muse Code setup and troubleshooting guide that records the successful registration and consent steps without overstating the blocked native callback.
On this page
Current status
Status: Blocked. Muse Code completed dynamic client registration, Rivul consent, and grant creation, but the browser callback never reached the native Muse client, so tool discovery and calls did not complete.
Dedicated-key mode remains a documented private fallback, not a retained verified run. Retest browser OAuth when Muse's local callback listener can complete the handoff.
Configure browser sign-in
Open ~/.config/muse/settings.json and retain schema_version 1.
Add the URL-only Rivul Atlas entry under the camel-case mcpServers key. Optional mode lets Muse continue with a warning if Atlas is unavailable.
Start Muse's MCP login command, choose one Atlas workspace in the browser, and approve read-only access.
{
"schema_version": 1,
"mcpServers": {
"rivul-atlas": {
"type": "streamable-http",
"url": "https://rivul.ai/mcp",
"mode": "optional"
}
}
}
muse mcp login rivul-atlasRecognize the callback blocker
The retained attempt reached the Rivul consent screen and created a grant. The failure occurred afterward: Muse's local callback listener did not receive the browser handoff.
Do not treat an approved Rivul grant as proof that Muse is connected. A passing run must continue through tool discovery, a bounded search_papers call, and usage_status.
Use a dedicated key carefully
Muse's published settings shape accepts a static Authorization header. Create a dedicated MCP key in Atlas, place it only in the private personal settings file, and replace the placeholder locally.
The vendor guide does not promise environment-variable expansion for remote headers. Do not commit a literal key, paste it into support messages, or reuse it for another client.
"headers": {
"Authorization": "Bearer YOUR_RIVUL_ATLAS_MCP_KEY"
}Clean up and retest
Disconnect the incomplete Muse grant in Rivul Atlas after a blocked OAuth attempt.
Revoke any temporary MCP key used for fallback testing and remove it from settings.json.
Retest OAuth only after Muse can receive its localhost callback, then verify both tools and denied access after revocation.
Something here wrong or missing? Email support@rivul.ai.