Averra Extract MCP
# Averra Extract MCP Server
MCP (Model Context Protocol) server for [Averra Extract](https://averra.dev) — lets AI agents like Claude, Cursor, and ChatGPT convert any webpage into clean, LLM-ready Markdown.
**Listed in the official [MCP registry](https://registry.modelcontextprotocol.io) 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
Sign up at [averra.dev](https://averra.dev) — the free plan includes 50 requests/month.
## 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"
}
}
}
}
```
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"
}
}
}
}
```
## 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
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: check_usage monitors quota, create_api_key and revoke_api_key manage key lifecycle, list_api_keys provides inventory, and extract_url performs content extraction. The descriptions explicitly differentiate use cases, preventing agent misselection.
All tools follow a perfect 'averra_verb_noun' pattern (e.g., averra_check_usage, averra_create_api_key), using snake_case consistently. The prefix 'averra_' identifies the server domain, and verb-noun combinations are uniformly applied across all five tools.
Five tools is well-scoped for the server's purpose of API key management and content extraction. Each tool earns its place: quota checking, key creation/listing/revocation, and the core extraction functionality, with no redundancy or obvious omissions for this focused domain.
The toolset provides complete coverage for API key lifecycle (create, list, revoke) and quota management, with the core extraction functionality included. A minor gap exists in lacking a tool for updating or managing account plans, but agents can work around this using existing tools for most workflows.