Ellmos ControlCenter MCP Server

MCP control plane: local server discovery, profiles, capability bundles, and policy audits.

Remote serverstreamable-httpTypeScript

What is the Ellmos ControlCenter MCP server?

Ellmos ControlCenter MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP control plane: local server discovery, profiles, capability bundles, and policy audits.

What you get

An alpha-stage Model Context Protocol (MCP) control plane for local MCP stacks. ControlCenter discovers local MCP servers, reads MCP profile files, groups servers into capability bundles, recommends profiles for a task, builds catalogs, probes real MCP tool lists from local repositories or profiles, assigns tools to capability bundles, and provides an optional local dashboard.

What the assistant can call

Once Ellmos ControlCenter is connected, these are the calls the assistant has available:

  • controlcenter_status — Show stack, profile, and detected-server status
  • controlcenter_actual_self_receipt — Run a native self list_tools probe and emit a short-lived signed runtime receipt when explicitly configured
  • controlcenter_get_language — Show the current ControlCenter output language
  • controlcenter_set_language — Set the ControlCenter output language for this running server instance
  • controlcenter_list_local_servers — Scan local MCP repositories below the MCP root
  • controlcenter_list_stacks — Read registered stacks from stacks.catalog.json and validate their ellmos.stack.v2 manifests
  • controlcenter_describe_stack — Describe typed components, roles, policies, and validation warnings for one registered stack
  • controlcenter_context_pack — Build a bounded, manifest-only handoff for a registered stack at short, execution, or full detail
  • controlcenter_list_tools — Start local or profile-defined MCP servers and read their real list_tools output
  • controlcenter_find_capability — Rank typed native-binding claims from a hash-consistent System Explorer resolution without selecting or executing one
  • controlcenter_tool_overview — Show resolution-bound component claims while keeping declared and runtime-state axes separate
  • controlcenter_assign_tool_bundles — Assign probed MCP tools to capability bundles

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ellmos ControlCenter's toolset — controlcenter_status, controlcenter_actual_self_receipt, controlcenter_get_language and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ellmos-ai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ellmos ControlCenter.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the ellmos controlcenter mcp server does with a few real requests.

Available tools

ToolWhat it does
controlcenter_statusShow stack, profile, and detected-server status
controlcenter_actual_self_receiptRun a native self list_tools probe and emit a short-lived signed runtime receipt when explicitly configured
controlcenter_get_languageShow the current ControlCenter output language
controlcenter_set_languageSet the ControlCenter output language for this running server instance
controlcenter_list_local_serversScan local MCP repositories below the MCP root
controlcenter_list_stacksRead registered stacks from stacks.catalog.json and validate their ellmos.stack.v2 manifests
controlcenter_describe_stackDescribe typed components, roles, policies, and validation warnings for one registered stack
controlcenter_context_packBuild a bounded, manifest-only handoff for a registered stack at short, execution, or full detail
controlcenter_list_toolsStart local or profile-defined MCP servers and read their real list_tools output
controlcenter_find_capabilityRank typed native-binding claims from a hash-consistent System Explorer resolution without selecting or executing one
controlcenter_tool_overviewShow resolution-bound component claims while keeping declared and runtime-state axes separate
controlcenter_assign_tool_bundlesAssign probed MCP tools to capability bundles
controlcenter_list_bundlesGroup local servers by capability bundle
controlcenter_suggest_bundlesRecommend bundles for a task

How to install the Ellmos ControlCenter MCP server

{
  "mcpServers": {
    "controlcenter": {
      "command": "ellmos-controlcenter"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Ellmos ControlCenter to controlcenter status.
  • Use Ellmos ControlCenter to controlcenter actual self receipt.
  • Use Ellmos ControlCenter to controlcenter get language.

Frequently asked questions

It connects Ellmos ControlCenter to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (controlcenter_status, controlcenter_actual_self_receipt, controlcenter_get_language, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Ellmos ControlCenter directly.