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