Extract

dev.averraPublished by averra.devv0.1.5Updated Oct 25, 2026

URL-to-Markdown API for AI pipelines — clean markdown with metadata and caching.

VerifiedSTDIODesktop onlyWeb Search & Scraping Security & Monitoring

Server details

Identifier: dev.averra/extract
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to averra.dev. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/dev.averra%2Fextract.svg)](https://sourceweft.com/mcp/dev.averra%2Fextract?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that turns webpages into clean Markdown via the Averra Extract API and manages the account's API keys and quota.

What you can do: Convert any URL into clean, LLM-ready Markdown with metadata, for reading or summarizing pages in a session. Check the account's monthly quota and remaining requests. Create, list and revoke API keys on the Averra account.
When to use it: Useful when an assistant needs to read webpages as tidy Markdown rather than raw HTML, for example to summarize an article or pull key concepts from documentation, and when you want quota and key management inside the chat.
Requirements: Runs as a local stdio process, typically launched with npx, so Node.js is needed. Requires an Averra account and an API key supplied in the AVERRA_EXTRACT_API_KEY environment variable; the free plan includes 50 requests per month. Network access to the Averra API is required, and the base URL can be overridden with AVERRA_EXTRACT_BASE_URL.

Before you install

The API key in AVERRA_EXTRACT_API_KEY is a live credential that grants access to your Averra account. The server can create and revoke API keys, which changes account access, so confirm before letting an assistant do it. Page content and requests are sent to the third-party Averra service, and usage counts against the monthly quota.

Installation

In SourceWeft

Open Extract in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Averra Extract MCP Server

MCP (Model Context Protocol) server for Averra Extract — lets AI agents like Claude, Cursor, and ChatGPT convert any webpage into clean, LLM-ready Markdown.

Listed in the official MCP registry as dev.averra/extract. MCP clients that support registry-based install can reference that identifier directly; for clients that need manual configuration, see the install sections below.

What it does

Exposes the Averra Extract API as 5 MCP tools:

Tool	Description
`averra_extract_url`	Convert any URL to clean Markdown with metadata
`averra_check_usage`	Check monthly quota and remaining requests
`averra_create_api_key`	Create a new API key
`averra_list_api_keys`	List all API keys on the account
`averra_revoke_api_key`	Revoke an API key by ID

Get an API key

Install (Claude Desktop)

Add this to your claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

json

{  "mcpServers": {    "averra-extract": {      "command": "npx",      "args": ["-y", "@averra/extract-mcp"],      "env": {        "AVERRA_EXTRACT_API_KEY": "sk_live_your_key_here"      }    }  }}

{  "mcpServers": {    "averra-extract": {      "command": "npx",      "args": ["-y", "@averra/extract-mcp"],      "env": {        "AVERRA_EXTRACT_API_KEY": "sk_live_your_key_here"      }    }  }}

Restart Claude Desktop. The 5 tools will appear in your session.

Install (Cursor)

Add to ~/.cursor/mcp.json (or use the Cursor MCP settings UI):

json

{  "mcpServers": {    "averra-extract": {      "command": "npx",      "args": ["-y", "@averra/extract-mcp"],      "env": {        "AVERRA_EXTRACT_API_KEY": "sk_live_your_key_here"      }    }  }}

{  "mcpServers": {    "averra-extract": {      "command": "npx",      "args": ["-y", "@averra/extract-mcp"],      "env": {        "AVERRA_EXTRACT_API_KEY": "sk_live_your_key_here"      }    }  }}

Install (other MCP clients)

Any stdio-based MCP client works. Point it at npx -y @averra/extract-mcp with AVERRA_EXTRACT_API_KEY in the environment.

Configuration

Env var	Required	Default	Description
`AVERRA_EXTRACT_API_KEY`	yes	—	Your Extract API key (starts with `sk_live_`)
`AVERRA_EXTRACT_BASE_URL`	no	`https://averra.dev`	Override API host
`TRANSPORT`	no	`stdio`	`stdio` (local) or `http` (hosted)
`PORT`	no	`3000`	Port when `TRANSPORT=http`

Example prompts (Claude Desktop)

Once installed, try:

"Extract the content from https://example.com and summarize it"
"What's my remaining Extract quota this month?"
"Read https://docs.anthropic.com/en/docs/intro and tell me the key concepts"
"List my Extract API keys"

License

MIT

Source: README.md at commit 72dc4a3

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.5LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts