Texas Ag Opinions vs Wisconsin Code
A side-by-side look at the Texas Ag Opinions and Wisconsin Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
Texas Ag OpinionsLegal · Local subprocess (stdio)Texas Attorney General opinions — statute-citation search over recorded45FairAuth: no auth requiredVerdict: choose Texas Ag Opinions for legal work as a local process; choose Wisconsin 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?
TChoose Texas Ag Opinions when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Wisconsin Code when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You want tools like
wi_statute.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Texas Ag Opinions | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 45/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Texas Ag Opinions | View Wisconsin Code |
Tools & capabilities
Texas Ag Opinions tools
No tool names declared yet. Check the project README from the listing page.
Wisconsin Code tools 1
wi_statuteGet the FULL TEXT of a section of the Wisconsin Statutes — Wisconsin state law — by citation. "Wis. Stat. 940.01" is first-degree intentional homicide. Returns the statutory text. Keyless. Use for "what does Wisconsin Statute 940.01 say" or to check a Wisconsin statute a case relies on.
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.
Texas Ag Opinions
{
"mcpServers": {
"texas-ag-opinions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-texas-ag-opinions"
]
}
}
}
Wisconsin Code
{
"mcpServers": {
"wisconsin-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-wisconsin-code"
]
}
}
}
Frequently asked questions
Texas Ag Opinions is categorized under Legal and uses a local stdio subprocess. Wisconsin Code belongs to Legal and uses a local stdio subprocess. Pick Texas Ag Opinions for legal work and Wisconsin 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.
Texas Ag Opinions is listed as free. Auth: no auth required. Wisconsin 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 texas-ag-opinions and wisconsin-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Texas Ag Opinions has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Wisconsin Code has 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars.