EleSync
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recallA | Search the user's unified memory across all AIs. Use this at the start of
a task to recover context. |
| list_projectsA | List the user's EleSync projects and their short ids. Use this before
|
| recall_projectA | Search only the chats and memories collected in one EleSync project.
Use the id from |
| project_contextC | Return the approved project knowledge sheets, tasks, decisions, handoffs, and collected memories as a compact context package. |
| save_project_documentC | Save a project knowledge sheet, task, decision, or handoff. |
| rememberA | Save a new memory to the user's vault so every other AI can see it too.
Use for durable facts, preferences, project state — not throwaway chatter.
Pass your identity in |
| forgetA | Delete a memory by id (full or 8-char prefix shown by recall). |
| memory_statusA | Summary of what's in the vault: totals by source and type (limited to the memories this client's scope can see). |
| list_scopesA | List the memory scope compartments this client can see, with how many
memories each holds. |
| find_conflictsA | Surface facts in the vault that look like they're about the same thing but disagree (e.g. two different stated locations), each with its source and date. Use this to spot stale/contradictory memory and confirm with the user. |
| historyA | Show the supersession history of a memory (id or 8-char prefix): every
version that led to or replaced it, oldest first, with when each changed.
This is the "what was true when" view — use it to see what a fact used to
be after a memory was superseded (via |
| audit_logA | View the audit trail of operations on this vault. Shows who did what
and when — useful for reviewing which AI clients are reading or writing
memories. Audit logging is enabled by default; set ELESYNC_AUDIT=0 to disable it.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| recent | The most recent memories, as a readable digest. |
| memory_templates | Available capture templates, their fields, and the defaults they set. |
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/darknodebros/EleSync'
If you have feedback or need assistance with the MCP directory API, please join our Discord server