1. Conduid
  2. Cloud
  3. Pce MCP
MCP server · Cloud

Pce MCP

MCP server for interacting with Pextra CloudEnvironment®.

Unclaimed Apache-2.0 last commit 9 months ago cloud
56Fair

Scored 8 days ago · breakdown

About Pce MCP

Pce MCP is an MCP server published by PextraCloud in the Cloud category: mCP server for interacting with Pextra CloudEnvironment®.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/PextraCloud/pce-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Pce MCP

Powered by Claude · Grounded in docs

I know everything about Pce MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

3 checks have not been run yet.

Releases

0.7.10.7.1 · 31 Dec 2025Changelog 75cdae29a542cbffed84fa8c4e1e667aa93cb111 fix: use `float64` instead of `string` for `DatacenterList.Location` <a href="https://pextra.cloud/cloudenvironment"><img…
0.6.00.6.0 · 22 Oct 2025Changelog 7265ec038a09309c2422bffcf6a10c6a8eeb8ffb feat: support stdio transport <a href="https://pextra.cloud/cloudenvironment"><img src="https://github.com/PextraCloud/.github/blob/master/banner.png" alt="Private cloud management,…
0.5.00.5.0 · 21 Oct 2025Changelog 88b1a48382a472b37fa0f448c146d6c5bf42bd6b feat: add support for specifying custom http headers <a href="https://pextra.cloud/cloudenvironment"><img src="https://github.com/PextraCloud/.github/blob/master/banner.png" alt="Private…
0.4.00.4.0 · 19 Oct 2025Changelog 2dd06e9d93aca163b5322f8b97e1146cd6927c28 feat: add support for custom CA cert <a href="https://pextra.cloud/cloudenvironment"><img src="https://github.com/PextraCloud/.github/blob/master/banner.png" alt="Private cloud management,…
0.3.10.3.1 · 19 Oct 2025Changelog 4e688afc19f902df92aae0e8a1ff34b5397532d0 fix: correct `GetNodeHardwareByIdResponse` field names and types <a href="https://pextra.cloud/cloudenvironment"><img src="https://github.com/PextraCloud/.github/blob/master/banner.png"…

README

pce-mcp

A production-ready Model Context Protocol (MCP) server for Pextra CloudEnvironment®.

Manage your Pextra CloudEnvironment® resources using MCP-compatible clients and tools.

Install

  1. Download the latest release binary from the Releases page for your platform.

  2. Follow the Configuration and Usage sections below to run the server.

  3. Connect your MCP-compatible clients and tools to the server and begin prompting!

This produces the pce-mcp binary in the repository root when using go build.

Configuration

You can configure the server using flags or environment variables. Flags override environment variables.

Flags:

  • --base-url (required): Pextra CloudEnvironment® base URL (e.g., https://192.168.1.27:5007).
  • --sse-addr (default :2222): SSE server listen address; set to empty string to disable.
  • --http-addr (default :2223): HTTP server listen address; set to empty string to disable.
  • --disable-stdio (default false): Disable the stdio server.
  • --tls-ca-cert (default ""): Path to a custom CA certificate file for the PCE API client. If set, TLS verification will use this CA instead of the system CAs. Mutually exclusive with --tls-skip-verify.
  • --tls-skip-verify (default false): Disable TLS verification for the PCE API client. This exposes you to man-in-the-middle attacks and is not recommended for production use. Mutually exclusive with --tls-ca-cert.
  • --timeout (default 10): PCE API request timeout in seconds.
  • --headers (default ""): Custom HTTP headers to include in the PCE API client requests, formatted as a key=value pairs, can be specified multiple times. Example: --headers "Authorization=Basic xxx" --headers "X-Custom-Header=Value".

Environment variables (fallbacks if corresponding flag is not set):

  • BASE_URL
  • SSE_ADDR
  • HTTP_ADDR
  • DISABLE_STDIO (e.g., true/false)
  • TLS_CA_CERT (file path)
  • TLS_SKIP_VERIFY (e.g., true/false)
  • TIMEOUT (integer seconds)

Usage

Run the server:

./pce-mcp serve --base-url "https://localhost:5007"

Disable transports as needed:

# Disable SSE
./pce-mcp serve --base-url "https://localhost:5007" --sse-addr=

# Disable HTTP
./pce-mcp serve --base-url "https://localhost:5007" --http-addr=

# Disable stdio server
./pce-mcp serve --base-url "https://localhost:5007" --disable-stdio

# Disable two transports (only stdio server enabled)
./pce-mcp serve --base-url "https://localhost:5007" --sse-addr= --http-addr=

Use environment variables as fallbacks:

export BASE_URL="https://localhost:5007"
export SSE_ADDR=":3000"
export HTTP_ADDR=":3001"
export DISABLE_STDIO=true
export TLS_SKIP_VERIFY=true
export TIMEOUT=15
./pce-mcp serve

Development

Build:

go build ./...

Run:

go run ./... serve --base-url "https://localhost:5007"

Tests

Integration tests (Linux only, optional tools required; some tests may need root):

go test -v -tags=integration -cover ./...

Coverage report:

go test -v -tags=integration -coverprofile=coverage.out ./...
go tool cover -html=coverage.out

License

This repository is licensed under the Apache License 2.0.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Pce MCP

How do I install Pce MCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Pce MCP safe to use with an AI agent?

Its trust score is 56 out of 100 (fair). It passes 2 of the 3 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Pce MCP still maintained?

The last commit was 9 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.