Dock vs TexMCP
A side-by-side look at the Dock and TexMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dock for workplace & productivity work as a local process; choose TexMCP for workplace & productivity over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dock when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DOCK_API_KEY, DOCK_MCP_URL.
Choose TexMCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 35/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | DOCK_API_KEYDOCK_MCP_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 11 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Dock | View TexMCP |
Tools & capabilities
Dock tools
No tool names declared yet. Check the project README from the listing page.
TexMCP 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.
Dock
{
"mcpServers": {
"dock-2": {
"command": "npx",
"args": [
"-y",
"@trydock/mcp"
],
"env": {
"DOCK_API_KEY": "YOUR_DOCK_API_KEY_HERE",
"DOCK_MCP_URL": "YOUR_DOCK_MCP_URL_HERE"
}
}
}
}
TexMCP
{
"mcpServers": {
"devroopsaha744-texmcp": {
"url": "http://localhost:8000/mcp"
}
}
}
Frequently asked questions
Dock is categorized under Workplace & Productivity and uses a local stdio subprocess. TexMCP belongs to Workplace & Productivity and uses a remote HTTP/SSE transport. Pick Dock for workplace & productivity work and TexMCP for workplace & productivity.
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.
Dock has no declared pricing — check the project's own site. TexMCP 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 dock-2 and devroopsaha744-texmcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dock has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. TexMCP has 48/100 (Fair) with 3 views, 0 installs and 11 GitHub stars.