Connect Meta Muse Code to Rivul MCP

Overview

Meta Muse Code connects to Rivul MCP as a remote MCP server, through browser sign-in with dynamic client registration and PKCE, or through a dedicated MCP key in your private settings file. Muse can then call search_papers, get_paper_details, and usage_status, all read-only.

Before you start

1. Step 1: Use a Rivul AI account with Rivul MCP provisioned for the workspace you intend to approve.
2. Step 2: Note that settings.json is a personal file. Nothing you put in it should be a credential you would not retype.
3. Step 3: Confirm your installed Muse Code version. Client behavior changes between releases, so a setting below can differ in your build.

Configure browser sign-in

1. Step 1: Open ~/.config/muse/settings.json and retain schema_version 1.
2. Step 2: Add the URL-only Rivul MCP entry under the camel-case mcpServers key. Optional mode lets Muse continue with a warning if Rivul MCP is unavailable.
3. Step 3: Start Muse's MCP login command, choose one Rivul MCP 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"
    }
  }
}

Verify before relying on it

1. Step 1: Start login and complete consent in the browser.
2. Step 2: Confirm Muse discovers search_papers, get_paper_details, and usage_status.
3. Step 3: Run a bounded three-result search and one usage read.

muse mcp login rivul-atlas

Use a dedicated key carefully

Muse's published settings shape accepts a static Authorization header. Create a dedicated MCP key in Rivul MCP, 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 a message, or reuse it for another client.

"headers": {
  "Authorization": "Bearer YOUR_RIVUL_ATLAS_MCP_KEY"
}

Troubleshooting

Consent succeeds but Rivul MCP tools don't appear in Muse. Restart Muse and run muse mcp login again. Disconnect any incomplete Muse grant in Rivul MCP rather than leaving it active, or use a dedicated key as described above.

A dedicated key is no longer needed. Revoke it in Rivul MCP and remove it from settings.json. Confirm Rivul MCP shows no active MCP keys you did not intend to keep.

You need to know whether access still works. Read usage_status, which never counts toward usage, and verify that every tool is denied after revocation.

• Meta Muse Code MCP documentation
• Model Context Protocol authorization specification
• Rivul MCP tool reference
• Open Rivul MCP