Document Converter vs Llm Context.py
A side-by-side look at the Document Converter and Llm Context.py MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Document Converter for file systems work; choose Llm Context.py for file systems as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Document Converter when
- You need dedicated capabilities in the File Systems domain.
- You want tools like
convert_to_markdown, preview_markdown.
Choose Llm Context.py when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 39/100 · Fair | 44/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 307 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Document Converter | View Llm Context.py |
Tools & capabilities
Document Converter tools 2
convert_to_markdownConverts a file or URL to Markdown and saves output (`.md` beside source, or `youtube-{id}.md` for YouTube URLs)preview_markdownReturns Markdown in the chat response only
Llm Context.py tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Document Converter
No confirmed install command for Document Converter yet — follow the setup steps linked from its listing page rather than a guessed package name.
Llm Context.py
{
"mcpServers": {
"cyberchitta-llm-context-py": {
"command": "uvx",
"args": [
"--from",
"llm-context",
"lc-mcp"
]
}
}
}
Frequently asked questions
Document Converter is categorized under File Systems and uses an install path we have not confirmed yet. Llm Context.py belongs to File Systems and uses a local stdio subprocess. Pick Document Converter for file systems work and Llm Context.py for file systems.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Document Converter has no confirmed install command yet — follow its own setup instructions.
Document Converter has no declared pricing — check the project's own site. Llm Context.py is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add document-converter and cyberchitta-llm-context-py as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Document Converter has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Llm Context.py has 44/100 (Fair) with 2 views, 0 installs and 307 GitHub stars.
