symapse
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@symapseexplain the architecture of this project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Symapse
Architectural awareness engine for AI coding agents
Install
npm install -g symapseRequires Node.js 22+. No dependencies. Zero config.
Related MCP server: Code Search MCP
Quick Start
# Index your project
symapse index /path/to/repo
# Start the MCP server (for OpenCode/Cursor/Claude integration)
symapse mcp /path/to/repo
# Query from the terminal
symapse_ask "add notification system"
symapse_find login
symapse_map "direct login after payment"
symapse_audit 10
symapse_health
# Live coding awareness — start watching for collisions, breaks, and dead code
symapse_health --watchOpenCode Integration
Install Symapse first:
npm install -g symapseAdd to your project's opencode.json:
{
"mcp": {
"symapse": {
"type": "local",
"command": ["npx", "symapse", "mcp", "."],
"enabled": true
}
}
}Create an AGENTS.md in your project root with:
## RULE 1: Always check Symapse first
| Instead of... | Use... |
|---|---|
| Reading files for architecture | `symapse_map` |
| Grepping for symbols | `symapse_find` |
| Guessing where code goes | `symapse_ask` |
| Finding dead code or duplicates | `symapse_audit` |
| Re-indexing or checking status | `symapse_health` |
First action every session: `symapse_ask "<request>"`. If it returns questions, ASK them.
If Symapse doesn't answer your question, read files.Tools
Tool | Question it answers |
| What should I know before working on X? |
| Where is X and what does it touch? |
| Show me the shape of this repo / feature |
| What's wrong, unused, or duplicated? |
| After changes: what did I affect? What did watch detect? |
| What's the state of the index? Watch mode |
Temporal workflow:
Before coding:
symapse_ask→symapse_map→symapse_findDuring coding:
symapse_health --watchAfter each edit:
symapse_diffMaintenance:
symapse_audit|symapse_health
Supported Languages
JavaScript, TypeScript, Python, Go, Rust, C#, PHP, Ruby, Lua, and C.
How It Works
Index — walks the repo, extracts functions/classes/methods with regex parsers, builds call and import edges
Store — normalized SQLite schema, incremental by mtime + engine version
Expose — CLI, REST API, and MCP over stdio. All share the same engine.
Self-Improving
Symapse learns from agent behavior across sessions without any user involvement:
Session coherence — biases context toward the subsystem the agent is already exploring
Usage signals — logs which symbols agents actually drill into
Workflow memory — auto-detects repeated symbol sequences across sessions
Intent classification — routes config/docs questions away from source code exploration
Architecture
packages/
engine/ — regex-based parser, call graph, all analysis tools
db/ — SQLite persistence with incremental indexing
mcp/ — MCP protocol server (JSON-RPC over stdio)
apps/
cli/ — command-line entry point
api/ — HTTP API server + web dashboard
web/ — terminal-style web UILicense
AGPL-3.0
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- 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/atobouh/symapse'
If you have feedback or need assistance with the MCP directory API, please join our Discord server