Cornell Wex vs Ttab
A side-by-side look at the Cornell Wex and Ttab MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cornell Wex for legal work as a local process; choose Ttab for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cornell Wex when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
Choose Ttab when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 41/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
Tools & capabilities
Cornell Wex tools
No tool names declared yet. Check the project README from the listing page.
Ttab 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.
Cornell Wex
{
"mcpServers": {
"cornell-wex": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-cornell-wex"
]
}
}
}
Ttab
{
"mcpServers": {
"ttab": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-ttab"
]
}
}
}
Frequently asked questions
Cornell Wex is categorized under Legal and uses a local stdio subprocess. Ttab belongs to Legal and uses a local stdio subprocess. Pick Cornell Wex for legal work and Ttab for legal.
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.
Cornell Wex has no declared pricing — check the project's own site. Ttab 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 cornell-wex and ttab as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cornell Wex has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Ttab has 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.