MCP server exposing Backplane platform tools for AI agents
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"backplane-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Backplane MCP Server An [MCP](https://modelcontextprotocol.io) server that exposes the [Backplane](https://github.com/Valaris-Studio/backplane) platform to AI agents. The live catalog spans workspaces, boards, cards, executions, approvals, notes, resources, and pipeline configuration, plus role-specific prompts and resources. Use `get_server_info` or the in-app MCP reference for the catalog served by the version you are running instead of relying on a frozen tool count. Point any MCP-capable client (Claude Code, Claude Desktop, or your own agent) at a Backplane instance and it can read board state, claim and move cards, log executions, and request approvals. ## Install ```bash uvx backplane-mcp ``` Or from source: ```bash uvx --from "git+https://github.com/Valaris-Studio/backplane.git#subdirectory=mcp-server" backplane-mcp ``` ## Configure Add to your MCP client's config (e.g. `~/.claude.json` or `claude_desktop_config.json`): ```json { "mcpServers": { "valaris": { "command": "uvx", "args": ["backplane-mcp"], "env": { "VALARIS_API_URL": "https://your-backplane-host", "VALARIS_API_KEY": "vlr_..." } } } } ``` | Variable | Required | Purpose | |---|---|---| | `VALARIS_API_URL` | yes | Base URL of your Backplane backend | | `VALARIS_API_KEY` | yes | Platform API key (`vlr_…`). Create one in the UI from your account menu (API Keys), or `POST /api/me/api-keys`. | | `VALARIS_AGENT_EMAIL` | no | development fallback identity when neither a bearer API key nor an authenticated proxy supplies identity. It is ignored when `VALARIS_API_KEY` is used. | | `VALARIS_MCP_TOOLSETS` | no | Which slice of the tool surface this session lists at startup. Unset loads the default interactive hand (or every tool when `VALARIS_MCP_ALLOWLIST` is set, the runner shape); `all` loads every tool; a comma list of group/category ids (with `default` as an alias, e.g. `default,autonomous-operations`) composes a custom hand. An unknown id…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.