Local Workspace MCP vs Markitdown
A side-by-side look at the Local Workspace MCP and Markitdown MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
MarkitdownFile Systems · Local subprocess (stdio)MCP tool access to MarkItDown -- a library that converts many file formats (local or remote) to Markdown for LLM consumption.67GreatAuth: no auth requiredVerdict: choose Local Workspace MCP for file systems work; choose Markitdown 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 Local Workspace MCP when
- You need dedicated capabilities in the File Systems domain.
- Its auth model fits you: No auth required.
Choose Markitdown 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.
- You want tools like
convert_to_markdown.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Markitdown | |
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 32/100 · Emerging | 67/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 190,462 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Local Workspace MCP | View Markitdown |
Tools & capabilities
Local Workspace MCP tools
No tool names declared yet. Check the project README from the listing page.
Markitdown tools 1
convert_to_markdownConvert a resource described by an http:, https:, file: or data: URI to markdown
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.
Local Workspace MCP
No confirmed install command for Local Workspace MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Markitdown
{
"mcpServers": {
"microsoft-markitdown": {
"command": "uvx",
"args": [
"markitdown-ocr"
]
}
}
}
Frequently asked questions
Local Workspace MCP is categorized under File Systems and uses an install path we have not confirmed yet. Markitdown belongs to File Systems and uses a local stdio subprocess. Pick Local Workspace MCP for file systems work and Markitdown 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. Local Workspace MCP has no confirmed install command yet — follow its own setup instructions.
Local Workspace MCP is listed as free. Auth: no auth required. Markitdown 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 local-workspace-mcp and microsoft-markitdown as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Local Workspace MCP has a quality signal of 32/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Markitdown has 67/100 (Great) with 5 views, 0 installs and 190,462 GitHub stars.