dev.getpepprPublished by getpeppr.devOfficial publisherv1.0.3Updated Nov 7, 2026
Peppol e-invoicing: look up participants, validate invoices, and send sandbox test invoices.
Sandbox-only Peppol e-invoicing helper: plans integrations, searches docs, validates invoices, looks up participants and sends test invoices.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/dev.getpeppr%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"getpeppr": {
"type": "http",
"url": "https://api.getpeppr.dev/mcp"
}
}
}A hosted Model Context Protocol server for Peppol e-invoicing, run by getpeppr.
Your assistant can plan a getpeppr integration, search the getpeppr documentation, check a test invoice against the Peppol rules and look up a participant on the Peppol network. With a free getpeppr sandbox account, it can also send test invoices and follow their status.
This repository holds no source code. The server is hosted and operated by getpeppr (Zero Loop Labs Ltd, UK). This repository describes it for MCP registries and directories. Nothing to install: you add an address to your assistant.
Full documentation: https://getpeppr.dev/docs/mcp/
Sandbox only. The server never sends a real invoice and never acts in production. Test invoices go to the sandbox test receiver
9925:BE0314595348, and a production key (sk_live_…) is refused: keep it out of your assistant's configuration. The participant lookup, on the other hand, reads the live Peppol network.
Registry name: dev.getpeppr/mcp · transport: streamable HTTP.
Add to .vscode/mcp.json in your workspace, or to your user mcp.json:
Or from a terminal:
VS Code asks you to sign in to getpeppr when it connects.
When you first call an account tool, run /mcp in Claude Code and sign in to getpeppr.
Run the login before using the account tools.
Both connect through https://api.getpeppr.dev/mcp/auth. getpeppr is also listed in Claude's connector directory. See the documentation for the one-click Cursor install.
Signing in uses your getpeppr account; there is no API key to copy. You choose the organisation the assistant acts for. You can also pass a sandbox API key (sk_sandbox_…) as a bearer token instead of signing in.
No account yet? Create a free sandbox account.
plan_integration gives the steps and code for your case; search_docs finds the pages to read.validate_invoice and lookup_participant work without an account.send_test_invoice sends to the sandbox test receiver. Platform accounts first call create_test_customer, then send as that customer.get_document_status follows the document until it is delivered or failed.Going live (an sk_live_ key, real receivers, webhooks) happens in the getpeppr console and in your own code, never through this server.
Public tools are rate limited per network address, and account tools per account. getpeppr can turn the MCP tools off without notice to protect the service; they then answer mcp.temporarily_disabled, and the API itself is not affected. Details: Limits.
Source: README.md at commit 48268d9
Plan a getpeppr integration
Returns 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.
moderequiredcountriesrequiredSearch the getpeppr documentation
Searches the prose of the public getpeppr documentation and returns up to 5 matching pages, each with its url and a short excerpt. Excerpts carry no code: open the returned url, or call plan_integration, for code.
queryrequiredValidate an invoice
Validates a Peppol BIS Billing 3.0 UBL document against the Peppol rules, or a getpeppr invoice JSON against the SDK rules, and explains each violation. It does not check whether the invoice can be sent. Send sample or test invoices only, never a real invoice or real people's data.
xmlformatrequiredinvoiceLook up a Peppol participant
Says whether a Peppol identifier (scheme:identifier) is registered to receive documents on the production Peppol network, and which ones. A sandbox test customer is never on it, and send_test_invoice only targets the test receiver 9925:BE0314595348 whatever this answers.
peppolIdrequiredCreate a sandbox test customer
Platform accounts only: creates a test customer (sub-tenant legal entity) in the getpeppr sandbox and returns its registration state. Up to 10 active test customers per account; identifier rules per country: https://getpeppr.dev/docs/platform/legal-entities/. Calling it again with the same arguments returns the same test customer with its current status, never a second one. Pass the returned legalEntity.id as sender.legalEntityId to send_test_invoice once its status allows sending. Requires the admin role and signing in to getpeppr.
addressrequiredcountryrequiredexternalIdrequiredidentifiercompanyNamerequiredidentifiersSend a sandbox test invoice
Sends an invoice in the getpeppr sandbox to the Belgian test receiver 9925:BE0314595348, for your own company or for one of your test customers. Never sends a real invoice. Lines without tax fields get your account's sandbox tax profile. While your sandbox tax profile is unchanged, calling it again with the same arguments returns the same document, never a second one. Returns a documentId to pass to get_document_status. Requires signing in to getpeppr.
senderinvoicerequiredGet a document's status
Returns the status and lifecycle events of a sandbox document sent from your getpeppr account; call it with the documentId send_test_invoice returned. submitted: getpeppr accepted it. delivered: the test receiver's access point received it, the goal of a sandbox test. failed: final, with a failureCategory. In application code, subscribe to webhooks instead of polling. Requires signing in to getpeppr.
documentIdrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a license in the repository or the registry entry.
{ "servers": { "getpeppr": { "type": "http", "url": "https://api.getpeppr.dev/mcp/auth" } }}code --add-mcp '{"name":"getpeppr","type":"http","url":"https://api.getpeppr.dev/mcp/auth"}'claude mcp add --transport http getpeppr https://api.getpeppr.dev/mcpcodex mcp add getpeppr --url https://api.getpeppr.dev/mcpcodex mcp login getpeppr