Rivul MCP Keys, Authorized Apps and Activity

The Rivul MCP page

Open Rivul MCP in the sidebar, under Agents. It has five tabs: Overview (today's usage, your keys, and the search, OpenAPI and MCP endpoints), Access keys, API playground, MCP setup, and Activity.

Rivul MCP is set up per workspace. If the page asks you to create a paper first, create one, then reload the page.

Two ways to connect

Sign in with Rivul (OAuth) is the usual way for an AI client: the client opens Rivul in your browser, you choose a workspace and approve two read-only scopes, and no key is copied anywhere.

An access key suits scripts, servers and clients without browser sign-in. An API key works with the REST API; an MCP key works with the MCP server at https://rivul.ai/mcp.

Create a key

1. Step 1: Open Access keys and use New key to choose an API key or an MCP key, then click Create key.
2. Step 2: Copy the key. It is shown once, and Rivul AI cannot show the full key again; the list keeps only its prefix.
3. Step 3: Store it in an environment variable or a secret store, never in a file you commit.

Each workspace holds 1 active API key and 1 active MCP key. To replace a key, revoke it first.

Revoke a key

1. Step 1: In Access keys, click Revoke on the key, then Confirm revoke.
2. Step 2: The key stops working at once: a call with it returns HTTP 401 Invalid Rivul Atlas key.
3. Step 3: Create a new key if a tool still needs access, and update that tool.

Authorized applications

MCP setup lists the AI clients you approved with Sign in with Rivul for this workspace. Click Disconnect, then Confirm disconnect, to remove one: it loses access at once, and reconnecting needs a new approval.

Test in the playground

API playground runs a live search with your saved API key and shows the JSON your application would receive. On MCP setup, Run MCP test calls search_papers with your saved MCP key. Both need a key first, and both count toward that channel's usage.

Activity

Activity shows today's usage and, under Recent requests, the status, channel, key and latency of each API and MCP request; filter by All, API or MCP. Query text and results are never stored there. Key changes lists when keys were created or revoked, never their secret values.

• Usage and fair-use limits