mindee
Server Details
Turn PDFs and images into typed fields — invoices, receipts, IDs and custom models — via Mindee OCR.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
4 toolsmindee_extract_documentExtract data from a documentInspect
Submit a document (PDF or image) to a Mindee extraction model and return the structured fields. Provide EITHER document_url (a public URL) OR file_base64 (+ filename). This enqueues an inference and polls until it completes (up to ~30s); if it is still processing it returns a job_id you can poll with mindee_get_job then read with mindee_get_inference. NOTE: consumes Mindee API credits (paid, billed per page). V2 API: POST /v2/inferences/enqueue.
| Name | Required | Description | Default |
|---|---|---|---|
| rag | No | Enable Retrieval-Augmented Generation for the model, if configured. | |
| alias | No | Your own reference tag echoed back in the job/result. | |
| polygon | No | Return bounding-box polygons for fields. | |
| filename | No | Filename for file_base64 uploads, e.g. 'invoice.pdf'. | |
| model_id | Yes | Extraction model id (from mindee_list_models). | |
| raw_text | No | Also return the full OCR raw text of the document. | |
| confidence | No | Return per-field confidence levels (Certain/High/Medium/Low). | |
| file_base64 | No | Base64-encoded document bytes. Use this OR document_url; set `filename` too. | |
| webhook_ids | No | Webhook ids to notify on completion (async flows). | |
| document_url | No | Public URL of the document to process. Use this OR file_base64. |
mindee_get_inferenceGet extraction resultRead-onlyInspect
Fetch the structured result of a completed inference by id, returned as a compact map of extracted fields (plus raw_text if it was requested). V2 API: GET /v2/inferences/{inference_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| raw | No | Return the full unshaped API response instead of the compact fields map. Default false. | |
| inference_id | Yes | Inference id (from a Processed job's result_url, or from mindee_extract_document). |
mindee_get_jobGet job statusRead-onlyInspect
Check the processing status of an enqueued document by job id. Status is Waiting | Processing | Processed | Failed. When Processed, the response carries a result_url; pass that inference id to mindee_get_inference. V2 API: GET /v2/jobs/{job_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes | Job id returned by mindee_extract_document (when it times out) or an enqueue call. |
mindee_list_modelsList extraction modelsRead-onlyInspect
List the document-extraction models available to your Mindee account (id, name, type). Use a model's id as the model_id for mindee_extract_document. V2 API: GET /v2/search/models.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Optional case-insensitive name filter, e.g. 'invoice'. | |
| model_type | No | Optional model type filter. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!