OpenPaper MCP Server
OpenPaper is an autonomous research engine for Claude Desktop and any MCP client. Auto research from a prompt to a fully-cited academic paper, exported as PDF, DOCX, or ZIP.
OpenPaper uses 18 specialized AI agents to search 500M+ academic sources (OpenAlex, Crossref, Semantic Scholar) and write thesis-level papers with every citation linked to a real publication.
Setup
1. Get your API token
- Go to openpaper.dev and sign in
- Open DevTools → Network tab
- Click any request → find the
Authorizationheader - Copy the value after
Bearer— that's your token
2. Configure Claude Desktop
Add to your claude_desktop_config.json (no manual install needed — uvx fetches the published package on first run):
{
"mcpServers": {
"openpaper": {
"command": "uvx",
"args": ["openpaper-mcp"],
"env": {
"OPENPAPER_API_TOKEN": "your-token-here"
}
}
}
}
Run from source instead
pip install mcp httpx
{
"mcpServers": {
"openpaper": {
"command": "python",
"args": ["/path/to/openpaper-mcp/server.py"],
"env": {
"OPENPAPER_API_TOKEN": "your-token-here"
}
}
}
}
Tools
start_paper_generation
Start generating a paper. Returns a generation_id immediately.
Generate a graduate-level paper on "The neurobiological basis of PTSD"
using APA 7th citation style, 20-30 pages
check_paper_status
Poll for progress and get download links when done.
Check the status of generation abc123
list_my_papers
See all your previous papers with download links.
List my last 5 papers
Example workflow
User: Write a paper on the impact of social media on adolescent mental health
Claude: [calls start_paper_generation("impact of social media on adolescent mental health")]
→ Generation started (ID: abc123). Checking back in a few minutes...
[later]
Claude: [calls check_paper_status("abc123")]
→ Status: processing, phase: writing, 65% complete
[later]
Claude: [calls check_paper_status("abc123")]
→ Status: completed! PDF: https://... DOCX: https://...
Credits
Papers cost 1-3 credits depending on length:
- 5-30 pages: 1 credit
- 30-50 pages: 2 credits
- 50-60 pages: 3 credits
New accounts get free credits. Buy more at openpaper.dev.
Metadata
Release files for openpaper-mcp 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| openpaper_mcp-0.1.3.tar.gz | 29.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openpaper_mcp-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 65.1 kB
Release files / openpaper_mcp-0.1.3.tar.gz
| Download URL | openpaper_mcp-0.1.3.tar.gz |
|---|---|
| Size | 29.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b57522c465175de96def2d00c141a95f5495f7719586dbfa5d11c6dc039bd074
|
|
BLAKE2b-256 checksum How to use checksums |
4af60ab8212cbfa6b2dd6b2d6eb41256f5e98da5d9f5fab3b6d11bb80a993da2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 29, 2026.
Transparency logRelease files / openpaper_mcp-0.1.3-py3-none-any.whl
| Download URL | openpaper_mcp-0.1.3-py3-none-any.whl |
|---|---|
| Size | 35.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ea1d8e94e409b1b14a07e0d3a4fcc6b7f36f16085580f737d68eaf3a2d2fd629
|
|
BLAKE2b-256 checksum How to use checksums |
885c405c14d88eeaf98b6ffe8a6797a7dc0b476f9ecb59b5d94b60cd9b68cb00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 29, 2026.
Transparency log