mcp-papra
An MCP server that lets Claude search, read and tag the documents in your Papra instance — read-only by default.
Install
pip install mcp-papra # or run it without installing: uvx mcp-papra
Create an API key in Papra (read permissions are enough), then set:
| Variable | Meaning |
|---|---|
PAPRA_API_KEY |
API key (required unless demo mode) |
PAPRA_URL |
Papra API URL (default https://api.papra.app; use your own for self-hosted) |
PAPRA_ORGANIZATION_ID |
Organization id (optional if the key only sees one) |
PAPRA_ALLOW_WRITE=1 |
Also expose upload_document and tag_document |
PAPRA_DEMO=1 |
Fictional documents, no key and no network |
Use with Claude Code
claude mcp add papra --env PAPRA_API_KEY=your_key -- uvx mcp-papra
# try it without any account:
claude mcp add papra-demo --env PAPRA_DEMO=1 -- uvx mcp-papra
Use with Claude Desktop
In claude_desktop_config.json:
{
"mcpServers": {
"papra": {
"command": "uvx",
"args": ["mcp-papra"],
"env": { "PAPRA_API_KEY": "your_key" }
}
}
}
Tools
| Tool | Mode | What it does |
|---|---|---|
search_documents(query, limit) |
read | Search with Papra's advanced syntax (tag:contract AND created:>2024, -has:tags, …); returns metadata, not text |
get_document(document_id, max_chars) |
read | Metadata and extracted text, truncated to max_chars |
summarize_by_tag(tag, limit) |
read | Name and excerpt of each document with a tag (Papra has tags, not folders); Claude writes the summary |
upload_document(path, ocr_languages) |
write | Upload a local file |
tag_document(document_id, tag_name) |
write | Attach a tag, creating it if needed |
Write tools exist only when PAPRA_ALLOW_WRITE=1. This is an unofficial project, not affiliated with Papra.
Development
pip install -e ".[test]" && pytest # no network needed
MIT licensed.
Metadata
Release files for mcp-papra 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_papra-0.1.0.tar.gz | 10.4 kB | Without provenance | Details for mcp_papra-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_papra-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for mcp_papra-0.1.0-py3-none-any.whl |
Total release size: 19.7 kB
Release files / mcp_papra-0.1.0.tar.gz
| Download URL | mcp_papra-0.1.0.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc8c80941d3d1caef1e06cd396fb2a9426159a08699237da2ef98741f83ec5aa
|
|
BLAKE2b-256 checksum How to use checksums |
8ba1ccc3afe8f153135e57d4325c82308f63c06cc65773221f142e192ac60d2c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Release files / mcp_papra-0.1.0-py3-none-any.whl
| Download URL | mcp_papra-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e261d7d01d4cb263084b199a9d5e58036fdd3af43748beb76ca92b8831f3f4c
|
|
BLAKE2b-256 checksum How to use checksums |
409df44636e2bff59f486b41b2bea040c16a462be02573b2b6c46344d01d435d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Security for mcp-papra 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.