A side-by-side look at the California Tax Appeals and Tennessee Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose California Tax Appeals for legal work as a local process; choose Tennessee 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?
C
Choose California Tax Appeals when
You need dedicated capabilities in the Legal domain.
No tool names declared yet. Check the project README from the listing page.
Tennessee 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.
California Tax Appeals is categorized under Legal and uses a local stdio subprocess. Tennessee Code belongs to Legal and uses a local stdio subprocess. Pick California Tax Appeals for legal work and Tennessee 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.
California Tax Appeals is listed as free. Auth: no auth required. Tennessee Code is listed as free. Auth: no auth required. 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 california-tax-appeals and tennessee-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, California Tax Appeals has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Tennessee Code has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.