mcp-ad4m
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AD4M_GQL_URL | No | GraphQL endpoint URL for the AD4M executor | http://localhost:4000/graphql |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ad4m_agent_statusA | Get the local AD4M agent status: DID, initialization state, keystore lock state. |
| ad4m_list_perspectivesA | List all Perspectives on the local AD4M executor. |
| ad4m_create_perspectiveA | Create a new named Perspective. Returns its UUID for subsequent link operations. |
| ad4m_write_memoryA | Write a signed LinkExpression (source → predicate → target) to a Perspective. Auto-optimizes the graph every 10 writes across all terminals. |
| ad4m_recallA | Query links from a Perspective by source, predicate, or target. Omit any field to match all. |
| ad4m_get_neighbourhoodB | Read a shared AD4M Neighbourhood by Perspective UUID. |
| ad4m_classifyA | Classify a piece of information by which layer it belongs to: ad4m, local, env, or relay. Run this BEFORE ad4m_write_memory if unsure. |
| ad4m_config_checkA | Check whether mcp-ad4m is registered in the correct config file. Detects the wrong-file misconfiguration that causes silent connection failures. |
| ad4m_optimizeA | Audit the memory graph for duplicates and stale entries. dry_run: true (default) reports without deleting. |
| ad4m_statsB | Memory graph statistics: total links, duplicates, breakdown by predicate, oldest and newest entries. |
| ad4m_delete_memoryA | Remove links from a Perspective by source, predicate, and/or target filter. Returns matched/removed/failed counts. |
| relay_writeA | Write a cross-terminal relay message to AD4M. Both terminals share the same AD4M executor so state is immediately visible. |
| relay_readA | Read cross-terminal relay messages from AD4M. Optionally filter by session_id or since a timestamp. |
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 13 tools
Each tool addresses a distinct operation: status, classification, config, perspective CRUD, link query/write/delete, optimization, stats, and relay messaging. No two tools have overlapping purposes; even similar-sounding tools like recall and stats serve different functions (query vs. summary).
Most tools follow the ad4m_ prefix with snake_case, but two tools (relay_read, relay_write) use a relay_ prefix instead. This minor inconsistency is clear and does not cause confusion, but it prevents a perfect score.
13 tools cover the core AD4M operations: agent management, perspective lifecycle, link manipulation, optimization, statistics, and relay messaging. The count feels well-proportioned for the domain, with no obvious bloat or insufficiency.
The set covers essential operations: create, read, list, delete for perspectives and links, plus classification, optimization, stats, and relay. Missing are update operations for perspectives or links, but these may be less critical in an immutable or signed-graph context. Minor gap.