plantoncloud/mcp-server-planton
If you are the rightful owner of mcp-server-planton and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.
The Planton Cloud MCP Server is a Model Context Protocol server designed to enable AI agents to query cloud resources using user permissions.
Planton Cloud MCP Server
MCP (Model Context Protocol) server for Planton Cloud that enables AI agents to query and manage cloud resources using user permissions.
Overview
The Planton Cloud MCP Server provides AI assistants like Cursor, Claude Desktop, and LangGraph agents with tools to interact with Planton Cloud resources. All queries respect your actual permissions through API key authentication.
Key Features:
- User-scoped permissions via API key authentication
- Query cloud resources, environments, organizations
- Create and manage cloud infrastructure
- Works with any MCP client (Cursor, Claude Desktop, LangGraph)
- Available as HTTP endpoint or local binary
Quick Start
Get Your API Key
- Log in to Planton Cloud Console
- Click your profile icon → API Keys
- Click Create Key and copy the generated key
Integration with Cursor
Add to your Cursor MCP settings (~/.cursor/mcp.json):
Remote Endpoint (Recommended)
{
"mcpServers": {
"planton-cloud": {
"type": "http",
"url": "https://mcp.planton.ai/",
"headers": {
"Authorization": "Bearer YOUR_PLANTON_API_KEY"
}
}
}
}
Local Testing with Docker
{
"mcpServers": {
"planton-cloud": {
"type": "http",
"url": "http://localhost:8080/",
"headers": {
"Authorization": "Bearer YOUR_PLANTON_API_KEY"
}
}
}
}
Run the Docker container:
docker run -p 8080:8080 \
-e PLANTON_MCP_TRANSPORT="http" \
-e PLANTON_MCP_HTTP_AUTH_ENABLED="true" \
ghcr.io/plantoncloud/mcp-server-planton:latest
Note: The API key is provided by each user in the Authorization header, not in the Docker environment. This enables proper multi-user support with per-user permissions.
Local Binary (STDIO Mode)
{
"mcpServers": {
"planton-cloud": {
"command": "mcp-server-planton",
"env": {
"PLANTON_API_KEY": "YOUR_PLANTON_API_KEY",
"PLANTON_CLOUD_ENVIRONMENT": "live"
}
}
}
}
Install the binary:
# macOS (ARM64)
curl -L https://github.com/plantoncloud/mcp-server-planton/releases/latest/download/mcp-server-planton_Darwin_arm64.tar.gz | tar xz
sudo mv mcp-server-planton /usr/local/bin/
# macOS (Intel)
curl -L https://github.com/plantoncloud/mcp-server-planton/releases/latest/download/mcp-server-planton_Darwin_x86_64.tar.gz | tar xz
sudo mv mcp-server-planton /usr/local/bin/
# Linux (AMD64)
curl -L https://github.com/plantoncloud/mcp-server-planton/releases/latest/download/mcp-server-planton_Linux_x86_64.tar.gz | tar xz
sudo mv mcp-server-planton /usr/local/bin/
Integration with Claude Desktop
Add to your Claude Desktop MCP settings:
{
"mcpServers": {
"planton-cloud": {
"command": "mcp-server-planton",
"env": {
"PLANTON_API_KEY": "YOUR_PLANTON_API_KEY",
"PLANTON_CLOUD_ENVIRONMENT": "live"
}
}
}
}
Integration with LangGraph
Add to your langgraph.json:
{
"mcp_servers": {
"planton-cloud": {
"command": "mcp-server-planton",
"env": {
"PLANTON_API_KEY": "${PLANTON_API_KEY}",
"PLANTON_CLOUD_ENVIRONMENT": "live"
}
}
}
}
Available Tools
The MCP server provides tools for querying and managing Planton Cloud resources:
Cloud Resources
list_cloud_resource_kinds- List all available cloud resource typesget_cloud_resource_schema- Get schema/spec for a resource typesearch_cloud_resources- Search and filter cloud resourceslookup_cloud_resource_by_name- Find resource by exact nameget_cloud_resource_by_id- Get complete resource details by IDcreate_cloud_resource- Create new cloud resourcesupdate_cloud_resource- Update existing resourcesdelete_cloud_resource- Delete cloud resources
Service Hub
list_services_for_org- List all services in an organizationget_service_by_id- Get service details by IDget_service_by_org_by_slug- Get service by organization and namelist_service_branches- List Git branches for a service's repositoryget_tekton_pipeline- Get complete Tekton pipeline definition with YAML by ID or org/nameget_pipeline_by_id- Get pipeline execution details by pipeline IDget_latest_pipeline_by_service_id- Get most recent pipeline execution for a serviceget_pipeline_build_logs- Stream and retrieve build logs for a pipeline
Connect (Credentials)
get_github_credential_for_service- Get GitHub credential for a serviceget_github_credential_by_org_by_slug- Get GitHub credential by org and namelist_github_repositories- List repositories accessible via a credential
Environments & Organizations
list_environments_for_org- List environments in an organizationlist_organizations- List organizations you're a member of
All tools respect your user permissions - you can only access resources you have permission to view or manage.
For detailed Service Hub tool documentation, see .
Configuration
Essential Environment Variables
| Variable | Default | Description |
|---|---|---|
PLANTON_API_KEY | (required) | Your API key from Planton Cloud console |
PLANTON_CLOUD_ENVIRONMENT | live | Target environment: live, test, or local |
PLANTON_MCP_TRANSPORT | stdio | Transport mode: stdio, http, or both |
PLANTON_MCP_HTTP_PORT | 8080 | HTTP server port (when using HTTP transport) |
PLANTON_MCP_HTTP_AUTH_ENABLED | true | Enable bearer token authentication for HTTP |
Note: When HTTP authentication is enabled, your PLANTON_API_KEY is used as the bearer token.
For complete configuration options, see .
Security
This MCP server uses user API keys for all operations, ensuring that:
- Per-User Authentication: Each user provides their own API key via Authorization header (HTTP mode) or environment variable (STDIO mode)
- Fine-Grained Authorization: All queries respect each user's actual permissions
- No API Key Persistence: Keys are held in memory only during request execution
- Complete Audit Trail: Every API call is validated and logged with the user's identity
- Multi-User Support: HTTP transport supports multiple users with different permissions accessing the same server instance
HTTP Transport Security Model
When using HTTP transport, each user's API key is:
- Provided in the
Authorization: Bearer YOUR_API_KEYheader - Extracted and validated by the MCP server
- Passed to Planton Cloud APIs for Fine-Grained Authorization
- Used only for that specific request (not stored)
This architecture ensures true multi-tenant security where users can only access resources they have permission to view or manage.
Documentation
- - Running the server locally and HTTP deployment
- - Complete environment variable reference
- - Contributing and local development setup
- - Detailed installation instructions
Support
- Issues: GitHub Issues
- Discussions: GitHub Discussions
- Documentation: Planton Cloud Docs
License
Apache-2.0 - see for details.
Built with ❤️ by Planton Cloud