Skavio Processing MCP
Skavio exposes its Processing API to AI agents as a standard, paid Model Context Protocol server. A model or agent can upload a document or media file, get a price, run the work on Skavio's real processing pipeline, download the signed result, and settle it against prepaid Skavio credits.
- Endpoint (Streamable HTTP):
https://www.skavio.eu/processing/mcp - Health:
https://www.skavio.eu/processing/health - Protocol: MCP
2025-06-18, official Streamable HTTP transport - Auth:
Authorization: Bearer <MCP credential>, or interactive
OAuth 2.0 + PKCE for hosted clients (see OAuth and authentication)
- Billing: prepaid USDC credits in your existing Skavio company wallet
This is not a mock, a wrapper or a second wallet. It calls the same Processing API and the same credit wallet that power the Skavio website, and it sells the same operations at the same verified cost-plus prices.
What you can do
| Task | Operation id | Unit |
|---|---|---|
| PDF to text | pdf_to_text | page |
| Extract a page range from a PDF | pdf_split | source document |
| Merge PDFs | pdf_merge | source document |
| OCR a scan or image | document_ocr | page |
| Extract invoice / receipt fields | invoice_extract | document |
| Transcribe audio or video | audio_transcribe | started minute |
Current prices are in pricing and as machine-readable data in pricing.json.
Start here
- Getting started — create a company, connect a client, run your first paid job.
- Authentication — create, rotate and revoke an MCP credential.
- OAuth 2.0 sign-in — interactive PKCE sign-in for Smithery and other hosted clients.
- Tools and workflow — every tool, argument and the exact paid sequence.
- Client configuration — copy-paste config for common MCP clients.
- Pricing — the price list and how credits work.
- Troubleshooting — error codes and how to recover.
- Privacy and security — data handling, isolation and limits.
- Integration examples — runnable Python and TypeScript clients.
Ground rules
- Paid work is only admitted when the price is proven to stay inside Skavio's
enforced 25–40% gross margin band from verified, dated cost evidence. If that evidence is missing or stale, paid admission fails closed with a clear error.
- Every MCP credential maps to exactly one verified company. A credential can
never read, spend or download for another company.
- Your MCP credential is independent of your Processing API key. Skavio never
forwards your MCP token upstream and never exposes the upstream key to you.
- An agent can never move funds, top up a wallet, charge a card or start a
checkout. Credits are purchased only by a company administrator in the Skavio dashboard.