mcpField
I
Infraveil Control Plane

Infraveil Control Plane

Local
infraveil.comSecurity
RepositoryVisit website

About Infraveil Control Plane

Govern your backend control plane from your AI agent — signed, human-approval-gated

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "infraveilhq-control-plane": {
      "command": "uvx",
      "args": [
        "infraveil-mcp"
      ],
      "env": {
        "INFRAVEIL_BASE_URL": "<INFRAVEIL_BASE_URL>",
        "INFRAVEIL_CLIENT_ID": "<INFRAVEIL_CLIENT_ID>",
        "INFRAVEIL_AGENT_ID": "<INFRAVEIL_AGENT_ID>",
        "INFRAVEIL_AGENT_TOKEN": "<INFRAVEIL_AGENT_TOKEN>",
        "INFRAVEIL_AGENT_FILE": "<INFRAVEIL_AGENT_FILE>",
        "INFRAVEIL_VERIFY_RESPONSES": "<INFRAVEIL_VERIFY_RESPONSES>"
      }
    }
  }
}
Run commanduvx infraveil-mcp
Environment variables to set
INFRAVEIL_BASE_URLControl-plane base URL, e.g. https://api.infraveil.com
INFRAVEIL_CLIENT_IDYour Infraveil client id (same one the agent uses)
INFRAVEIL_AGENT_IDThe agent id this MCP server speaks for
INFRAVEIL_AGENT_TOKENSecretThe agent's existing token; used to sign requests. Never minted here.
INFRAVEIL_AGENT_FILEAlternative to the four vars above: path to your rendered agent source; ids and token are read from it.
INFRAVEIL_VERIFY_RESPONSESVerify the control plane's response signatures (default on). Set 0 only for debugging.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiinfraveil-mcp0.1.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.