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