extracto-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXTRACTO_API_KEY | Yes | Your key from app.getextracto.dev/keys. | |
| EXTRACTO_BASE_URL | No | Override the API host (defaults to https://app.getextracto.dev). | |
| EXTRACTO_TIMEOUT_MS | No | Per-request timeout in ms (default 90000). |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extractA | Extract structured data from a public web page and return it as validated, typed JSON. Extracto renders the page (JavaScript included), runs a schema-constrained extraction, and returns ONLY fields that match the schema. Missing data comes back as null rather than a hallucinated guess. Best for a single known URL. This call is synchronous (up to ~90s); for heavy or anti-bot pages prefer |
| extract_asyncA | Submit an asynchronous extraction job for a heavy, slow, or anti-bot-protected page. Returns a job id immediately; poll it with |
| get_jobA | Fetch the current status and (once complete) the result of an async extraction job created with |
| list_jobsA | List your recent async extraction jobs, newest first. |
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 4 tools
Each tool serves a distinct purpose: synchronous extraction, async submission, polling, and listing. No overlap or ambiguity.
Names are mostly lowercase and descriptive, but 'extract_async' breaks the verb_noun pattern seen in 'get_job' and 'list_jobs'. Minor inconsistency.
With 4 tools covering sync/async extraction and job management, the count is well-scoped for a focused extraction service.
Covers core extraction workflows, but lacks a cancel job or delete job tool. Minor gap for a complete surface.