Turn any URL plus a schema into validated, typed JSON via the Extracto API.
If you already use Extracto, the extracto mcp server is the piece that lets your assistant work with it directly. Turn any URL plus a schema into validated, typed JSON via the Extracto API.
You need an Extracto API key. Get one at app.getextracto.dev/keys.
extracto-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
extract — Synchronous extraction from a single URL (up to ~90s). Returns { data, meta }extract_async — Submit an async job for heavy or anti-bot pages. Returns a job id immediatelyget_job — Poll an async job for status and resultlist_jobs — List your recent async jobsCursor — Add to ~/.cursor/mcp.json (or the project .cursor/mcp.json) with the same blockConfiguration is passed through the environment: EXTRACTO_API_KEY, EXTRACTO_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Extracto's toolset — extract, extract_async, get_job and 2 more — is a fair guide to whether it matches your workflow. It is maintained by massanaRoger; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| extract | Synchronous extraction from a single URL (up to ~90s). Returns { data, meta }. |
| extract_async | Submit an async job for heavy or anti-bot pages. Returns a job id immediately. |
| get_job | Poll an async job for status and result. |
| list_jobs | List your recent async jobs. |
| Cursor | Add to ~/.cursor/mcp.json (or the project .cursor/mcp.json) with the same block. |
{
"mcpServers": {
"extracto": {
"command": "npx",
"args": ["-y", "extracto-mcp"],
"env": { "EXTRACTO_API_KEY": "exa_live_your_key_here" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| EXTRACTO_API_KEY | Credential the server authenticates with. | Yes |
| EXTRACTO_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.