Schema | aspark-graph

aspark-graph

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
build_graph	(Re)scan a repository and its .spark/ artifacts and persist the graph.
get_node	Look up a single node by its id (e.g. 'file:src/foo.py').
story_traceB	Full thread of a user story: acceptance criteria (with their latest QA verdict), mapped plan tasks, and any best-effort code links.
impactA	Blast radius of a change: the stories and acceptance criteria that depend on the given files (or the files in a git `diff` range), each tagged with its weakest-edge confidence. Pass either `files` or `diff`, not both.
gate_healthC	The aSPARK gate invariants as data: orphan tasks, unverified acceptance criteria, and open findings for a feature.
stalenessC	Report whether the built graph still matches the repo on disk (US-4).
find_nodesC	Find nodes whose id or name contains a substring, optionally by type.
get_neighborsC	Nodes within `depth` hops of a node (both directions); 'what touches this?'.
shortest_pathC	An ordered path connecting two nodes, or an explicit 'no path' result.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/a-lottes/aSPARK-graph'

If you have feedback or need assistance with the MCP directory API, please join our Discord server