Melaya vs MetaDock
A side-by-side look at the Melaya and MetaDock 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 Melaya for os automation work as a local process; choose MetaDock for os automation over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Melaya when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
MChoose MetaDock when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M MetaDock | |
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 45/100 · Fair | 38/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Melaya | View MetaDock |
Tools & capabilities
Melaya tools
No tool names declared yet. Check the project README from the listing page.
MetaDock 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.
Melaya
{
"mcpServers": {
"melaya": {
"command": "npx",
"args": [
"-y",
"@melaya/runner@1.1.60"
]
}
}
}
MetaDock
{
"mcpServers": {
"metadock": {
"url": "https://metadock.app/mcp"
}
}
}
Frequently asked questions
Melaya is categorized under OS Automation and uses a local stdio subprocess. MetaDock belongs to OS Automation and uses a remote HTTP/SSE transport. Pick Melaya for os automation work and MetaDock for os automation.
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.
Melaya has no declared pricing — check the project's own site. MetaDock has no declared pricing — check the project's own site. 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 melaya and metadock as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Melaya has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. MetaDock has 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.