# Elicit MCP MCP Server > **Elicit MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Elicit MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/elicit-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About Elicit accelerates evidence-based research by searching millions of academic papers, extracting key findings, comparing study methods and results, and synthesizing evidence across research questions. Build literature reviews, generate structured evidence tables, and identify patterns across scientific studies. --- ## Details - Server ID: `elicit-mcp` - Version: 1.0.0 - Tools: 32 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Elicit MCP has to be in the toolset first. In order: 1. Add Elicit MCP to your toolset at https://mewcp.com/mcp/elicit-mcp 2. Connect your Elicit MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (32) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `search_papers` _(read)_ — Search Elicit's academic paper corpus. Pass `corpus` (`elicit` — default, full paper index — or `pubmed` for PubMed-only), `searchMode: "keyword"` to interpret… - `search_trials` _(read)_ — Search for clinical trials. Trial records come from ClinicalTrials.gov. Pass `trialFilters` to narrow by phase, recruitment status, or whether the trial has… - `create_report` _(destructive)_ — Create an Elicit report for a research question. - `get_report` _(read)_ — Fetch a report by its `sessionId`. The response includes title, summary, status, and available PDF/DOCX and txt/bib/ris reference-list download URLs. For… - `create_systematic_review` _(destructive)_ — Create a systematic literature review with configurable search, screening, extraction, and report stages. Two options are the person's to choose, not yours:… - `get_systematic_review` _(read)_ — Fetch a systematic review by its `sessionId`. The response includes status, available search/screen/fulltext/extract exports as CSV + XLSX under `data`, and… - `list_sessions` _(read)_ — List accessible research sessions — reports, systematic reviews, and Research Agent sessions — newest first. Use `type: agent` to find agent sessions,… - `resume_session` _(destructive)_ — Resume an owned report, systematic review, or Research Agent session with status `pausedForInsufficientQuota`. Pass the `sessionId` from the create tools or… - `get_usage` _(read)_ — Get the current account's usage status for this billing period: whether usage remains (`hasUsageRemaining`), the percentage of plan usage consumed… - `search_library` _(read)_ — Returns your own sources, newest first. To list a shared collection's papers, pass its id in the `collectionId` query parameter; those papers are not included… - `get_library_source` _(read)_ — Retrieves a source by id. `fullTextStatus` values: `pending`, Elicit has not finished looking for a PDF; `available`, full text is ready; `unavailable`, no PDF… - `get_library_source_full_text` _(read)_ — Returns the parsed full text of the source's PDF as markdown: title, abstract, and body. A `404` has one of three codes. `full_text_pending`: the PDF search or… - `save_library_sources` _(write)_ — Saves 1–100 papers. Each item is one of: an `elicitId`; a `pdfUrls` entry, metadata optional; or a `title` with at least one of `doi`, `authors`, `year`,… - `list_library_collections` _(read)_ — Returns the collections you own and the collections shared with you, sorted by name with id as a tie-breaker. `role` is your access level. `sharedVia` is set… - `get_library_collection` _(read)_ — Retrieves a collection by id. `role` is your access level. - `create_library_collection` _(write)_ — Creates an empty collection. Names are not unique. Store the returned id. - `add_to_library_collection` _(write)_ — Adds up to 500 of your sources to a collection you own or can edit. `addedCount` is the number added. A source is skipped if it is already in the collection,… - `stage_library_upload` _(write)_ — Stages a local PDF for `import_library_files`. Send the filename, `content_type: application/pdf`, and the exact `size_bytes`. Then PUT the file bytes to the… - `import_library_files` _(write)_ — Imports PDFs staged with `stage_library_upload` into the user's library. Elicit parses each file, extracts its metadata, attaches the full text, and checks for… - `get_library_import` _(read)_ — Retrieves an import. `status` is `processing` or `completed`. `completed` does not mean that every file succeeded. File `status` values: `pending`; `created`,… - `create_agent_session` _(destructive)_ — Start asynchronous Research Agent work from a query and optional attachments: [{file_id}] from stage_file_upload, after the bytes have been uploaded.… - `get_agent_session` _(read)_ — Inspect an owned or explicitly shared Research Agent session. Status is processing (working), completed (idle and ready for input, not permanently closed),… - `get_agent_session_events` _(read)_ — Read conversation, research progress, answers with citations, and Methods from an owned or explicitly shared session. Omit cursor once for full history, then… - `send_agent_session_message` _(destructive)_ — Send a follow-up to an owned Research Agent session, preferably when completed (idle) or stopped. Optionally attach uploaded files with attachments:… - `stop_agent_session` _(destructive)_ — Safely stop an owned Research Agent session, even when quota is exhausted. Repeated stop requests are safe. stopping means the stop was queued, not yet… - `stage_file_upload` _(write)_ — Prepare an upload (maximum 30 MiB) for Research Agent. Supply filename, content_type, and exact size_bytes. This does not transfer the bytes: PUT the file to… - `get_agent_session_artifacts` _(read)_ — Discover the latest file-backed artifacts and delivered outputs in an owned or explicitly shared Research Agent session. Use the opaque artifactId unchanged:… - `get_agent_session_artifact_content` _(read)_ — Read a delivered output from an owned or explicitly shared session as structured JSON, including resolved citations. Use a deliveredOutputs artifactId from… - `download_agent_session_artifact` _(read)_ — Get a short-lived download URL for an owned or explicitly shared session artifact. Use format original (default) for file-backed artifacts; for… - `create_session_share` _(destructive)_ — Share an owned Research Agent session, report, or systematic review read-only with the requested email. May send an invitation email and exposes session… - `list_session_shares` _(read)_ — List read-only recipients and pending read-only invitations on an owned Research Agent session, report, or systematic review. Owner only; recipients cannot… - `delete_session_share` _(destructive)_ — Revoke an email's direct share or pending invitation on an owned Research Agent session, report, or systematic review. Owner only and safe to repeat.… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file, then quit Claude Desktop completely and reopen it 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)