Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| observe_ecosystem_state | Get a snapshot of the current ecosystem state, including active patterns, couplings, and coherence metrics |
| record_ecosystem_moment | Record a moment (event) from the ecosystem - a meditation, critique, insight, weave, or other observation |
| detect_emergent_patterns | Analyze all observations to detect recurring patterns and emergent themes |
| visualize_coupling_graph | Generate a text visualization of how MCPs and concepts are coupled together |
| suggest_next_synthesis | Based on current patterns, suggest what action the system should take next (meditate, consult, weave, observe) |
| listen_for_harmony | Check if the system is in a state of resonance/harmony - when patterns strengthen each other |
| reset_observations | Clear all observations and patterns (useful for starting a new session) |
| couple_servers | Prototype: Couple two MCP servers with an initial resonance strength (ports resonance-bridge) |
| resonate | Prototype: Trigger resonant response from a server across its couplings (ports resonance-bridge) |
| balance_load | Prototype: Distribute an operation across available servers (ports resonance-bridge) |
| orchestrate_emergent | Prototype: Create an emergent orchestration chain for an operation (ports resonance-bridge) |
| harmony_metrics | Prototype: Inspect harmony, load distribution, and propagation metrics (ports resonance-bridge) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |