elephantasm-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ELEPHANTASM_API_KEY | Yes | Your API key (starts with sk_live_) | |
| ELEPHANTASM_ANIMA_ID | No | Default anima ID (can be overridden per tool call) | |
| ELEPHANTASM_ENDPOINT | No | API endpoint | https://api.elephantasm.com/api |
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 |
|---|---|
| queryA | Search an Anima's brain across memories, knowledge, and identity. Returns relevant results ranked by semantic similarity to your query. Use this for general questions about what the Anima knows or remembers. |
| search_memoriesA | Semantic search across an Anima's memories. Returns memories ranked by similarity to your query. Use this when you want to find specific past experiences or interactions. |
| search_knowledgeA | Semantic search across an Anima's knowledge base. Returns canonicalized truths (facts, concepts, methods, principles, experiences) ranked by similarity. Use this for structured knowledge retrieval. |
| get_identityB | Get an Anima's identity profile — personality type, communication style, and self-reflection data. |
| ingest_eventA | Record an interaction event for future memory synthesis. Use this to capture messages, tool calls, or other signals that should become part of the Anima's long-term memory. |
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 5 tools
There is overlap between 'query', 'search_knowledge', and 'search_memories', as all three perform semantic search; descriptions help differentiate but ambiguity remains.
Most tools follow a verb_noun pattern (get_identity, ingest_event, search_knowledge, search_memories), but 'query' is a single verb without a noun, breaking consistency.
5 tools is well-scoped for the domain of managing an Anima's identity, events, and memory; each tool serves a clear purpose.
Core operations (get identity, record events, search) are present, but missing update/delete for identity and events, and no explicit tool to add knowledge directly.