docira-mcp
MCP server for Docira — multi-model OCR / document-to-Markdown/JSON.
A thin client over the hosted Docira API: it needs only your API key, no local model stack. Works with any MCP client (Claude Desktop, agents).
Tools
| Tool | What it does |
|---|---|
parse_document(file_url, operation_mode, max_pages) |
Parse a doc at a URL → Markdown |
extract_structured(file_url, json_schema, max_pages) |
Schema-driven structured JSON (invoices, receipts, forms) |
parse_local_file(file_path, operation_mode) |
Parse a local file (multipart upload) → Markdown |
get_result(result_id) |
Retrieve an async/batch result by id |
health() |
API + provider status |
Claude Desktop
Add to claude_desktop_config.json (create a key in the Docira dashboard → Keys):
{
"mcpServers": {
"docira": {
"command": "uvx",
"args": ["docira-mcp"],
"env": { "DOCIRA_API_KEY": "pw_live_…" }
}
}
}
Before publishing to PyPI, run it straight from the repo:
{
"mcpServers": {
"docira": {
"command": "uvx",
"args": ["--from", "/abs/path/to/ParseWave/clients/docira-mcp", "docira-mcp"],
"env": { "DOCIRA_API_KEY": "pw_live_…" }
}
}
}
Config (env)
| Var | Default | Notes |
|---|---|---|
DOCIRA_API_KEY |
— (required) | Your pw_live_… / pw_test_… key |
DOCIRA_API_URL |
https://parsewave-api.fly.dev |
API base |
DOCIRA_TIMEOUT |
300 |
Per-request seconds |
Notes
extract_structuredis the schema-driven path (returnscontent_json); it routes server-side to a structured-extraction-capable model.- Responses are model-agnostic —
provideris reported as"docira".
Metadata
Release files for docira-mcp 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 |
|---|---|---|---|---|
| docira_mcp-0.1.0.tar.gz | 4.3 kB | Without provenance | Details for docira_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| docira_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for docira_mcp-0.1.0-py3-none-any.whl |
Total release size: 9.1 kB
Release files / docira_mcp-0.1.0.tar.gz
| Download URL | docira_mcp-0.1.0.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8659ba4661fbeaeaf8be2d46304a24a973ab2660033be8d25c1c64c3c03c4fae
|
|
BLAKE2b-256 checksum How to use checksums |
4f4ba34b377f1bcec78cb8387b5995b0f3ec11d6f2f37ad0f09adf0f1ca163f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / docira_mcp-0.1.0-py3-none-any.whl
| Download URL | docira_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56824e4a4eff7eb306c11f79f5c8d15f9f6133936a95a43a9ca4579c99f77b70
|
|
BLAKE2b-256 checksum How to use checksums |
ea81e2cdf73608b13056572eb6ae53206bbad6b557474d325bf7190ab8288830
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for docira-mcp 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.