OpenStack-MCP
A Model Context Protocol server that provides 123 tools across 7 OpenStack domains (compute, network, storage, etc.) for managing cloud resources via natural language, with stateless per-caller authentication and Kolla log observability.
README
OpenStack-MCP
English | 한국어
A Model Context Protocol (MCP) server for OpenStack — 123 tools across 7 domains, built on openstacksdk, with stateless per-caller header auth, a declarative RESOURCES registry, and Kolla log observability.
Architecture
LLM client (Claude / any MCP host)
│ MCP protocol (stdio or HTTP/SSE)
▼
┌─────────────────────────────────────────────────────┐
│ server.py │
│ RESOURCES table → auto-generated list/show/ │
│ update/delete tools + hand-written specials │
│ │
│ _os_conn(ctx) ──► os_backend.py │
│ (per-caller creds) openstacksdk Connection │
│ (Keystone app credential) │
│ ▼ │
│ OpenStack APIs │
│ Nova · Neutron · Cinder │
│ Glance · Keystone · Octavia │
│ Placement │
│ │
│ ops_backend.py ──► Kolla log files (read-only) │
│ (observability) /var/log/kolla/* │
└─────────────────────────────────────────────────────┘
Per-domain HTTP mounts (stateful sessions for elicitation):
/compute/mcp /network/mcp /lbaas/mcp
/storage/mcp /image/mcp /identity/mcp
/observability/mcp
Each domain is an independent FastMCP instance. A shared process exposes all mounts; OSMCP_DOMAINS and OSMCP_TIERS narrow which tools are active.
Features
- Declarative registry —
RESOURCEStable +_make_list/_make_show/_make_update/_make_deletegenerators; adding a new resource is one dict entry. - Stateless per-caller auth — credentials are read from request headers on every call (HTTP) or from env vars (stdio). The server stores nothing; multiple callers with different credentials share one process safely.
- Structured error envelope — all tool errors surface as
Error executing tool <name>: {"error":{"type","message","http_status?}}. Parse from the first{. - Delete confirmation —
*_deletetools use MCP elicitation to require an explicit human"delete"choice before executing. Irreversible operations cannot be triggered by an LLM alone. - Key-columns / detail — list tools return a compact key-column view by default; pass
detail=Truefor all fields.limit=Ncaps row count.all_projects=Truefor the admin view where supported. - Multimount — 7 per-domain FastMCP instances served at
/<domain>/mcp, each carrying a routing map in itsinitializeinstructions so clients pick the right mount on the first try. - Kolla log observability —
log_targets,log_tail,log_traceread Kolla service log files directly from the host filesystem (mounted read-only), with time-window filtering, regex grep, and request-ID cross-service tracing.
Documentation
- Usage — install, stdio & HTTP modes, container, and configuration reference.
- Tool Reference — all 123 tools by domain.
Quick install:
git clone https://github.com/YeeDochi/OpenStack-MCP.git
cd OpenStack-MCP
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
Then see Usage to run in stdio or HTTP mode.
Extending: add a new resource
Create tools is intentionally not implemented — it is the primary extension point. To add a create tool or a new resource type:
- Add a function in
src/server.pyorsrc/os_backend.pyusing openstacksdk. - Register it with
add(fn, name="...", domain="...", tier="write"). - For a full CRUD resource, add one dict to
RESOURCESand aRESOURCE_DOMAINmapping entry;_make_list/_make_show/_make_update/_make_deletegenerate the tools automatically.
Any OpenStack service supported by openstacksdk can be wired in this way with a handful of lines.
Running tests
pytest -q
The smoke suite verifies: the tool registry is non-empty and contains the expected OpenStack tools (and excludes non-OpenStack ones), no legacy router module is present, and the Kolla log backend resolves targets/parses request IDs correctly.
License
MIT — see LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.