Landscape 查询 MCP 服务

landscape-mcp

An MCP server for Landscape, written in Go with the official Go MCP SDK. It lets AI agents query Landscape accounts, licenses, and registered computers.

Tools and prompts

Configuration

The server reads its configuration from the environment:

The server starts without credentials so clients can list its tools; tool calls fail with an error naming the missing variables until they are set.

Building

Requires Go 1.26+:

go build -o landscape-mcp ./cmd/landscape-mcp

Running

Two transports are available, selected with -transport (env LANDSCAPE_MCP_TRANSPORT):

• stdio (default): for local agent clients launching the binary directly.
• http: streamable HTTP at /mcp on -addr (env LANDSCAPE_MCP_HTTP_ADDR, default :8080), with a /healthz endpoint for load balancer health checks. Used by the charm and rock.

./landscape-mcp -transport http -addr :8080

To serve HTTPS, pass -tls-cert and -tls-key (env LANDSCAPE_MCP_TLS_CERT and LANDSCAPE_MCP_TLS_KEY). Both must be set together; with neither, the server serves plain HTTP. The charm sets them when integrated with a TLS certificates provider.

VSCode

Add an entry to mcp.json:

{
	"servers": {
		"landscape-mcp": {
			"type": "stdio",
			"command": "/path/to/landscape-mcp",
			"env": {
				"LANDSCAPE_API_URI": "${input:landscape-api-uri}",
				"LANDSCAPE_API_KEY": "${input:landscape-api-access-key}",
				"LANDSCAPE_API_SECRET": "${input:landscape-api-secret-key}"
			}
		}
	},
	"inputs": [
		{
			"id": "landscape-api-uri",
			"type": "promptString",
			"description": "API URI for Landscape"
		},
		{
			"id": "landscape-api-access-key",
			"type": "promptString",
			"description": "API Access Key for Landscape"
		},
		{
			"id": "landscape-api-secret-key",
			"type": "promptString",
			"description": "API Secret Key for Landscape",
			"password": true
		}
	]
}

Charmed deployment

The charm/ directory contains a Kubernetes charm that deploys the server (HTTP transport) and can publish it behind the same HAProxy as the landscape-server charm via an haproxy-route relation - clients can then connect directly to a local binary or to the charmed deployment. See charm/README.md.

Pushes to main publish the image to ghcr.io/jansdhillon/landscape-mcp and the charm to Charmhub latest/edge; see Continuous publishing.

Development

go build ./...
go vet ./...
go test ./...

API client

v2 API calls (e.g. get_computers) go through the generated landscape-go-api-client, which is regenerated from the landscape-openapi-spec. Legacy API actions (GetAccounts) use the shim in internal/landscape/ - the legacy API is not OpenAPI-specifiable and stays out of the spec permanently.

The spec grows demand-driven: endpoints are added only when a consumer (this MCP, the Terraform provider) needs them. When Canonical publishes an official spec, point the client repo at it, regenerate, and the MCP follows.