PAVE vs Exogram Authority Runtime
A side-by-side look at the PAVE and Exogram Authority Runtime 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 Exogram Authority Runtime 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 Exogram Authority Runtime when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
create_entities, create_relations, add_observations.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 36/100 · Fair | 59/100 · Good |
| 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 | None listed |
| Verified owner |
Tools & capabilities
PAVE tools
No tool names declared yet. Check the project README from the listing page.
Exogram Authority Runtime tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
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"
}
}
}
Exogram Authority Runtime
{
"mcpServers": {
"exogram-authority-runtime": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Frequently asked questions
PAVE is categorized under Developer Tools and uses a remote HTTP/SSE transport. Exogram Authority Runtime belongs to Developer Tools and uses a local stdio subprocess. Pick PAVE for developer tools work and Exogram Authority Runtime 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. Exogram Authority Runtime 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 exogram-authority-runtime 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. Exogram Authority Runtime has 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars.
