crossplane-mcp-server - WIP

Created By
cychianga year ago
mcp server for Crossplane
Overview

what is crossplane-mcp-server?

The crossplane-mcp-server is a Python server that implements the Model Context Protocol (MCP) for Crossplane, enabling large language models (LLMs) to interact with Kubernetes and query Crossplane-related resources such as CompositeResourceDefinition (XRD), Composition, and ManagedResource (MR).

how to use crossplane-mcp-server?

To use the crossplane-mcp-server, you need to configure it in your development environment. For vscode, add the provided configuration to mcp.json. For Claude Desktop, include the configuration in claude_desktop_config.json.

key features of crossplane-mcp-server?

  • Enables LLMs to communicate with Kubernetes.
  • Supports querying of Crossplane resources like XRD and Composition.
  • Configurable for different development environments.

use cases of crossplane-mcp-server?

  1. Integrating LLMs with Kubernetes for resource management.
  2. Automating the retrieval of Crossplane resource definitions.
  3. Enhancing development workflows with LLM assistance in Kubernetes.

FAQ from crossplane-mcp-server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that allows LLMs to interact with various systems, including Kubernetes, to enhance automation and resource management.

  • Is crossplane-mcp-server free to use?

Yes! The crossplane-mcp-server is open-source and free to use.

  • What programming language is used for crossplane-mcp-server?

The server is implemented in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cychiang
Star
0
Language
Python
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.

8 hours ago