Installation¶
pip install cloudg # the layer, the CLI and the dependency-free native server
pip install "cloudg[mcp]" # adds the official mcp SDK (mcp>=1.30,<3) for the SDK flavor and adapters
pip install fastmcp # only if you want the fastmcp flavor or mount into fastmcp
Python 3.11 or newer is required. Importing cloudg.mcp imports nothing outside cloudg's own
dependencies; mcp and fastmcp are imported lazily, inside the functions that need them.
What you get without the extra:
| Feature | Plain cloudg |
With cloudg[mcp] |
With fastmcp |
|---|---|---|---|
CloudGMCPLayer, in-process calls, export_definitions |
yes | yes | yes |
cloudg mcp tools / resources / prompts / call / read / config |
yes | yes | yes |
cloudg mcp serve --flavor native (stdio, HTTP, SSE) |
yes | yes | yes |
cloudg mcp serve --flavor sdk |
no | yes | yes (fastmcp depends on mcp) |
cloudg mcp serve --flavor fastmcp |
no | no | yes |
register_into(...) an SDK server |
no | yes | yes |
register_into(...) a fastmcp.FastMCP |
no | no | yes |
--flavor auto (the default) picks the SDK when mcp.server.lowlevel imports and falls back
to the native server otherwise, so cloudg mcp serve works either way.
The SDK flavor's HTTP transport runs on uvicorn and Starlette. Both arrive with the mcp
package; cloudg does not list them separately.
The CLI is reachable three ways, all running the same click group:
cloudg mcp serve # the mcp group on the main cloudg CLI
cloudg-mcp serve # stand-alone console script (pyproject: cloudg-mcp = "cloudg.mcp.cli:main")
python -m cloudg.mcp serve # module entry point, handy inside virtualenvs
If you installed cloudg in editable mode before 0.6.0, reinstall (pip install -e .) so the
cloudg-mcp script gets created. cloudg mcp config falls back to cloudg mcp serve or to
python -m cloudg.mcp serve when the script is missing.