API testen — pfx MCP

← Zurück

API Key nötig — kostenlos anfordern. Header: Authorization: Bearer DEIN_API_KEY (oder X-API-Key). Proffix: X-Proffix-Username (optional), X-Proffix-Password, X-Proffix-Url, X-Proffix-Port, X-Proffix-Database.

Demo Chatbot Client Setup

1. CURL-Flow

Endpoint: POST https://mcp.pfx.ch/api/server

initialize

curl -X POST https://mcp.pfx.ch/api/server \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer DEIN_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "capabilities": {},
      "clientInfo": {"name": "curl-test", "version": "1.0.0"}
    }
  }'

tools/list

curl -X POST https://mcp.pfx.ch/api/server \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer DEIN_API_KEY" \
  -H "X-Proffix-Username: YOUR_USERNAME" \
  -H "X-Proffix-Password: YOUR_PASSWORD" \
  -H "X-Proffix-Url: https://your-proffix.example" \
  -H "X-Proffix-Port: 11011" \
  -H "X-Proffix-Database: YOUR_DB" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

tools/call (Beispiel)

curl -X POST https://mcp.pfx.ch/api/server \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer DEIN_API_KEY" \
  -H "X-Proffix-Username: YOUR_USERNAME" \
  -H "X-Proffix-Password: YOUR_PASSWORD" \
  -H "X-Proffix-Url: https://your-proffix.example" \
  -H "X-Proffix-Port: 11011" \
  -H "X-Proffix-Database: YOUR_DB" \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "px_search_addresses",
      "arguments": { "ort": "Zuerich", "limit": 5 }
    }
  }'

Gleiche Bodies in PowerShell / JS / Python

JSON-RPC-Body und Header unverändert; nur HTTP-Client wechseln (Invoke-RestMethod, fetch, requests.post).

Optional kompakter Output: Argument "format": "toon" bei lesenden Tools.

2. MCP Inspector

npx @modelcontextprotocol/inspector
HTTP → https://mcp.pfx.ch/api/server
Custom Headers: Bearer-API-Key + X-Proffix-*
tools/list, dann tools/call

3. Antwortformat

{
  "jsonrpc": "2.0",
  "id": 3,
  "result": { "content": [{ "type": "text", "text": "…" }] }
}

{
  "jsonrpc": "2.0",
  "id": 3,
  "error": { "code": -32001, "message": "Unauthorized: …" }
}

4. Troubleshooting

Symptom	Typische Ursache
401 / Unauthorized	API Key fehlt oder ungültig
503 / Bridge / Proffix	Proffix REST hängt oder Credentials/URL falsch — Host prüfen, ggf. neu starten
Unbekannte `proffix_*`-Tools	Standard nur `px_*` — Header `X-Legacy-Mode: 1`
Timeout bei Reports	Schwerer `generieren`-Call; Body/Selektionen prüfen, Timeout erhöhen
Chatbot ohne LLM	Key in Einstellungen setzen oder Demo-Proxy (`?demo=1`)