Neuron - "Synapse"
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NS_DB_PATH | No | Path to the Turso/SQLite database file. Default is 'graph.db' in the current directory. | graph.db |
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 |
|---|---|
| statusA | Current graph state: nodes, links, health, configuration. Safe first call to see if the memory holds anything. New to Neuron? The core workflow is a 2-step loop each substantive turn: pre_turn (before) then store_turn (after); call |
| store_turnA | MEMORY LOOP — STEP 2 (after replying). Call this AFTER you answer a substantive turn, to persist what is new into long-term memory. Curate for a clean graph: topic = 3-5 words; keywords = 3-5 CONCEPT nouns / entities / tech (never verbs or filler like 'use', 'make'); links = typed edges between keywords (never link a keyword to itself). This is the preferred way to save — cleaner than auto(). Skip on trivial turns (greetings, acknowledgements, yes/no). |
| get_contextA | Retrieve related nodes and links for a topic/keyword — what the memory already knows. Call BEFORE answering when a question may have prior context worth recalling. For the normal start-of-turn load, prefer pre_turn (one shot: status + compact context). |
| confirmA | Feedback signal: confirm that context retrieved from the graph was useful. Boosts salience of specified keywords so they surface more prominently in future get_context calls. Call this when retrieved context directly influenced your response. Skipping is safe — it only affects future retrieval quality. |
| find_candidatesA | Screening: find existing similar keywords (vector search). Call BEFORE store_turn. |
| vector_searchB | Semantic vector search. Find similar keywords via Turso vector_distance_cos or a Python cosine fallback (384-dim fastembed embeddings, NS_EMBED_MODEL). |
| summaryB | Textual graph summary: top keywords, recent links, health, forgotten concepts |
| forgottenA | Find keywords not touched in N turns (decaying salience). Useful for rediscovering lost concepts. |
| pruneC | Force prune inactive tangential links |
| consolidateA | Consolidate the graph: merge near-duplicate concepts (cosine) and archive low-salience orphans to a recoverable _graveyard. Keeps the memory clean; safe to run periodically. |
| dedupC | Toggle keyword deduplication |
| flashB | Toggle semantic flashbacks |
| resetC | Reset the graph and start over |
| extractA | Automatic semantic extraction from text: keyword, topic, domain, intent, sentiment, entities. Heuristic (0 token) — no LLM extraction. |
| autoA | POST fallback (0-token): one-shot extract + topic-shift + auto-link + save. Prefer a curated store_turn when you can pick the concepts yourself; use auto only for throwaway turns. |
| exportC | Export the complete graph as JSON |
| mergeA | Merge duplicate or near-duplicate nodes. Moves all links from |
| switch_contextA | Switch active context (creates if new). E.g. 'java/spring', 'python/django'. |
| list_contextsB | List all available contexts with metadata. |
| pre_turnA | MEMORY LOOP — STEP 1 (before replying). Call this FIRST on any substantive turn to load relevant past context in one shot (status + get_context in compact form). Fold what it returns silently into your answer; do not announce it. Then reply, then call store_turn (step 2). Skip only on trivial turns or when the graph is empty. Ideal for clients without automatic context-injection hooks. |
| helpA | Show every Neuron command (one line each) plus how to use Neuron well. Call once at the start if unsure; full playbook: call skill(name='playbook'). |
| skillA | Return the FULL text of a Neuron skill/playbook on demand — token-cheap, fetch it only when you need the details. Use after the compact opener to load the complete workflow or curation rules. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| neuron-playbook | The full per-turn workflow: PRE/POST loop, extraction, linking, tools, provider notes. |
| neuron-curated-memory | How to curate turns so the graph stays clean: concept nouns, typed links, no self-links. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/recla93/Neuron'
If you have feedback or need assistance with the MCP directory API, please join our Discord server