Ravenroot Second Brain MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host interface to bind when using the HTTP transport (e.g., 127.0.0.1). | |
| MCP_PORT | No | Port to listen on when using the HTTP transport (e.g., 8765). | |
| MCP_TRANSPORT | No | Transport for the MCP server. Set to 'http' to run an HTTP server instead of the default stdio transport. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_graphB | Search the knowledge graph using BFS or DFS. Returns relevant nodes and edges as text context. |
| get_nodeB | Get full details for a specific node by label or ID. |
| get_neighborsC | Get all direct neighbors of a node with edge details. |
| get_communityB | Get all nodes in a community by community ID. |
| god_nodesB | Return the most connected nodes - the core abstractions of the knowledge graph. |
| graph_statsA | Return summary statistics: node count, edge count, communities, confidence breakdown. |
| shortest_pathA | Find the shortest path between two concepts in the knowledge graph. Follows stored edge direction by default; set undirected=true to ignore it. |
| list_prsA | List open GitHub PRs with CI status, review state, and graph impact (which communities each PR touches, blast radius). Use this before starting work to check if a PR already covers the area you're about to change. |
| get_pr_impactA | Get detailed graph impact for a specific PR: which files it changes, which knowledge-graph communities are affected, and how many nodes are touched. Use this to assess merge risk or check for overlap with your current work. |
| triage_prsA | Return all actionable open PRs (correct base, not stale) with full graph impact data so you can reason about review priority, merge order, and conflict risk. Call this when the user asks 'what PRs should I review?' or 'what's ready to merge?' |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Graph Report | Full GRAPH_REPORT.md |
| Graph Stats | Node/edge/community counts and confidence breakdown |
| God Nodes | Top 10 most-connected nodes |
| Surprising Connections | Cross-community surprising connections |
| Confidence Audit | EXTRACTED/INFERRED/AMBIGUOUS edge breakdown |
| Suggested Questions | Suggested questions for this codebase |
TDQS
Scored across 10 tools
The graph tools (query_graph, get_node, get_neighbors, get_community, god_nodes, graph_stats, shortest_path) each target a clearly distinct operation. The PR tools are mostly distinct, though list_prs and triage_prs overlap heavily—both return open PRs with graph-impact data—and only the descriptions' filtering nuance (actionable/correct base/not stale) separates them.
All names use consistent snake_case, which is predictable and readable. However, the verb pattern is not strictly uniform: several are noun phrases (god_nodes, graph_stats, shortest_path) while others are verb_noun (get_node, list_prs), a minor deviation.
Ten tools is well-scoped for a knowledge-graph query plus PR-triage server, with each tool earning its place. No redundancy that would push it toward bloat.
Read-side graph coverage is solid (search, fetch, neighbors, community, hubs, stats, pathfinding) and the PR workflow is covered from listing to impact to triage. The only gap is the absence of any mutation tools (add/update/delete node or edge), which an agent might expect for a 'second brain'.