Heventure Search MCP Server

Most MCP search servers require you to sign up for API keys (Bing, Google, SerpAPI...). This one works **immediately** — zero configuration, zero

Local serverstdioPython

What is the Heventure Search MCP MCP server?

Heventure Search MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Most MCP search servers require you to sign up for API keys (Bing, Google, SerpAPI...). This one works immediately — zero configuration, zero cost, zero sign-ups.

Setting it up

The server ships on PyPI as heventure-search-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Heventure Search MCP is connected, these are the calls the assistant has available:

  • web_search — The web_search tool exposed by this server
  • get_page_content — The get_page_content tool exposed by this server

Configuration and credentials

You will need 2 environment variables: SERPAPI_KEY, TAVILY_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the heventure search mcp mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Heventure Search MCP's toolset — web_search, get_page_content — is a fair guide to whether it matches your workflow. It is maintained by HughesCuit; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
web_searchThe web_search tool exposed by this server.
get_page_contentThe get_page_content tool exposed by this server.

How to install the Heventure Search MCP MCP server

{
  "mcpServers": {
    "heventure-search": {
      "command": "uvx",
      "args": ["heventure-search-mcp"],
      "env": {
        "SERPAPI_KEY": "your-value",
        "TAVILY_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
SERPAPI_KEYCredential the server authenticates with.Yes
TAVILY_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Heventure Search MCP to web search.
  • Use Heventure Search MCP to get page content.

Frequently asked questions

It connects Heventure Search MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (web_search, get_page_content) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Heventure Search MCP directly.