OpenStack MCP Server

Created By
DragomirAlina year ago
A lightweight and extensible service that enables AI assistants to securely execute OpenStack CLI commands via the Model Context Protocol (MCP)
Overview

What is OpenStack MCP Server?

OpenStack MCP Server is a lightweight and extensible service that allows AI assistants to securely execute OpenStack CLI commands via the Model Context Protocol (MCP). It is designed to work with the Claude Desktop application, enabling users to interact with OpenStack resources directly from the AI assistant.

How to use OpenStack MCP Server?

To use the OpenStack MCP Server, you need to install the required software, configure your OpenStack credentials in the application.yml file, and integrate it with the Claude Desktop application by updating the claude-desktop.json file with the server details.

Key features of OpenStack MCP Server?

  • Secure execution of OpenStack CLI commands through AI assistants.
  • Integration with Claude Desktop for seamless interaction.
  • Extensible architecture for future enhancements.

Use cases of OpenStack MCP Server?

  1. Listing OpenStack servers and projects through AI commands.
  2. Managing OpenStack resources using natural language prompts.
  3. Automating OpenStack CLI tasks via AI assistants.

FAQ from OpenStack MCP Server?

  • What are the prerequisites for using OpenStack MCP Server?

You need Java 21, Maven 3.8+, and the OpenStack CLI installed on your machine.

  • How do I configure OpenStack credentials?

Update the application.yml file with your OpenStack authentication URL, region name, and application credentials.

  • Can I use OpenStack MCP Server with other AI assistants?

Currently, it is designed to work with Claude Desktop, but it may be extended for other platforms in the future.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
DragomirAlin
Star
0
Language
Java
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago