Allows to automatically submit PDF documents (e.g., medical invoices) from Paperless-NGX to the Debeka health insurance portal.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Debeka MCP Server Submit claim with servicenummer 123456789 and upload rechnung.pdf"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ein MCP (Model Context Protocol) Server zur Automatisierung von Debeka Leistungsaufträgen mit Playwright.
🌐 Automatisches Öffnen der Debeka Leistungsauftrag-Seite
📝 Ausfüllen von Servicenummer und Geburtsdatum
📎 Upload von PDF-Dokumenten (Arztrechnungen)
📸 Screenshots zur Überprüfung
✅ Formular absenden
Related MCP server: form-auto-mcp
Node.js 18 oder höher
npm
cd debeka-mcp-server
npm install
npm run buildDies installiert auch automatisch den Chromium-Browser für Playwright.
Füge folgende Konfiguration zu deiner claude_desktop_config.json hinzu:
Pfad: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"debeka": {
"command": "node",
"args": ["/pfad/zu/debeka-mcp-server/dist/index.js"]
}
}
}Pfad: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"debeka": {
"command": "node",
"args": ["C:\\pfad\\zu\\debeka-mcp-server\\dist\\index.js"]
}
}
}Nach der Konfiguration stehen folgende Tools zur Verfügung:
Öffnet die Debeka Leistungsauftrag-Seite im Browser.
debeka_open_page(headless=false) # Mit sichtbarem Browser
debeka_open_page(headless=true) # Ohne UI (Hintergrund)Füllt Servicenummer und Geburtsdatum aus.
debeka_fill_credentials(
servicenummer="123456789",
geburtsdatum="15.03.1985"
)Lädt PDF-Dokumente hoch.
debeka_upload_documents(
file_paths=["/pfad/zu/rechnung1.pdf", "/pfad/zu/rechnung2.pdf"]
)Macht einen Screenshot der aktuellen Seite.
debeka_screenshot(output_path="/pfad/zum/screenshot.png")Sendet das Formular ab.
debeka_submit()Schließt den Browser.
debeka_close()Zeigt Informationen über die Seitenstruktur (für Debugging).
Seite öffnen: debeka_open_page(headless=false)
Credentials eingeben: debeka_fill_credentials(servicenummer="...", geburtsdatum="...")
Dokumente hochladen: debeka_upload_documents(file_paths=[...])
Überprüfen: debeka_screenshot()
Absenden: debeka_submit()
Browser schließen: debeka_close()
Der Server kann zusammen mit Paperless-NGX verwendet werden:
Arztrechnungen aus Paperless exportieren
Mit diesem MCP-Server automatisch bei Debeka einreichen
Stelle sicher, dass Chromium installiert ist: npx playwright install chromium
Die Debeka-Website könnte ihre Struktur geändert haben
Nutze debeka_get_page_info um die aktuelle Struktur zu sehen
Nutze debeka_screenshot um den aktuellen Zustand zu überprüfen
Die Debeka-Website ist manchmal in Wartung
Versuche es später erneut
MIT
Closes the browser instance.
Call this when you're done with the Debeka form to free up resources.
Returns: Confirmation that browser was closed.
Inputs: no named parameters.
Fills in all personal data fields on the Debeka Leistungsauftrag form.
This tool enters your credentials into the open Debeka form. Make sure to call debeka_open_page first.
Args:
servicenummer (string): Your Debeka Servicenummer (e.g., '2267092.1')
geburtsdatum (string): Your birth date (DD.MM.YYYY or YYYY-MM-DD format)
vorname (string): First name of the insured person
nachname (string): Last name of the insured person
telefon (string, optional): Phone number for contact
Returns: Success message if credentials were entered, or error details.
Example: servicenummer="2267092.1", geburtsdatum="25.06.1974", vorname="Jyn", nachname="Schultze-Melling", telefon="+4917672825190"
Inputs: vorname (required), nachname (required), geburtsdatum (required), servicenummer (required), +1 more.
Gets information about the current page structure.
Useful for debugging if the form structure has changed.
Returns: Page URL, title, and list of form elements found.
Inputs: no named parameters.
Opens the Debeka Leistungsauftrag form page in a browser.
This tool launches a Chromium browser and navigates to the Debeka form for submitting medical invoices.
Args:
headless (boolean): If true, runs browser without UI. Default: false (shows browser window)
Returns: Success message with page title, or error if page couldn't be loaded.
Example:
debeka_open_page with headless=false to see the browser
debeka_open_page with headless=true for automated processing
Inputs: headless.
Takes a screenshot of the current browser page.
Useful for verifying the current state of the form before submitting.
Args:
output_path (string, optional): Path to save the screenshot. If not provided, returns base64.
Returns: Screenshot saved confirmation or base64 encoded image data.
Inputs: output_path.
Submits the Debeka Leistungsauftrag form.
WARNING: This will actually submit the form! Make sure all data is correct first.
Returns: Success message if form was submitted, or error details.
Inputs: no named parameters.
Uploads PDF documents to the Debeka form.
This tool uploads one or more PDF files to the Debeka Leistungsauftrag form. Make sure to call debeka_open_page and debeka_fill_credentials first.
Args:
file_paths (string[]): Array of absolute file paths to PDF documents
Returns: Success message listing uploaded files, or error details.
Example: file_paths=["/path/to/invoice1.pdf", "/path/to/invoice2.pdf"]
Inputs: file_paths (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Each tool has a clearly distinct role in the form automation workflow: opening, filling, uploading, inspecting, screenshotting, submitting, and closing. There is no meaningful overlap that would cause an agent to select the wrong tool for a given step.
Tool names consistently use snake_case with a debeka_ prefix and mostly follow a verb_noun pattern like debeka_open_page and debeka_fill_credentials. Minor deviations like debeka_submit and debeka_close omit an explicit object, but the pattern remains predictable.
Seven tools is well-scoped for the server's stated purpose of automating a single form submission workflow. Each tool maps to a necessary step or useful utility, with no redundant or excessive additions.
The tool set covers the full lifecycle from opening the page, filling credentials, uploading documents, submitting, and closing the browser, plus debugging aids like screenshot and page info. Minor gaps exist around post-submission verification or waiting for confirmation, but agents can generally complete the core workflow without dead ends.
Playwright browser automation — navigate, click, fill forms, extract, screenshot — 17 agent tools.
AI-powered browser automation — navigate, click, fill forms, and extract data from any website.
Stealth web automation for AI agents. Login, signup, navigate, screenshot.
Stealth web automation for AI agents. Login, signup, navigate, screenshot.
