omnidesk-mcp
An MCP server that lets Claude, Cursor and other agents convert files through OmniDesk — 325 formats, routed through intermediate formats when no direct converter exists.
Setup
You need an OmniDesk API key (Team plan). Create one at app.omnidesk.win → Control panel → API keys.
Add to your MCP client config (Claude Desktop: claude_desktop_config.json):
{
"mcpServers": {
"omnidesk": {
"command": "uvx",
"args": ["omnidesk-mcp"],
"env": { "OMNIDESK_API_KEY": "od_..." }
}
}
}
Tools
| tool | what it does |
|---|---|
convert_file |
convert a local file to another format; returns the result path |
list_formats |
the 325 supported formats by category |
find_route |
how a conversion would be routed, and alternatives |
file_action |
one of 33 file actions: extract tables, redact, OCR, trim, … |
list_actions |
the actions and their options |
Files are uploaded to your personal drive (not the shared company drive), converted there, and the result is downloaded back to a path you choose. Nothing is kept on the client beyond that.
Safety
Tool arguments are chosen by the agent, and an agent can be steered by text it reads (a web page, an email, a document). The server therefore:
- only uploads regular files (not directories, devices or pipes);
- never replaces an existing output file unless the tool call passes
overwrite: true; - uploads to your personal drive, so a stray upload is not visible to teammates.
To confine the server to specific folders, set OMNIDESK_MCP_ROOTS to one or
more directories, separated by : on macOS/Linux or ; on Windows
(os.pathsep). Input and output paths are resolved (symlinks included) and
must lie inside one of them; anything else is refused. Unset means no folder
restriction.
"env": {
"OMNIDESK_API_KEY": "od_...",
"OMNIDESK_MCP_ROOTS": "/Users/me/Documents/convert:/Users/me/Downloads"
}
Metadata
Release files for omnidesk-mcp 0.1.2
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 |
|---|---|---|---|---|
| omnidesk_mcp-0.1.2.tar.gz | 7.3 kB | With provenance | Details for omnidesk_mcp-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| omnidesk_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for omnidesk_mcp-0.1.2-py3-none-any.whl |
Total release size: 15.6 kB
Release files / omnidesk_mcp-0.1.2.tar.gz
| Download URL | omnidesk_mcp-0.1.2.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e6535d7f180d975b85e0b4d6aae64d0de855ba315a7d6ad5e4d88233feea95c
|
|
BLAKE2b-256 checksum How to use checksums |
69c38a3d7561b2abc19201ad2316db3553383b7a88f429dafa1ab5d9c69c00bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Oct 8, 2026.
Transparency logRelease files / omnidesk_mcp-0.1.2-py3-none-any.whl
| Download URL | omnidesk_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1aff7029225d66c2fa46ffd5a47ad4c7f8ae82fd863a17d0dcc0cdc0672ce933
|
|
BLAKE2b-256 checksum How to use checksums |
f9fd22829f302927aef35d16298d61884c2aa15e32625aa1629e78d0f93d6704
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Oct 8, 2026.
Transparency logSecurity for omnidesk-mcp 0.1.2
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for omnidesk_mcp-0.1.2.tar.gz
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 Oct 8, 2026.
Transparency logA 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.