MCP server exposing FC operations as MCP tools
Until 2026-09-27 this record combined several servers published from one repository. The others now have records of their own: fc-mcp-external. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"fc-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# FC MCP Server An [MCP](https://modelcontextprotocol.io/) server, built on [FastMCP](https://github.com/jlowin/fastmcp), that exposes FC operations as MCP tools. Under the hood every tool shells out to `fc-client`, so an AI agent can lock/unlock resources, query status, run console/ssh/power commands, and drive image deploy/flash workflows. ## Architecture The server is plugin based. `mcp_server.py` creates the FastMCP instance, loads the internal plugin, then auto-discovers external plugins. ``` fc_mcp/ mcp_server.py # entry point (fc-mcp), transport handling mcp_base.py # MCPPlugin base class + shared helpers mcp_plugins/ internal/fc_mcp.py # core fc-client operations (always loaded) external/ uuu_bcu_mcp.py # UUU/BCU flashing tools (sample external plugin) uboot_mcp.py # U-Boot console deploy tools: predeploy / uri / livedeploy (sample) deploy_recommender_mcp.py# deploy method recommender (entry point) ``` Any `*_mcp.py` file placed under `mcp_plugins/external/` that exposes a `Plugin` class is discovered and loaded automatically at startup. ## Installation From the repository root: ```bash python setup.py install fc-mcp ``` This installs the `fc-mcp` console entry point. Requires Python >= 3.10 and `fastmcp >= 2.3` (needed for the Streamable HTTP transport). ## Starting the server The server supports two transports. **stdio** is the default and is what a local client (for example `fc-agent`, which launches the server as a subprocess) uses. **Streamable HTTP** runs the server as a standalone HTTP service so remote / third-party MCP clients can connect. ### stdio (default) ```bash fc-mcp ``` The client is responsible for spawning the process and talking JSON-RPC over stdin/stdout. ### Streamable HTTP ```bash # Local only (default host 127.0.0.1, port 8000, path /mcp) fc-mcp --transport http # Expose to the network fc-mcp --transport http --host 0.0.0.0 …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.