Integration

PrintNode integration

PrintNode prints to any printer attached to a computer running the PrintNode Client. Read the account, list printers with their capabilities (trays, paper sizes, copies, duplex), send a PDF or RAW document to a printer by URL or base64, follow print job history and state (new, sent_to_client, done, error, expired), cancel jobs not yet delivered, and manage webhooks for computer and print job state messages. Computer removal, scales, child accounts, API key and tag management and client downloads are not exposed. Authentication is HTTP Basic with the API key as the username and an empty password; the API allows 10 requests per second per account.

Connect PrintNode How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in PrintNode.Built from the 10 PrintNode tools below, on the connection you add once.

What you can do with PrintNode

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Print job, 3 operations

cancel_printjobsCancel printjobsDELETECancels the print jobs in the set that have not yet reached the PrintNode Client; delivered or finished jobs cannot be cancelled. Returns the ids actually cancelled.
create_printjobCreate printjobPOSTSends a document to a printer; it prints for real, now or when its computer reconnects. The job id is not returned here: find the job by its title at the top of list_printjobs, then follow it with list_printjob_states.
list_printjobsList printjobsGETLists the account's print job history, most recent first (up to 100 per call): id, printer, title, content type, source, expiry and state.

Webhook, 3 operations

create_webhookCreate webhookPOSTRegisters a URL that PrintNode calls on computer state or print job state messages. Returns the account's webhooks, the new one included with its webhookId.
delete_webhookDelete webhookDELETEDeletes a webhook. Returns the account's remaining webhooks.
list_webhooksList webhooksGETLists the account's webhooks with id, target URL, message types and delivery counts.

Printer, 2 operations

get_printersGet printersGETReturns the printers whose ids are in the set, with computer, state and capabilities. Read capabilities before setting create_printjob options.
list_printersList printersGETLists every printer on the account with its computer, name, state and capabilities (trays, papers, copies, duplex). Use an id as printerId in create_printjob.

Account, 1 operation

get_accountGet accountGETReturns the authenticated account: id, name, email, credits, number of computers, total prints, state and permissions.

Print job state, 1 operation

list_printjob_statesList printjob statesGETReturns the state history of each print job in the set: new, sent_to_client, then done, error or expired (stable states), with message and timestamps.

Use PrintNode from Claude Code, Cursor or Codex

Connect PrintNode in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its PrintNode operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect PrintNode

Create your workspace
Sign up free. Nothing to install.
Connect PrintNode once
Add your PrintNode connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.