sovereign-exoself-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | No | API key for OpenRouter. Required when SOVEREIGN_PROVIDER_MODE=openrouter. | |
| SOVEREIGN_PROVIDER_MODE | No | Provider mode: mock, ollama, openrouter. Defaults to ollama. | ollama |
| SOVEREIGN_OLLAMA_CRITIC_MODEL | No | Model for critic role when using Ollama. | |
| SOVEREIGN_OLLAMA_WORKER_MODEL | No | Model for worker role when using Ollama. | |
| SOVEREIGN_OLLAMA_MANAGER_MODEL | No | Model for manager role when using Ollama. | |
| SOVEREIGN_OLLAMA_ARCHIVIST_MODEL | No | Model for archivist role when using Ollama. | |
| SOVEREIGN_OLLAMA_SYNTHESIZER_MODEL | No | Model for synthesizer role when using Ollama. |
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 |
|---|---|
| council_runD | Run the bounded personal council. |
| memory_manageB | Search, store, list, delete, export, or profile memory. |
| system_statusA | Return local health without calling a provider. |
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 3 tools
Each tool has a clearly distinct domain: running a council, managing memory, and checking system status. There is no overlap in functionality, so an agent can easily select the right tool.
Tools use a consistent underscore-separated, lowercase pattern. The first two are noun-verb compounds (council_run, memory_manage), while system_status is a noun-noun compound, creating a minor inconsistency, but it's still readable and recognizable.
With only three tools, the server is tightly focused on the core functions of a personal exoself: decision-making (council), memory, and health. The count is small but each tool has a clear purpose and fits within the typical well-scoped range.
The memory_manage tool covers a full range of memory operations, and council_run covers the main action for the council. A possible gap is the lack of configuration or lifecycle management for the council, but for a bounded personal council, this may be sufficient, so the core workflows are covered.