Set up Pneumatic with MCP

The Pneumatic MCP connects an AI assistant to your account so it can do the setup with you. Cursor, Claude, and any other client that speaks MCP can create templates, run workflows, complete tasks, subscribe webhooks, and configure AI providers and agents. The assistant acts as the user behind the API key you give it.

Create a key for the assistant

  1. Sign in to Pneumatic.
  2. Open Integrations in the left menu.
  3. Under Your API Keys, choose Create.
  4. Name the key so you can tell it apart later, for example MCP.
  5. Copy the key when Pneumatic shows it. The full key is visible only this once.

Revoke that key on the same screen when you want the assistant to stop. Anything still using the key stops with it.

Admins and account owners create and revoke keys. Guest users cannot call the API.

Add the server

The server address is https://mcp.pneumatic.app/mcp.

Send the key on every request:

Authorization: Bearer YOUR_API_KEY

Cursor

Create .cursor/mcp.json in the project, or add the same block in Cursor Settings under MCP.

{
  "mcpServers": {
    "pneumatic": {
      "url": "https://mcp.pneumatic.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Reload the window, then ask the assistant to list your templates. A list of templates from your account means the connection is live.

Claude

Add a custom connector and paste https://mcp.pneumatic.app/mcp. If the connector has a header field, use the same Authorization value. If it opens a browser page, connect that page with this API key.

When the page says the client is unknown, remove the connector and add it again.

Any other client

Point it at the same URL. A client that implements MCP sign-in registers itself and opens the browser. A client that only takes a token sends the API key as Authorization: Bearer YOUR_API_KEY.

What to ask it to set up

The key’s permissions are the assistant’s permissions. An admin key can change account-level AI settings. A member key can work with the templates, workflows, and tasks that member can already open.

Ask for one concrete result, then open it in Pneumatic and confirm it before you rely on it.

  • An AI provider: a name, the provider base URL, and that provider’s own API key.
  • An AI agent: a name, the provider, the model, and the system prompt.
  • A workflow template: describe the process, then review the steps, performers, and fields.
  • A workflow run: the template and the kickoff values.
  • A webhook: the events to send and the URL that should receive them.

The field-level reference is the API documentation.

When the client cannot connect

  • The request has no Authorization header. The server answers that the header is missing.
  • The key is wrong, copied with a space, or already revoked. The server answers that the Pneumatic API key is invalid or revoked. Create a new key. The old one cannot be displayed again.
  • The header is missing the Bearer prefix.
  • The browser page says the client is unknown. Remove the connector in the MCP client and add it again.