POP MCP Server
Live Remote Endpoint

POP MCP for document workflows and business integrations.

This endpoint exposes the POP Cloud API as a remote MCP server for Claude, OpenAI Responses API, n8n, MCP Inspector, and any client that speaks Streamable HTTP MCP.

Machine-readable summary

This section states the essential MCP connection facts in plain text so both developers and LLM-based agents can extract the integration contract quickly.

Protocol endpoint
https://mcp.popapi.io/mcp
Authentication
Authorization: Bearer <license_key> on every request.
Transport
Streamable HTTP MCP. POST requests must accept both application/json and text/event-stream.
Human and machine routes
/ is the landing page, /mcp is the MCP endpoint, and /health is the JSON health check.
First protocol test
Use JSON-RPC method tools/list to verify live endpoint connectivity and tool exposure.

How to connect

Point your MCP client to https://mcp.popapi.io/mcp and send your POP license key as a Bearer token. The server is stateless and multi-tenant: every request carries its own credential.

Claude remote MCP OpenAI Responses API n8n MCP Inspector Custom integrations
Find your POP license key

Open popapi.io and go to Account > API.

Keep the header on every request

The remote server does not read POP_API_KEY from its own environment. Authentication is per-request only.

Use /health for monitoring

The JSON health check is available separately so the root path can stay readable for humans.

Quick test

The first real protocol check is tools/list. It confirms request routing, auth handling, MCP negotiation, and tool exposure in one call.

curl -X POST https://mcp.popapi.io/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer your_license_key_here" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Open /health

Connection tester

Run a safe client-side MCP connectivity check directly from this page. The key is used only for the in-browser request and is never stored. Use this on a trusted machine only.

Idle Requests are sent to https://mcp.popapi.io/mcp with the exact MCP headers required by the live endpoint.
Awaiting input.

Primary tool groups

Invoice generation

pop_create_sdi_invoice, pop_create_peppol_invoice, pop_create_pdf_invoice, pop_create_ksef_invoice, pop_create_zugferd_invoice, pop_sync_zoho_document

Status and retrieval

pop_get_invoice_status, pop_get_peppol_document, pop_get_sdi_document

Advanced document operations

pop_verify_sdi_document, pop_preserve_document

Onboarding flow

OTP authentication

pop_onboarding_request_otp and pop_onboarding_verify_otp

Account setup inspection

pop_onboarding_get_status and pop_onboarding_get_account_setup

Configuration write path

pop_onboarding_save_account_setup with explicit environment selection.