PAVE vs Companies House
A side-by-side look at the PAVE and Companies House MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PAVE for developer tools work over a hosted endpoint; choose Companies House for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose PAVE when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
Choose Companies House when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
COMPANIES_HOUSE_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 36/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | COMPANIES_HOUSE_API_KEY |
| Verified owner |
Tools & capabilities
PAVE tools
No tool names declared yet. Check the project README from the listing page.
Companies House 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.
PAVE
{
"mcpServers": {
"pave": {
"url": "https://api.pavecfi.com/mcp"
}
}
}
Companies House
{
"mcpServers": {
"companies-house": {
"command": "npx",
"args": [
"-y",
"companies-house-mcp"
],
"env": {
"COMPANIES_HOUSE_API_KEY": "YOUR_COMPANIES_HOUSE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
PAVE is categorized under Developer Tools and uses a remote HTTP/SSE transport. Companies House belongs to Developer Tools and uses a local stdio subprocess. Pick PAVE for developer tools work and Companies House for developer tools.
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.
PAVE has no declared pricing — check the project's own site. Companies House 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 pave and companies-house as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PAVE has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Companies House has 47/100 (Fair) with 3 views, 0 installs and 13 GitHub stars.
