Elicit opened research workflows through its API and MCP server
Elicit made search, screening, extraction, and reporting workflows available through an API and MCP server.
- What changed
- Elicit made search, screening, extraction, and reporting workflows available through an API and MCP server.
- Who is affected
- Developers and research-operations teams considering Elicit as a component inside an agent or internal workflow.
- What to do now
- Confirm the current implementation contract before building: access, limits, data handling, output traceability, and failure behavior.
The material change
Elicit documents API and MCP access for research search, screening, extraction, and reporting workflows.
Current authentication, plan access, limits, pricing, data handling, and failure behavior require verification in current official documentation.
What users should reconsider
Developers can evaluate Elicit as an evidence component inside another agent instead of using it only as a destination product.
Buyers should compare integration scope, evidence traceability, usage limits, and data handling before adopting it for automated research.
Check these before connecting the API or MCP server
- Authentication and access: confirm the current credential flow and which API or MCP features your plan includes.
- Limits and cost: verify current rate limits, usage limits, pricing, and expected completion time in official documentation.
- Data handling: confirm how uploaded or internal material is retained, processed, and separated for your use case.
- Failure boundary: decide how the host workflow handles partial search, screening, extraction, or report failures without presenting an incomplete result as final.
These implementation details are not established by the launch announcement; verify them in current official documentation.
What was recorded before
See the accepted Change record for the preserved previous state.
What is known now
Elicit documents API and MCP access for research search, screening, extraction, and reporting workflows. Current authentication, plan access, limits, pricing, data handling, and failure behavior require verification in current official documentation.
Accepted Change chg_loop_elicit_api_mcp → Agent Fact fact_loop_elicit_api_mcp · Last verified 2026-07-15The Elicit API and MCP: Powering autonomous research engines
Published by Elicit. Evidence state remains Source-Backed; this is not execution verification.
Open official source →