Harvey Tools
Give your agent hosted tools for scraping, code review, content generation, and analysis with USDC pay-per-call instead of bolting together four separate APIs.
Overview
Harvey Tools is an MCP server for the Build phase that exposes scraping, code review, content generation, and analysis tools to agents via pay-per-call USDC on streamable HTTP.
What is this MCP server?
- Four tool families: web scraping, code review, content generation, and analysis
- LLM-powered tools backed by required XAI_API_KEY (xAI Grok)
- Optional PAYMENT_WALLET for Solana USDC pay-per-call receipts
- Streamable HTTP MCP at tools.rugslayer.com/mcp (npm v1.1.0)
- Remote @meltingpixels/harvey-tools package—no local stdio server in registry
- Registry version 1.1.0
- Four advertised capability areas in description
- One required secret env var: XAI_API_KEY; one optional PAYMENT_WALLET
What problem does it solve?
Shipping agent products means stitching scraping, review, and content APIs—each with different auth, billing, and MCP shapes—which burns solo-builder time.
Who is it for?
Builders already using xAI Grok who want multipurpose agent tools without maintaining custom MCP wrappers for each vendor.
Skip if: Air-gapped workflows, teams that cannot use cloud LLM keys, or anyone who needs guaranteed scrape compliance/legal review out of the box.
What do I get? / Deliverables
After registration, one MCP connection lets your agent invoke four capability classes with shared USDC metering and a single Grok API key.
- MCP tools for scrape, review, generate, and analyze workflows
- Unified pay-per-call USDC charging across tool families
- Agent-ready outputs without custom middleware per capability
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the server is a production integration layer—your agent calls remote tools while you ship features, not while you are still scoping the idea. Integrations is the right subphase: streamable HTTP MCP plus required xAI Grok credentials is classic external-service wiring during implementation.
How it compares
Bundled remote tool MCP with metered USDC, not a local code-review skill or self-hosted Playwright stack.
Common Questions / FAQ
Who is Harvey Tools for?
Indie developers and agent authors who want scraping, review, content, and analysis as MCP tools while building integrations in Claude Code, Cursor, or similar clients.
When should I use Harvey Tools?
Use it during Build when your agent needs live web data, diff commentary, generated copy, or analysis and you prefer one paid remote server over many APIs.
How do I add Harvey Tools to my agent?
Add https://tools.rugslayer.com/mcp as a streamable-http MCP server, set XAI_API_KEY in the environment block, optionally set PAYMENT_WALLET, and install/register @meltingpixels/harvey-tools per your client.