Rivul MCP is the Rivul AI MCP server and REST API for read-only agentic AI research. Search metadata for 300M+ scholarly works, built using the open OpenAlex dataset (CC0), and return normalized titles, authors, years, citation counts, DOI links, and source URLs through one workspace-scoped service. Setup guides cover Claude Code, OpenAI Codex, Cursor, Google Antigravity, Muse Code, and any client that supports remote MCP servers.
Available to every Rivul AI account, within fair-use limits. Paper metadata from the open OpenAlex dataset (CC0).
Each card opens the client's official MCP documentation. The setup guide under MCP setup in Rivul MCP gives the matching steps.
Google AntigravityGoogleMuse CodeMetaThese links document each client's MCP support. They do not imply a partnership, endorsement, or certification of every client-specific flow.
REST is for software. MCP is for AI clients. Both use the same validated search capability and return the same normalized scholarly metadata.
For applications and automations
Add research-paper search and paper metadata to a backend service without running a search index or translating provider records yourself.
POST /api/atlas/v1/searchSearch scholarly metadataGET /api/atlas/v1/usageRead API usageGET /api/atlas/openapi.jsonOpenAPI 3.1 contractDedicated Rivul MCP API key
For compatible AI clients
Give an AI agent a small, discoverable set of read-only research tools instead of pasting paper results into each conversation.
search_papersSearch scholarly works and return structured metadata.get_paper_detailsReturn the full record for one work by its OpenAlex ID.usage_statusRead today's usage against fair-use daily limits.Browser sign-in or a dedicated MCP key
Metadata, not hosted full text. Rivul MCP returns scholarly metadata and source locations. The original publication remains the authority for the paper and its findings.
Personal clients can use browser authorization. Scripts and managed environments can use a dedicated, revocable service key.
Add the Rivul MCP URL. The client opens Rivul so you can sign in, choose a workspace, review access, and approve the connection.
Create a named key for an application, script, or managed environment. API and MCP keys are separate and cannot be used interchangeably.
Use a confirmed Rivul AI account.
Create the matching key, or use browser sign-in for MCP.
Inspect the structured result and usage in the Rivul MCP console.
Rivul MCP begins with read-only scholarly search. New capabilities join the API and MCP only after the shared implementation is stable and measurable.