Evictions API vs Texas Code
A side-by-side look at the Evictions API and Texas Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
E
Evictions APILegal · Remote HTTP/SSEUS/DC eviction cases. A licensed attorney reviews each real case before anything is served or filed.43FairAuth: api key requiredVerdict: choose Evictions API for legal work over a hosted endpoint; choose Texas Code for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
EChoose Evictions API when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
EVICTIONS_API_URL, EVICTIONS_API_KEY.
Choose Texas Code 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 | E Evictions API | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 43/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | EVICTIONS_API_URLEVICTIONS_API_KEY | None listed |
| Verified owner |
Tools & capabilities
Evictions API tools
No tool names declared yet. Check the project README from the listing page.
Texas Code 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.
Evictions API
{
"mcpServers": {
"evictions-api": {
"url": "https://evictionsapi.com/mcp"
}
}
}
Texas Code
{
"mcpServers": {
"texas-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-texas-code"
]
}
}
}
Frequently asked questions
Evictions API is categorized under Legal and uses a remote HTTP/SSE transport. Texas Code belongs to Legal and uses a local stdio subprocess. Pick Evictions API for legal work and Texas Code 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.
Evictions API has no declared pricing — check the project's own site. Auth: api key required. Texas Code 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 evictions-api and texas-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Evictions API has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Texas Code has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.