Local MCP server/Search

ContextFetch MCP server

Local MCP server

ContextFetch gives an agent web search results as clean Markdown with query-pruned context, plus research, crawl, and map. It is a local stdio server started with npx -y @contextfetch/mcp and requires Node 18+. The free tier allows 25 searches a day without a key; paid use costs $1 per 1,000 searches and uses CONTEXTFETCH_API_KEY. The api.contextfetch.dev host is the API base rather than the MCP transport.

none for the free tier; optional CONTEXTFETCH_API_KEY for paid use Source checked Nov 12, 2026 Local install path Reviewed 2026-11-16
About

Where it fits

Agents needing clean Markdown search results with a free daily allowance through a local stdio server.

  • Register the stdio server with npx -y @contextfetch/mcp.
  • Search the web for clean Markdown results.
  • Add CONTEXTFETCH_API_KEY for paid volume.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server

Requires Node 18+. The free tier needs no key; set CONTEXTFETCH_API_KEY for paid use. api.contextfetch.dev is the API base, not the MCP transport.

  1. Install Node 18+

    Confirm Node.js 18 or newer is on PATH.

  2. Register the stdio server

    Run claude mcp add contextfetch -- npx -y @contextfetch/mcp, or add command npx with args -y @contextfetch/mcp to your client config.

  3. Add the optional key

    Set CONTEXTFETCH_API_KEY only for paid use. The free tier works without a key.

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

ContextFetch repositoryhttps://github.com/lachy3433/contextfetch-mcp