MCP server

Boardwalk exposes a Model Context Protocol server, a peer to the REST API over the same auth and the same org scoping. Point any MCP-aware agent at it and the agent can manage and trigger your workflows directly, no shell required. (If you just want your coding agent to drive the CLI, the plugins are the simpler path.)

Connect

The server is a streamable-HTTP MCP endpoint at https://api.boardwalk.sh/mcp/v1, authenticated with a bearer API key. Configure it in your client the same way you add any remote MCP server:

{
  "mcpServers": {
    "boardwalk": {
      "url": "https://api.boardwalk.sh/mcp/v1",
      "headers": { "Authorization": "Bearer bwk_your_key_here" }
    }
  }
}

Tools

The server registers these tools:

Tool	What it does
`list_workflows`	List the workflows in your org.
`get_workflow`	Fetch one workflow, including its bundled files.
`create_workflow` / `update_workflow`	Deploy a single-file or multi-file program (update bumps the version).
`delete_workflow`	Soft-delete a workflow.
`trigger_now`	Fire a one-off run, with optional `args` as the trigger input.
`list_runs` / `get_run`	List recent runs (filter by status) or read one run.
`list_artifacts` / `get_artifact_download_url`	List a run's artifacts and mint a signed download URL.
`list_secret_names`	List secret names and metadata (never values).
`list_inference_providers` / `list_tools`	List configured providers and the built-in tools available to `agent()`.
`get_balance`	Read the org's credit balance and active grants.
`list_audit` / `revoke_api_key`	Read the audit log; revoke a key (the one mutating credential op allowed).

What it won't do

Credential-creating operations, writing a secret, minting an API key, are intentionally not available over MCP (or any API key). They require a logged-in session in the dashboard, so a token can never escalate its own reach. See Authentication for the same boundary on REST.