litcoin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEO4J_URI | Yes | LitCoin Knowledge Graph endpoint (default: bolt://litcoin-graph.apps.renci.org:7687). | bolt://litcoin-graph.apps.renci.org:7687 |
| NEO4J_PASSWORD | Yes | LitCoin Neo4j server authentication password. | |
| NEO4J_USERNAME | Yes | LitCoin Neo4j server authentication username. | |
| OPENAI_API_KEY | Yes | OPENAI API Key for semantic search related tools such as get_semantic_similar_nodes and get_semantic_similar_edges. |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_nodeD | – |
| get_node_edgesD | – |
| get_edges_betweenD | – |
| get_semantic_similar_edgesD | – |
| get_semantic_similar_nodesD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Tool names use distinct noun phrases (node, node_edges, edges_between, semantic_similar_edges, semantic_similar_nodes) that indicate different query targets. However, the absence of descriptions could cause confusion between get_node_edges and get_edges_between for an agent unfamiliar with the API.
All tools follow a consistent get_<noun> pattern with snake_case, making the naming predictable and uniform.
The server provides exactly 5 tools, which is a well-scoped number for a graph query server, not overwhelming or too sparse.
The surface covers node retrieval, edge retrieval, and semantic similarity queries, but lacks basic operations like listing all nodes/edges or fetching an edge by ID, leaving notable gaps for broader graph exploration.