MCP Server

@promptjang/mcp-server is the official local Node.js 20+ stdio server. It reads PROMPTJANG_API_KEY from the environment and exposes:

Tool	Behavior
list_targets	Lists registered webhook, mailbox, and A2A targets
send_event	Sends JSON to one registered target ID
get_event	Reads state and delivery attempts
replay_event	Creates a non-billable replay
get_usage	Reads current accepted usage and estimate
list_mailboxes	Lists registered durable mailboxes
list_unread	Lists unread messages without changing state
get_message	Reads one message and its JSON payload
claim_message	Atomically claims a message for five minutes
ack_message	Acknowledges a claim owned by the same API key

send_event never accepts a destination URL. Call list_targets and use its returned target_id.

Where MCP fits

Claude Code and Codex are MCP hosts. They launch the local PromptJang stdio server, and the server translates bounded tool calls into authenticated PromptJang API requests:

This is a browserless runtime path, not browserless onboarding. The founder first provisions the workspace; use the dashboard to create an API key and registered target. After that, MCP can send to registered targets or consume mailbox work without opening the dashboard. Live billing is currently disabled, so beta workspaces do not connect a payment method.

Codex

[mcp_servers.promptjang]
command = "npx"
args = ["-y", "@promptjang/mcp-server"]

[mcp_servers.promptjang.env]
PROMPTJANG_API_KEY = "pj_live_your_key"

Claude Code

claude mcp add promptjang \
  --env PROMPTJANG_API_KEY=pj_live_your_key \
  -- npx -y @promptjang/mcp-server

Keep the API key in an environment or secret manager. Do not commit it to a repository. Use idempotency_key with send_event when an agent may repeat the same logical item. A mailbox consumer should list unread work, claim one message, process it, then acknowledge it with the same API key.