MetaDock vs PraisonAI
A side-by-side look at the MetaDock and PraisonAI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MetaDockOS Automation · Remote HTTP/SSEControl the MetaDock desktop workspace over MCP: browsers, layouts, bookmarks, downloads, and more.38FairAuth: not declaredVerdict: choose MetaDock for os automation work over a hosted endpoint; choose PraisonAI for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose MetaDock when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a remote HTTP/SSE transport.
Choose PraisonAI when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
OPENAI_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M MetaDock | |
|---|---|---|
| Category | OS Automation | Coding Agents |
| Quality signal | 38/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | OPENAI_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 9,284 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MetaDock | View PraisonAI |
Tools & capabilities
MetaDock tools
No tool names declared yet. Check the project README from the listing page.
PraisonAI 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.
MetaDock
{
"mcpServers": {
"metadock": {
"url": "https://metadock.app/mcp"
}
}
}
PraisonAI
{
"mcpServers": {
"praisonai": {
"command": "uvx",
"args": [
"praisonai"
],
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE"
}
}
}
}
Frequently asked questions
MetaDock is categorized under OS Automation and uses a remote HTTP/SSE transport. PraisonAI belongs to Coding Agents and uses a local stdio subprocess. Pick MetaDock for os automation work and PraisonAI for coding agents.
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.
MetaDock has no declared pricing — check the project's own site. PraisonAI has no declared pricing — check the project's own site. 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 metadock and praisonai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MetaDock has a quality signal of 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. PraisonAI has 40/100 (Fair) with 3 views, 0 installs and 9,284 GitHub stars.