Haunt MCP Server

Haunt API MCP Server

This is the canonical public MCP package working tree for @hauntapi/mcp-server and GitHub Darko893/mcp-server. The live Haunt API app/site lives separately in /root/haunt. Do not confuse this with /root/haunt/mcp-server, which is a legacy/local copy inside the app repo.

Give Claude, Cursor, Windsurf, and other MCP-compatible agents a clean web extraction tool.

Haunt turns permitted public web pages into structured JSON using natural-language prompts. It can also return clean Markdown for agents, RAG pipelines, notes, and .md files when you need page text instead of typed fields. It is built for agent workflows that need product data, competitor pricing, article content, metadata, lead lists, research snippets, Markdown page text, or other visible web data without maintaining brittle selectors.

Quick Start

One-command agent setup

For the clean CLI path, run:

npx -y --package @hauntapi/cli@latest haunt-cli init

If you already have a Haunt API key:

HAUNT_API_KEY=PASTE_YOUR_KEY_HERE npx -y --package @hauntapi/cli@latest haunt-cli init

The CLI prints the MCP config for Claude, Cursor, Windsurf, and other MCP-compatible clients. It does not edit config files for you.

1. Prove the MCP package is wired in, no key needed

Install the MCP server and call try_demo_extract first. It returns a fixed sample extraction JSON/trace plus docs, signup, pricing, and free-tier links without using credits.

Use Haunt's try_demo_extract tool and show me the signup and docs links.

2. Add a free API key for live extraction

Get a free API key: https://hauntapi.com/#signup

Add this to your MCP client config:

{
  "mcpServers": {
    "haunt": {
      "command": "npx",
      "args": ["-y", "@hauntapi/mcp-server"],
      "env": {
        "HAUNT_API_KEY": "your-api-key"
      }
    }
  }
}

Then ask your agent:

Use Haunt to extract the product name, price, availability, and review count from https://example.com/product

For Markdown output:

Use Haunt extract_markdown to turn https://example.com/docs into clean Markdown.

Capability boundaries

Haunt does not promise universal extraction, CAPTCHA solving, login-wall access, paywall access, or anti-bot circumvention. It works best on permitted public pages and supported rendered pages. When a page is blocked, login-required, CAPTCHA-gated, or too thin to verify, Haunt returns a clear failure signal instead of fabricated data.

Tools

try_demo_extract

No-key activation check. Returns a fixed sample extraction JSON/trace, Haunt's demo endpoint, docs, signup, pricing, MCP info route, and free-tier details. Use this first when a user has installed the MCP server but has not added HAUNT_API_KEY yet.

extract / extract_url

General-purpose extraction from permitted public web pages. extract and extract_url are aliases so hosted MCP docs and local stdio package users can follow the same wording.

Use it for:

• Product names, prices, stock status, reviews
• Competitor pricing pages
• Directories and lead lists
• Job boards
• Research pages
• Supported permitted public pages where you want clean JSON instead of HTML

It accepts optional response_format values: json (default), markdown / md, and raw_html / html.

extract_markdown

Return clean Markdown from a permitted public page. Use this when the agent or workflow wants readable page text for RAG, notes, docs ingestion, or saving as a .md file instead of structured fields.

extract_article

Extract article fields from news, blog, and editorial pages.

Returns title, body text, author, and publish date when available.

extract_metadata

Extract page metadata including title, description, Open Graph tags, Twitter Card tags, canonical URL, and related metadata.

get_usage

Check current plan, monthly credit limit, used credits, reserved credits, and remaining credits. Use this after a live extraction to see what was charged.

Why Haunt

• Natural-language prompts instead of fragile CSS selectors
• Supported fetch paths for JavaScript-heavy pages
• Challenge-aware extraction with machine-readable verification signals (error_code, captcha_provider, requires_human_verification)
• Clean JSON output for agents, databases, and workflows
• Clean Markdown output when the job is page text for agents, RAG, notes, or .md files
• Free tier for testing

Pricing

Credits are not one-to-one requests. Simple public/non-LLM output usually uses 1 credit, normal structured extraction 2, browser-rendered or authenticated extraction 4, and heavy/screenshot extraction 8. Failed, blocked, login/CAPTCHA, provider, and server failures do not burn credits.

Upgrade: https://hauntapi.com/#pricing

Links

• Website: https://hauntapi.com
• Docs: https://hauntapi.com/docs
• Get API key: https://hauntapi.com/#signup
• GitHub: https://github.com/Darko893/mcp-server