MCP control plane: local server discovery, profiles, capability bundles, and policy audits.
MCPpedia last refreshed this data
io.github.ellmos-ai/ellmos-controlcenter-mcp is an MCP server that MCP control plane: local server discovery, profiles, capability bundles, and policy audits. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 89/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"controlcenter": {
"command": "ellmos-controlcenter"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Part of the ellmos-ai family.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'ellmos-controlcenter-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked ellmos-controlcenter-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Transport for TMCP using STDIO
The graph based agentic IDE
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.
MCP Security Weekly
Get CVE alerts and security updates for io.github.ellmos-ai/ellmos-controlcenter-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Part of the ellmos-ai family.
[!NOTE] LLM / AI Agent Integration: This repository provides an
llms.txtindex file for context optimization, RAG discovery, and agent navigation.
Quick Start • System Architecture • Control & Gateway Flow • Tools (31) • Gateway • Security Policy • llms.txt Context • Ecosystem Matrix
An alpha-stage Model Context Protocol (MCP) administration server 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 "control" means here — read this before you rely on it. ControlCenter is a read-mostly administration surface. It reads, inventories, resolves, audits, and generates configuration. Its only write actions are generating an MCP config file (
controlcenter_switch_profile) and writing a catalog (controlcenter_build_catalog); the dashboard can additionally toggle servers in a profile file, with confirmation and backup.It does not change a running session, does not sit in the request path, does not proxy or execute another server's tools, and does not enforce any permission. In the ellmos taxonomy it is a control plane in the narrow sense — it administers MCP servers, profiles, and stacks without owning domain data — not a gateway.
Provider note: ControlCenter works with any MCP-capable client (Claude Code, Codex, Gemini, or any stdio-based MCP host). The profile management tools default to Claude Code's profile directory (
~/.claude/profiles) but accept any directory viaELLMOS_PROFILE_ROOT. The skill and plugin inventory tools are scoped to Claude Code conventions by default; see the environment variables below for override options.
The first alpha release focuses on discovery, profile visibility, dashboard workflows, capability bundles, profile-aware tool-list probes, tool-bundle assignments, internationalization, and initial policy audits. Since 0.5.0 a gateway is added on top: `controlcenter_list_available_too