A Model Context Protocol server that lets AI assistants understand a Crossplane control plane.
crossplane-mcp-server is an MCP project maintained in the ravibagri5/crossplane-mcp-server repository. The maintainer describes its purpose as “A Model Context Protocol server that lets AI assistants understand a Crossplane control plane”. Read the project documentation for the complete scope.
The project provides a local client configuration using crossplane-mcp-server. Follow the repository’s build and installation steps before copying it, and replace example paths with the paths on your own computer.
The example declares PATH, HOME. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| crossplane_managed_resources_summary | How many managed resources exist, by kind, and how many are Ready and Synced |
| crossplane_managed_resources_list | Which managed resources exist, optionally only the failing ones |
| crossplane_composite_resources_list | Which composite resources (XRs) exist and which Composition each selected |
| crossplane_claims_list | Which claims exist and which composite each is bound to |
| crossplane_resource_get | Everything about one resource: conditions, external name, events, manifest |
| crossplane_resource_tree | The composition tree below a claim or composite, with per-resource status |
| crossplane_resource_events | The events Crossplane recorded against one resource |
| crossplane_diagnose | Why a resource is not Ready, and which resource is actually at fault |
| crossplane_drift_detect | Which infrastructure no longer matches its declared spec, and whether that will be corrected |
| crossplane_providers_list | Which providers are installed and healthy |
| crossplane_functions_list | Which composition functions are installed and healthy |
| crossplane_configurations_list | Which configurations are installed and healthy |
| crossplane_package_get | One package plus its revisions, where image pull and dependency errors appear |
| crossplane_xrds_list | Which platform APIs this control plane offers |
| crossplane_xrd_schema | The fields a platform API takes, with a ready-to-edit example manifest |
| crossplane_compositions_list | Which Compositions exist and what pipeline they run |
| crossplane_composition_get | The full definition of one Composition |
| crossplane_composition_validate | Why a Composition does not work, without running anything |
| crossplane_composition_render | What a Composition would actually create, as a dry run |
| crossplane_environment_configs_list | Which EnvironmentConfigs exist and what data they hold |
| crossplane_deployment_runtime_configs_list | Which runtime configs exist and which packages use them |
| crossplane_managed_resource_definitions_list | Which managed resource kinds are Active, on Crossplane v2 |
| crossplane_managed_resource_activation_policies_list | Which policies activate those definitions |
| crossplane_clusters_list | Which control planes this server can reach |
| crossplane_status | The overall health of the control plane in one call |
| crossplane_unhealthy_resources | Everything that is currently failing, and why |
| crossplane_deleting_resources | What is stuck deleting, and what is holding it up |
| crossplane_usages_list | What is protected from deletion, and what needs it |
| crossplane_impact | What a deletion would destroy, and whether it would be blocked |
| crossplane_api_resources | The Crossplane API surface, to find exact kinds and groups |
| crossplane_database_create | Asks the control plane's own database API for a database, filling in the fields its XRD declares |
| crossplane_workload_create | The same for a workload, app or service |
| crossplane_resource_apply | Applies a Crossplane manifest, for XRDs, Compositions and specs you built yourself |
{
"mcpServers": {
"crossplane": {
"command": "crossplane-mcp-server",
"args": [
"--clusters",
"staging,production",
"--context",
"staging"
],
"env": {
"PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin",
"HOME": "/Users/you"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| PATH | Declared in the maintainer’s client configuration. | Check documentation |
| HOME | Declared in the maintainer’s client configuration. | Check documentation |
Inspect PostgreSQL schemas and run read-only queries with the archived MCP reference server. Review its maintenance status before choosing it.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.