mcp-resonance
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| observe_ecosystem_stateB | Get a snapshot of the current ecosystem state, including active patterns, couplings, and coherence metrics |
| record_ecosystem_momentB | Record a moment (event) from the ecosystem - a meditation, critique, insight, weave, or other observation |
| detect_emergent_patternsB | Analyze all observations to detect recurring patterns and emergent themes |
| visualize_coupling_graphB | Generate a text visualization of how MCPs and concepts are coupled together |
| suggest_next_synthesisB | Based on current patterns, suggest what action the system should take next (meditate, consult, weave, observe) |
| listen_for_harmonyC | Check if the system is in a state of resonance/harmony - when patterns strengthen each other |
| reset_observationsB | Clear all observations and patterns (useful for starting a new session) |
| couple_serversC | Prototype: Couple two MCP servers with an initial resonance strength (ports resonance-bridge) |
| resonateC | Prototype: Trigger resonant response from a server across its couplings (ports resonance-bridge) |
| balance_loadC | Prototype: Distribute an operation across available servers (ports resonance-bridge) |
| orchestrate_emergentC | Prototype: Create an emergent orchestration chain for an operation (ports resonance-bridge) |
| harmony_metricsC | 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 | |
TDQS
Scored across 12 tools
Most tools have distinct purposes, but there is some overlap between 'detect_emergent_patterns' and 'suggest_next_synthesis' as both analyze patterns to guide actions, which could cause confusion. Tools like 'balance_load' and 'orchestrate_emergent' are more clearly differentiated by focusing on distribution vs. orchestration.
Naming is inconsistent with a mix of verb_noun patterns (e.g., 'balance_load', 'couple_servers') and more descriptive phrases (e.g., 'listen_for_harmony', 'visualize_coupling_graph'). Some tools use underscores consistently, but the verb styles vary, lacking a unified convention.
With 12 tools, the count is reasonable for a server focused on resonance and ecosystem management. It covers monitoring, analysis, and orchestration without being overly bloated, though it might feel slightly dense for a niche domain.
The tool set provides good coverage for ecosystem observation, pattern detection, and resonance management, with tools for recording, resetting, and suggesting actions. Minor gaps might include more direct control over individual servers or detailed configuration, but core workflows are supported.