OpenStack MCP + Agent PoC

Created By
Akroga year ago
An OpenStack MCP server PoC
Overview

what is OpenStack MCP + Agent PoC?

OpenStack MCP + Agent PoC is a proof of concept project that demonstrates how to run an OpenStack MCP server along with a basic agent program to interact with it using a large language model (LLM).

how to use OpenStack MCP + Agent PoC?

To use this project, clone the repository, configure the MCP server with your OpenStack deployment details, and run both the MCP server and the agent in separate terminal windows. Follow the QuickStart guide for detailed instructions.

key features of OpenStack MCP + Agent PoC?

  • Integration with OpenStack components using OpenAPI specifications.
  • Ability to run multiple MCP servers for different OpenStack components.
  • Interaction with MCP servers through an LLM for querying and managing OpenStack resources.

use cases of OpenStack MCP + Agent PoC?

  1. Testing OpenStack deployments with a conversational interface.
  2. Automating queries about OpenStack resources and configurations.
  3. Demonstrating the capabilities of LLMs in managing cloud infrastructure.

FAQ from OpenStack MCP + Agent PoC?

  • What is required to run this project?

You need access to an OpenStack deployment and an LLM, along with the uv package manager.

  • Can I customize the MCP server configuration?

Yes, you can edit the servers.yaml file to configure the MCP server according to your OpenStack cluster.

  • How does the agent interact with the MCP server?

The agent sends queries to the MCP server and receives responses based on the OpenStack API.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Akrog
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago