Skip to main content
Glama
Averra Extract MCP

Averra Extract MCP

by Swwyymm

Averra Extract MCP 서버

Averra Extract용 MCP(Model Context Protocol) 서버 — Claude, Cursor, ChatGPT와 같은 AI 에이전트가 모든 웹 페이지를 LLM이 바로 사용할 수 있는 깔끔한 Markdown으로 변환할 수 있게 해줍니다.

공식 MCP 레지스트리에 dev.averra/extract로 등록되어 있습니다. 레지스트리 기반 설치를 지원하는 MCP 클라이언트는 해당 식별자를 직접 참조할 수 있으며, 수동 구성이 필요한 클라이언트는 아래 설치 섹션을 참조하십시오.

기능

Averra Extract API를 5개의 MCP 도구로 노출합니다:

도구

설명

averra_extract_url

모든 URL을 메타데이터가 포함된 깔끔한 Markdown으로 변환

averra_check_usage

월간 할당량 및 남은 요청 수 확인

averra_create_api_key

새 API 키 생성

averra_list_api_keys

계정의 모든 API 키 나열

averra_revoke_api_key

ID를 사용하여 API 키 취소

Related MCP server: mcp-server-scraper

API 키 받기

averra.dev에서 가입하세요 — 무료 플랜에는 월 50회 요청이 포함되어 있습니다.

설치 (Claude Desktop)

claude_desktop_config.json에 다음을 추가하세요:

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

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

Claude Desktop을 재시작하세요. 5개의 도구가 세션에 나타납니다.

설치 (Cursor)

~/.cursor/mcp.json에 추가하거나 Cursor MCP 설정 UI를 사용하세요:

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

설치 (기타 MCP 클라이언트)

모든 stdio 기반 MCP 클라이언트에서 작동합니다. 환경 변수에 AVERRA_EXTRACT_API_KEY를 설정하고 npx -y @averra/extract-mcp를 가리키도록 하세요.

구성

환경 변수

필수

기본값

설명

AVERRA_EXTRACT_API_KEY

예

—

Extract API 키 (sk_live_로 시작)

AVERRA_EXTRACT_BASE_URL

아니요

https://averra.dev

API 호스트 재정의

TRANSPORT

아니요

stdio

stdio (로컬) 또는 http (호스팅)

PORT

아니요

3000

TRANSPORT=http일 때의 포트

예시 프롬프트 (Claude Desktop)

설치 후 다음을 시도해 보세요:

라이선스

MIT

Available Tools

5 tools
averra_check_usageCheck Extract API UsageA
Read-onlyIdempotent

Check the current month's Extract API usage and remaining quota for the authenticated account.

Usage is counted per user across all API keys (not per key). Cached requests also count against the quota. The counter resets at the start of each calendar month (UTC).

Args:

  • response_format ('markdown' | 'json', optional): Output format. Default 'markdown'.

Returns: For JSON format: { "plan": "free" | "starter" | "pro" | "scale", "monthly_limit": number, // Max requests allowed this month "used": number, // Requests made so far this month "remaining": number // max(0, monthly_limit - used) }

For Markdown format: a summary showing plan, limit, used, and remaining.

Examples:

  • Use when: "How many extracts do I have left this month?"

  • Use when: Before a batch of extracts, to confirm sufficient quota.

  • Use when: User asks "Am I on the free plan?" — the plan field answers this.

Error Handling:

  • 401: Invalid API key — check AVERRA_EXTRACT_API_KEY

Inputs: response_format.

averra_create_api_keyCreate Extract API KeyA

Create a new Extract API key for the authenticated account.

IMPORTANT: The plaintext key is returned ONLY ONCE in this response. It cannot be retrieved later — only the prefix is stored for display. If lost, the key must be revoked and a new one created.

The new key automatically inherits the plan and limits from your account's current subscription. You cannot choose a plan — it is determined by your billing state.

Args:

  • response_format ('markdown' | 'json', optional): Output format. Default 'markdown'.

Returns: For JSON format: { "key": string, // FULL plaintext key (shown once) — format: sk_live_<48 hex> "id": string, // Key ID for management operations "prefix": string, // First 12 chars (for display/reference) "plan": "free" | "starter" | "pro" | "scale", "monthly_limit": number, "created_at": string, // ISO 8601 "warning": string // Reminder to save the key }

Examples:

  • Use when: User wants to create a new API key for a different integration.

  • Use when: Rotating keys (create new, then revoke old).

  • Don't use without user confirmation — this creates a credential the user must save.

Error Handling:

  • 401: Invalid API key — check AVERRA_EXTRACT_API_KEY

  • 500: Database error — retry

Inputs: response_format.

averra_extract_urlExtract URL to MarkdownA
Read-onlyIdempotent

Convert any webpage URL into clean, LLM-ready Markdown using Averra Extract.

This tool fetches the page (executing JavaScript via a headless browser), strips navigation/ads/UI clutter via Mozilla Readability, converts the main content to Markdown, and returns it along with metadata (title, word count, links, language). Results are cached for 7 days and shared across users.

Use this when you need the actual content of a webpage for an LLM — e.g. reading a blog post, docs page, article, or product page to answer a question or synthesize information.

Args:

  • url (string, required): The webpage URL. Accepts https://example.com or bare example.com (https:// is auto-added). Max 2048 chars.

  • response_format ('markdown' | 'json', optional): Output format. Default 'markdown'.

Returns: For JSON format, structured data: { "markdown": string, // Clean markdown content of the page "metadata": { "title": string, // Page title (from first H1 or URL fallback) "word_count": number, // Word count of extracted text "links": string[], // Unique URLs found in the content "language": string, // "en" or "unknown" "timestamp": string // ISO 8601 extraction time }, "warning": string (optional) // Present if content is thin (<200 words) }

For Markdown format: a formatted document with title, metadata summary, and the extracted markdown.

Counts against your monthly Extract quota (including cached requests). Use averra_check_usage to see remaining quota.

Examples:

  • Use when: "Summarize this blog post: https://example.com/post" → extract then summarize

  • Use when: "What does this docs page say about auth?" → extract then answer

  • Don't use when: You just need a link preview or metadata (this returns full content)

  • Don't use when: You need JSON extraction with a schema (not supported yet)

Error Handling:

  • 400: URL rejected by safety checks (malformed, private IP, unreachable host) — check the URL resolves publicly.

  • 401: Invalid API key — check AVERRA_EXTRACT_API_KEY env var

  • 404: Page not found at URL

  • 429: Monthly limit exceeded — upgrade plan or wait

  • 502/503/504: Scraping service temporarily unavailable — retry

Inputs: url (required), response_format.

averra_list_api_keysList Extract API KeysA
Read-onlyIdempotent

List all API keys for the authenticated account.

Returns metadata only — the actual plaintext keys are never returned (only prefixes). Includes both active and revoked keys, ordered by creation date (newest first).

Args:

  • response_format ('markdown' | 'json', optional): Output format. Default 'markdown'.

Returns: For JSON format: { "keys": [ { "id": string, // Key ID (use for revoke operations) "key_prefix": string, // First 12 chars of key "plan": "free" | "starter" | "pro" | "scale", // Decorated from the account profile — identical across every key on the account. "monthly_limit": number, // Decorated from the account profile — identical across every key on the account. "is_active": boolean, // false if revoked "created_at": string, // ISO 8601 "revoked_at": string | null // ISO 8601 if revoked, null otherwise } ] }

Examples:

  • Use when: User asks "How many API keys do I have?"

  • Use when: Need to find a key's ID before revoking it.

  • Use when: Auditing which keys exist and their plans.

Error Handling:

  • 401: Invalid API key — check AVERRA_EXTRACT_API_KEY

Inputs: response_format.

averra_revoke_api_keyRevoke Extract API KeyA
DestructiveIdempotent

Revoke an Extract API key by its ID. The key is immediately deactivated and cannot be reactivated — create a new key if needed.

SAFETY: You cannot revoke the key that is currently authenticating the MCP server itself (the one set in AVERRA_EXTRACT_API_KEY). Attempting to do so returns a 400 error.

Args:

  • id (string, required): The key ID to revoke. Get this from averra_list_api_keys.

  • response_format ('markdown' | 'json', optional): Output format. Default 'markdown'.

Returns: For JSON format: { "message": "API key revoked", "id": string, // The revoked key's ID "prefix": string, // Key prefix for confirmation "revoked_at": string // ISO 8601 revocation time }

This operation is destructive (cannot be undone) but idempotent (revoking an already-revoked key is safe).

Examples:

  • Use when: User explicitly asks to revoke a specific key.

  • Use when: Rotating keys — after confirming the new key works.

  • Don't use without user confirmation — this invalidates a credential.

Error Handling:

  • 400: Attempting to revoke the currently-authenticating key — use a different auth key first

  • 401: Invalid API key — check AVERRA_EXTRACT_API_KEY

  • 404: Key not found or already revoked

Inputs: id (required), response_format.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers