RunHarvester

com.runharvesterPublished by runharvester.comOfficial publisherv2.0.0Updated Oct 26, 2026

Web data extraction and browser workflows for AI assistants.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBrowser Automation

Overview

AI-generated overview

Remote MCP endpoint for RunHarvester that gives an assistant web data extraction and browser workflow capabilities.

What you can do
  • Extract structured data from web pages and run browser-based workflows on the assistant's behalf.
  • Tool availability is not fixed: the set of tools exposed depends on the type and scopes of the API key used to connect.
When to use it
Worth adding when an assistant needs to pull data from websites or carry out browser-driven tasks through RunHarvester, and you already have an account and API key there.
Requirements
A remote streamable HTTP endpoint at api.runharvester.com; no local package or runtime. A RunHarvester API key sent in the X-API-Key header is required, and the tools available depend on that key's type and scopes. Network access is needed.
Before you install
The connection requires a secret API key in the X-API-Key header; keep it scoped to only what is needed, since the key's scopes determine which tools the assistant can use. Extraction and browser workflows act on external websites, so review what the assistant is allowed to run.

Installation

In SourceWeft

  1. Open RunHarvester in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.runharvester%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "runharvester": {
      "type": "http",
      "url": "https://api.runharvester.com/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v2.0.0LatestOct 21, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.