scantobill-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCANTOBILL_API_KEY | Yes | Your ScanToBill API key. Required for authentication. Can also be passed via --api-key CLI flag, but in MCP config this environment variable is used. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_documentA | Extract structured data from an invoice, receipt, commercial register, VAT certificate, or other business document at a public URL. Returns JSON with all detected fields including vendor, customer, line items, totals, VAT, and currency. Each extraction consumes one unit from the authenticated user's plan quota. |
| list_extractionsA | List past extraction log entries for the authenticated user. Returns extraction metadata (ID, type, provider, date, status) sorted newest first. Use get_extraction for the full details of a specific entry. |
| get_extractionA | Get the metadata for a specific past extraction by its log ID. Returns the document type, OCR provider used, status, and timestamp. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: extracting a new document, listing past extractions, and fetching a specific extraction's metadata. No overlap or ambiguity exists.
All tool names follow the same verb_noun pattern with lowercase and underscores: get_extraction, extract_document, list_extractions. Consistent and predictable.
Three tools is slightly minimal but appropriate for a focused extraction service. Each tool serves a distinct need in the extraction workflow, though additional operations like delete or re-extract could be added.
The set covers the core lifecycle: create (extract_document), list (list_extractions), and get (get_extraction). Missing update/delete operations, but extractions are likely immutable, so this is acceptable. A tool to check quota would be a minor addition.