Everything2MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVERYTHING2MCP_DATA_DIR | No | Registration persistence directory (JSON). | data |
| EVERYTHING2MCP_SSE_PATH | No | Legacy SSE GET path. | /sse |
| EVERYTHING2MCP_HTTP_HOST | No | HTTP/SSE bind address. | 127.0.0.1 |
| EVERYTHING2MCP_HTTP_PATH | No | Streamable HTTP path. | /mcp |
| EVERYTHING2MCP_HTTP_PORT | No | HTTP/SSE port (avoid 3000/5173/8080). | 8742 |
| EVERYTHING2MCP_TRANSPORT | No | Transport: `stdio` (default) / `http` / `sse`. | stdio |
| EVERYTHING2MCP_HTTP_TOKEN | No | Shared secret; required before leaving loopback; empty means no auth (local only). | |
| EVERYTHING2MCP_INTEGRITY_KEY | No | Optional HMAC key; can also be placed at `dataDir/.integrity-key`. Empty means SHA-256 only. | |
| EVERYTHING2MCP_DISCOVERY_MODE | No | Console auto-discovery mode: `auto` / `manual` / `off` (defaults to `off` under `node --test`). | auto |
| EVERYTHING2MCP_DISCOVERY_SCOPES | No | Additional private-network ranges (host / domain / CIDR ≤ /16), comma-separated. | |
| EVERYTHING2MCP_DISCOVERY_ENABLED | No | Whether to expose the `discovery_probe` tool; `false` also turns off auto-discovery. | true |
| EVERYTHING2MCP_DISCOVERY_EXCLUDE | No | Exclusion list for auto-discovery. | |
| EVERYTHING2MCP_HTTP_TOKEN_HEADER | No | Extra token header (Authorization / x-api-key are still accepted). | |
| EVERYTHING2MCP_RATE_LIMIT_INVOKE | No | Max business invokes per minute under Safe; `0` = unlimited. Skipped in Full. | 60 |
| EVERYTHING2MCP_SSE_MESSAGES_PATH | No | Legacy SSE POST path. | /messages |
| EVERYTHING2MCP_RATE_LIMIT_DISCOVER | No | Max discover calls per minute under Safe; `0` = unlimited. Skipped in Full. | 20 |
| EVERYTHING2MCP_DISCOVERY_TIMEOUT_MS | No | Single probe timeout in milliseconds. | 2500 |
| EVERYTHING2MCP_DISCOVERY_INTERVAL_MIN | No | Auto mode interval in minutes (5–1440). | 30 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_listA | List tools by layer: management (mcp_*/discovery_*) vs business (protocol.name.op). Default layer=business so agents are not flooded. |
| mcp_addB | Dynamically register a protocol endpoint. Tools appear immediately as namespaced MCP tools (protocol.name.operation). |
| mcp_updateC | Update an existing registration's config and reconnect/reload its tools |
| mcp_removeA | Disconnect an adapter and unregister its tools (same Catalog path as capability_unregister). Control-plane: does not require allowWrite. |
| mcp_query_by_protocolC | Filter live adapters and tools by protocol type |
| mcp_healthB | Process + adapter health snapshot for agents (live/restore_failed, tool counts) |
| mcp_explain_toolB | Explain a namespaced MCP tool: adapter, protocol, local operation, input schema |
| mcp_plan_bridgeA | Turn a natural-language goal into recommended protocols, example configs, and next MCP tool calls. Does not scan by itself. |
| mcp_add_from_discoveryC | Register an adapter from a discovery_suggest payload (protocol + name + config + confidence) |
| schema_importA | Import OpenAPI, WSDL, proto, GraphQL SDL, or AsyncAPI from a URL or file (OpenAPI servers[] become config.baseUrl). OData / JSON:API / tRPC / Connect-RPC are import-first: export OpenAPI (or pass gRPC target for Connect proto). |
| mcp_blacklist_listA | List operator blacklist entries. Match key is canonical protocol + host + port (or normalized url). See docs/BLACKLIST.md. |
| mcp_blacklist_addA | Add a blacklist entry. kind=target (default): protocol + host+port or network url; blocks mcp_add, discovery register and invoke on matching adapters. kind=capability: adapterId (protocol:name); hides and blocks that one instance. kind=tool: pattern (exact tool name or glob, * = one segment, ** = any, e.g. redis.*.flushall); hides and blocks matching tools. Blacklist still applies in Full mode. |
| mcp_blacklist_removeC | Remove a blacklist entry by id (protocol|host|port, cap|, or tool|) |
| environment_inventoryA | On-demand Environment Plane snapshot (OS/arch, permission hints, listening ports best-effort, runtimes, container clues, config paths). Feeds suggest only — never auto-registers, never sets allowWrite=true. |
| capability_registerB | Hot-add a capability through the shared Policy Gateway (same path as mcp_add). Pass a suggestion or protocol/name/config. auto:true only works for Safe + readonly + non-blacklist. Suggest never bulk-registers. |
| capability_unregisterA | Hot-delete a live capability through the shared Policy Gateway (same path as mcp_remove). Removes the adapter instance and its tools immediately. Control-plane: does not require allowWrite. Console REST requires confirm:true. Missing id is E_NOT_FOUND. |
| capability_configureC | Reconfigure a live capability (same path as mcp_update). Does not silently enable writes. |
| partner_listB | List southbound Partner connections (ingress=partner). Agent-facing northbound is still MCP only. Apps do not implement MCP. |
| compat_scanC | Compat Catalog scan: P0 installed∩catalog + Partner drops; P1 login clues; P2 ports; P3 mcpServers as mcp_bridge 兜底 only; P4 desktop UI deferred. Scan never opens write/desktop/secrets. |
| discovery_suggestB | Map probe/scan candidates to one-click mcp_add drafts (protocol, name, config, confidence). Pass candidates or a host to scan first. |
| discovery_probeB | Probe a single host+port for common OpenAPI/SOAP/GraphQL paths. CIDR / ranges are never allowed. |
| discovery_scan_hostB | Parallel single-host discovery: OpenAPI/WSDL/GraphQL paths, gRPC reflection, Redis PING, MQTT CONNECT, Modbus, CoAP, NATS INFO, JSON-RPC/XML-RPC, Pulsar 8080/6650, GCS 4443, Influx 8086, OSS headers, SMTP 25/587 220-banner. CIDR / ranges are never allowed (EVERYTHING2MCP_DISCOVERY_ALLOW_SCAN is ignored). Timeouts + SSRF (blocks metadata IPs). |
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 22 tools
Several tools have unclear boundaries: mcp_add vs capability_register, mcp_remove vs capability_unregister, mcp_update vs capability_configure, and mcp_add_from_discovery vs capability_register are nearly identical in purpose, with descriptions explicitly noting they share the same catalog/policy path. mcp_list, mcp_query_by_protocol, and various discovery tools have distinct scopes but overall the set is hard to distinguish.
Mixed conventions: snake_case throughout but with inconsistent prefixes (mcp_*, capability_*, discovery_*, partner_*, environment_*, compat_*) and no predictable pattern. The use of both mcp_ and capability_ prefixes for essentially the same operations further breaks consistency.
22 tools is on the high side for a server whose purpose seems to be managing MCP integrations and discovery. While each tool has a hypothetical role, many are redundant (e.g., multiple add/remove/update paths), making the surface feel heavy.
Core lifecycle operations (add, remove, update, list) are present, but the domain—managing MCP adapters, discovery, and blacklisting—has notable gaps: no explicit tool for querying tool details (except mcp_explain_tool), no pagination for mcp_list, and no clear way to manage partner connections beyond listing. Some operations are only partially covered.