Contracts Wizard vs Texas Code
A side-by-side look at the Contracts Wizard and Texas Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Contracts Wizard 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?
Choose Contracts Wizard when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
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 | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 56/100 · Good | 41/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 | None listed |
Tools & capabilities
Contracts Wizard 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.
Contracts Wizard
{
"mcpServers": {
"openzeppelin-contracts-wizard": {
"url": "https://mcp.openzeppelin.com"
}
}
}
Texas Code
{
"mcpServers": {
"texas-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-texas-code"
]
}
}
}
Frequently asked questions
Contracts Wizard is categorized under Legal and uses a remote HTTP/SSE transport. Texas Code belongs to Legal and uses a local stdio subprocess. Pick Contracts Wizard 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.
Contracts Wizard is listed as free. Auth: no auth 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 openzeppelin-contracts-wizard and texas-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Contracts Wizard has a quality signal of 56/100 (Good) with 1 views, 0 installs and 295 GitHub stars. Texas Code has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.