Skip to content
mcp/skillhub

MY Websearch MCP Server

by wtznicyio.github.wtznicy/my-websearchv1.0.23

MyWebSearch - multi-engine web search MCP server, CLI and local daemon. No API keys required.

1Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active5d ago

Install MY Websearch MCP server

Install in Claude Code

claude mcp add my-websearch -e EXA_API_KEY='<exa-api-key>' -- npx -y my-websearch

Configuration

VariableRequiredSecretDescription
EXA_API_KEY—yesOptional Exa API key (https://dashboard.exa.ai/api-keys) — only needed for the exa search engine

Freshness

Active — last maintenance signal 5d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-10-05 · 5d ago · GitHub

  2. Latest release

    2026-10-05 · 5d ago · GitHub · 1.0.23

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-10-05 · 5d ago · official registry · v1.0.23

FAQ

›How do I install the MY Websearch MCP server in Claude Code?

Run: claude mcp add my-websearch -e EXA_API_KEY='<exa-api-key>' -- npx -y my-websearch. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does MY Websearch require an API key?

Yes. It expects EXA_API_KEY, of which 1 is a secret.

›Can I use MY Websearch as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is MY Websearch in the official MCP registry?

Yes, as io.github.wtznicy/my-websearch.

Alternatives to MY Websearch

Other web search MCP servers.

View all