Vaswani et al. · 2017
Connect AI agents to scholarly search with the Atlas API and MCP server.
Search scholarly works and return normalized titles, authors, years, DOI links, and source URLs through one workspace-scoped service.
Included for verified Pro and Ultimate accounts during the controlled beta.
Metadata availability varies by record. Atlas links to source locations; it does not host paper full text.
Connect where you work
One Atlas endpoint. Familiar client workflows.
Open an official guide for the client's current MCP behavior. Rivul's in-product guide provides the Atlas-specific steps.
These links document each client's MCP support. They do not imply a partnership, endorsement, or certification of every client-specific flow.
Two interfaces, one capability layer
Choose the interface that fits the work.
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
Atlas REST API
Add scholarly discovery to a backend service without operating 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 Atlas API key
For compatible AI clients
Atlas MCP server
Give an AI client a small, discoverable set of read-only Atlas tools instead of pasting search results into each conversation.
search_papersSearch scholarly works and return structured metadata.usage_statusRead the current MCP-credit balance and plan period.Browser sign-in or a dedicated MCP key
Metadata, not hosted full text. Atlas returns scholarly metadata and source locations. The original publication remains the authority for the paper and its findings.
Access and control
Connect securely in the way your client supports.
Personal clients can use browser authorization. Scripts and managed environments can use a dedicated, revocable service key.
Browser sign-in
Add the Atlas MCP URL. The client opens Rivul so you can sign in, choose a workspace, review access, and approve the connection.
- No key to paste into the client
- Workspace-scoped access
- Visible and revocable in Atlas
API and MCP keys
Create a named key for an application, script, or managed environment. API and MCP keys are separate and cannot be used interchangeably.
- Complete key shown once
- Separate usage boundaries
- Immediate revocation
- 01Open Atlas
Use a verified Pro or Ultimate account.
- 02Choose REST or MCP
Create the matching key, or use browser sign-in for MCP.
- 03Test a search
Inspect the structured result and usage in the Atlas console.
Product direction
Start narrow. Expand from trusted primitives.
Atlas begins with read-only scholarly search. New capabilities join the API and MCP only after the shared implementation is stable and measurable.
- Paper search with bounded filters and sorting
- Titles, authors, year, DOI, venue, and source links
- Separate API-call and MCP-credit usage
- Workspace-scoped keys, activity, and revocation
- Deterministic lookup by DOI or OpenAlex ID
- Open-access resolution with provenance
- Related-paper discovery and journal-scope matching
- Reproducible landscape reports through Rivul Intelligence
Rivul Atlas · Beta
Bring scholarly search into the tools you already use.
Available to verified Pro and Ultimate accounts.