Keenable Web Search

Keenable MCP

MCP server for live web search and clean-markdown page fetch over the Keenable web index.

• Hosted endpoint: https://api.keenable.ai/mcp (Streamable HTTP)
• Tools: search_web_pages, fetch_page_content
• Keyless by default (1,000 requests/hour). An optional API key lifts the cap.

The server is hosted, so most clients just point at the URL. For clients (or config paths) that only accept a stdio command there is a thin npm wrapper (@keenable/mcp) that bridges to the same endpoint.

Tools

Use it

Remote (recommended)

Clients with remote MCP support — Cursor, Cline, VS Code, and Claude Desktop's Custom Connectors UI — connect to the URL directly:

{

"mcpServers": { "keenable": { "type": "streamable-http", "url": "https://api.keenable.ai/mcp" } } }

Stdio (e.g. Claude Desktop's claude_desktop_config.json)

For clients or config paths that only accept a stdio command, run the wrapper with npx:

{

"mcpServers": { "keenable": { "command": "npx", "args": ["-y", "@keenable/mcp"] } } }

That is all you need for keyless use.

API key (optional)

Keenable is keyless by default. To lift the hourly rate limit, pass a key.

Remote:

{

"mcpServers": { "keenable": { "type": "streamable-http", "url": "https://api.keenable.ai/mcp", "headers": { "X-API-Key": "YOUR_KEY" } } } }

Stdio:

{

"mcpServers": { "keenable": { "command": "npx", "args": ["-y", "@keenable/mcp"], "env": { "KEENABLE_API_KEY": "YOUR_KEY" } } } }

How the wrapper works

@keenable/mcp is a small stdio bridge: it connects to the hosted server over Streamable HTTP and forwards every tool the server exposes. There is no search logic in this package; the index and tools live behind https://api.keenable.ai/mcp. Environment variables:

• KEENABLE_API_KEY — optional API key, sent as X-API-Key.
• KEENABLE_MCP_URL — override the endpoint (defaults to https://api.keenable.ai/mcp?keenable_title=npm).

Development

npm install

npm test

npm test runs the unit tests and a stdio smoke test of the discovery build (src/discovery.js): initialize must advertise the server metadata and tools/list must return both tools. CI runs it on Node 18, 20 and 22 and on the oldest MCP SDK the package accepts.

Releasing

The npm version lives only in package.json; the bridge reads it at runtime. server.json (the MCP Registry manifest) must repeat it as a literal in packages[].version, so bump both. npm run check:version compares them and runs automatically before npm publish. The top-level server.json version is the registry entry's own version and is bumped whenever server.json changes.

Links

• Docs: https://docs.keenable.ai/mcp-server
• Site: https://keenable.ai
• Registry: ai.keenable/web-search (Official MCP Registry)

License

MIT