Edge Flow Manager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EFM_USER | No | Username for HTTP Basic authentication, only if EFM enforces it | |
| EFM_BASE_URL | Yes | Base URL of the EFM API, e.g., http://efm-host:10090/efm/api | |
| EFM_PASSWORD | No | Password for HTTP Basic authentication, only if EFM enforces it | |
| EFM_READONLY | No | Whether to enable read-only mode, default 'true' | |
| MCP_TRANSPORT | No | Transport mode: 'stdio' or 'sse' | |
| EFM_VERIFY_SSL | No | Whether to verify SSL certificates: 'true', 'false', or path to CA bundle | |
| EFM_MCP_RETRIES | No | Number of retries for MCP requests | |
| EFM_MCP_TIMEOUT | No | Timeout for MCP requests | |
| EFM_MCP_RETRY_WAIT | No | Wait time between retries |
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 |
|---|---|
| efm_list_agent_classesA | List every agent class EFM manages (name, description, and the agent manifest(s) each class is bound to). An agent class groups MiNiFi agents that share one flow — the top of the edge hierarchy. |
| efm_get_agent_classA | Detail for one agent class: its manifest ids, monitoring config, and any Designer flow association. Start here to resolve a class to its manifest. |
| efm_list_agentsA | List enrolled MiNiFi agents with their last-heartbeat timestamp (status/firstSeen/lastSeen) — the primary online/offline signal. Pass agent_class to filter to one class; omit it for every agent. |
| efm_get_agentA | Full record for one agent: its class, device/host, manifest hash, and heartbeat/status detail. Use to confirm which manifest an agent actually reports. |
| efm_get_class_monitorB | Per-class health view: current flow version, agent counts (online / missing), health status, and connection metrics. The fastest answer to "is this class healthy and how many agents are up?". |
| efm_get_manifestA | The agent manifest(s) for a class: the processor, controller-service, and reporting-task types that class can run. This is what tells you whether a flow you want to build is even deployable to that class's agents. |
| efm_get_manifest_by_idA | One agent manifest by its id (as listed on an agent class or agent record). Returns the full component-type catalog with property descriptors. |
| efm_list_flowsA | One summary per agent class: |
| efm_get_flowA | The full live Designer flow document for a flowId: process groups, processors, connections, controller services, and parameters. Ground truth for what an agent class is running — read this before reasoning about a flow. |
| efm_validate_flowA | Validation results for a flow — the same check EFM runs before a publish. Surfaces invalid/misconfigured components without changing anything. |
| efm_list_resourcesA | All resources in EFM's resource manager (assets and extension bundles), with names, types, and SHA-512 digests — the files EFM can push to agents. |
| efm_list_class_resourcesA | Resources currently assigned to one agent class — the assets/extensions EFM syncs to every agent in that class on its next heartbeat. |
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
Each tool targets a distinct resource or action: classes, agents, manifests, monitors, flows, resources. Even similar pairs (e.g. efm_get_manifest vs efm_get_manifest_by_id) are separated by query key, and efm_list_resources vs efm_list_class_resources differ by scope.
All tools follow a consistent efm_<verb>_<noun> snake_case pattern. List/get are used predictably, and compound nouns like class_monitor and class_resources are clear. Minor suffix variations (by_id) are still systematic.
12 tools is a well-scoped set for an edge flow manager: enough to cover the main entities (agent classes, agents, flows, manifests, resources) without bloat.
The read/query surface is thorough: classes, agents, manifests, flows, resources, health. Validation is included enough to test flows. However, there are no publish/update/delete operations, and resource assignment is only readable, so management actions are missing.