Developer Tools
getpeppr.dev
Provides developer tools for integrating Peppol e-invoicing, including integration planning, documentation search, invoice validation, participant lookup, and sandbox test customer creation.
ENDPOINT 1
https://api.getpeppr.dev/mcp
MCP server metadata
- Name
- getpeppr
- Version
- 1.0.0
getpeppr sends Peppol e-invoices from JSON. This MCP server works in the getpeppr sandbox only: it never sends a real invoice and never acts in production. Journey to a first delivered test invoice: 1. plan_integration (mode, countries) returns the steps and the code for the developer's case; search_docs finds documentation pages (open the returned url for the full text and code). 2. validate_invoice and lookup_participant need no account. Give validate_invoice sample or test invoices only, never a real invoice or real people's data. 3. The developer needs a free getpeppr account (https://console.getpeppr.dev/sign-up?source=mcp) and their own company registered at https://console.getpeppr.dev/onboarding?source=mcp. The account tools (send_test_invoice, get_document_status, create_test_customer) ask the user to sign in to getpeppr on first use; a sandbox API key (sk_sandbox_...) sent as the bearer also works. 4. send_test_invoice delivers only to the sandbox test receiver 9925:BE0314595348. When the invoice lines carry no tax fields, it applies the account's sandbox tax profile. Platform accounts first call create_test_customer, then pass sender.legalEntityId. 5. get_document_status with the returned documentId, until the status is delivered or failed. 6. Going live (an sk_live_ key, real receivers, webhooks) happens in the getpeppr console and in the developer's own code, never through this server: https://getpeppr.dev/docs/authentication/ Every tool result carries a code and a message. On an error, follow the message, and the next field when there is one.
Known tools 7
plan_integrationReturns the integration steps, code snippets and documentation links for adding Peppol to an application, for a single sender or for a platform that sends on behalf of its customers.
Inferred read-onlysearch_docsSearches the prose of the public getpeppr documentation and returns up to 5 matching pages, each with its url and a short excerpt.
Inferred read-onlylookup_participantSays whether a Peppol identifier (scheme:identifier) is registered to receive documents on the production Peppol network, and which ones.
Inferred read-onlycreate_test_customerPlatform accounts only: creates a test customer (sub-tenant legal entity) in the getpeppr sandbox and returns its registration state.
Inferred read-onlysend_test_invoiceSends an invoice in the getpeppr sandbox to the Belgian test receiver 9925:BE0314595348, for your own company or for one of your test customers.
Potential side effectsget_document_statusReturns the status and lifecycle events of a sandbox document sent from your getpeppr account; call it with the documentId send_test_invoice returned.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.getpeppr]
url = "https://api.getpeppr.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"getpeppr": {
"type": "http",
"url": "https://api.getpeppr.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: getpeppr
Remote MCP URL: https://api.getpeppr.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"getpeppr": {
"url": "https://api.getpeppr.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"getpeppr": {
"type": "http",
"url": "https://api.getpeppr.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "getpeppr",
"transport": "streamable-http",
"url": "https://api.getpeppr.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://api.getpeppr.dev/mcp/auth
Known tools 0
No tool metadata was available in the registry cache.
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.getpeppr-dev]
url = "https://api.getpeppr.dev/mcp/auth"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Code
.mcp.json
{
"mcpServers": {
"getpeppr-dev": {
"type": "http",
"url": "https://api.getpeppr.dev/mcp/auth",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Desktop
Settings → Connectors → Add custom connector
Name: getpeppr-dev
Remote MCP URL: https://api.getpeppr.dev/mcp/auth
Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"getpeppr-dev": {
"url": "https://api.getpeppr.dev/mcp/auth",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Visual Studio Code
.vscode/mcp.json
{
"servers": {
"getpeppr-dev": {
"type": "http",
"url": "https://api.getpeppr.dev/mcp/auth",
"headers": {
"Authorization": "Bearer ${input:mcp-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "mcp-token",
"description": "getpeppr-dev bearer token",
"password": true
}
]
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Generic MCP
Client-specific MCP configuration
{
"name": "getpeppr-dev",
"transport": "streamable-http",
"url": "https://api.getpeppr.dev/mcp/auth",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.