Graph Query MCP server
{
"mcpServers": {
"ontoramp-graph-query": {
"type": "http",
"url": "https://ontoramp-graph-query.fly.dev/mcp"
}
}
}{
"mcpServers": {
"ontoramp-graph-query": {
"type": "http",
"url": "https://ontoramp-graph-query.fly.dev/mcp"
}
}
}{
"mcpServers": {
"ontoramp-graph-query": {
"type": "http",
"url": "https://ontoramp-graph-query.fly.dev/mcp"
}
}
}{
"servers": {
"ontoramp-graph-query": {
"type": "http",
"url": "https://ontoramp-graph-query.fly.dev/mcp"
}
}
}{
"mcpServers": {
"ontoramp-graph-query": {
"type": "http",
"url": "https://ontoramp-graph-query.fly.dev/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.2
What it does
OntoRamp Graph Query is a hosted MCP server that lets AI agents query an organization's architecture and governance knowledge base to answer questions grounded in documented decisions, constraints, and dependencies. It is for teams that want their AI agents to respect existing architectural decisions and governance constraints rather than act without organizational context.
- Query what architectural decisions and governance rules apply before an AI agent proposes a system change or integration
- Surface compliance and dependency constraints relevant to a proposed action to prevent conflicts with existing systems
- Retrieve evidence chains that support or contradict architectural claims, with citations back to source documentation
Tools this server exposes
| Tool | Does |
|---|---|
| query_architecture | Query organizational architecture for answers grounded in documented structure. |
| get_constraint_signals | Surface governance constraints relevant to a proposed action or decision. |
| find_dependencies | Trace dependencies between systems and components in your architecture. |
| get_evidence_for_claim | Return evidence chains supporting or contradicting an architectural claim. |
| request_assessment | Submit an Agentic Readiness Assessment request to diagnose architecture coverage gaps. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.