Skip to main content
Install Keenable from the catalog you already use. Every listing on this page points at Keenable’s hosted MCP server or at the keenable-web-search skill. The MCP server listings give you the same tools wherever you find them: search_web_pages and fetch_page_content. The skill listings give your agent search through a Python script, with no MCP client and no page fetch tool. All listings but the OpenAI plugin work with no API key to start. See the MCP server reference for per-client setup.

Listings

If a listing shows a setup that differs from the MCP server page, follow the MCP server page.

Read the registry entry

The Official MCP Registry serves each published version of ai.keenable/web-search as JSON. To see the latest manifest, with its remote URL and npm package:
The entry with "isLatest": true is the current one. Its remotes list holds a Streamable HTTP endpoint with an optional X-API-Key header, and its packages list holds @keenable/mcp with an optional KEENABLE_API_KEY variable.

VS Code from the GitHub MCP Registry

The GitHub MCP Registry backs one-click MCP installs in VS Code. It reads the same server.json as the Official MCP Registry, so Install on the listing adds the registry’s remote: the keyless endpoint https://api.keenable.ai/mcp-public?keenable_title=mcp-registry. That endpoint publishes no OAuth discovery, and it accepts an optional X-API-Key header. See Keyless endpoint for listings and presets. To write the entry by hand, for example because you will add your own key, point it at /mcp:
.vscode/mcp.json
Leave out headers to run on the public tier. VS Code uses the top-level key servers, not mcpServers. Open Copilot Chat in agent mode: the tools picker lists search_web_pages and fetch_page_content.

Local bridge from npm

mcp.so, LobeHub and the registry’s npm entry use the stdio bridge, which runs locally and forwards to the hosted server. This is the shape for clients that take only local commands, such as Claude Desktop’s config file:
Add "env": { "KEENABLE_API_KEY": "keen_<your_key>" } to the entry to use your key. See Local bridge (with an API key).

Install the agent skill

The skill gives agents web search through a Python script, with no MCP client. Install it into a project for Claude Code:
The command prints where it copied the skill. Change -a for another agent. See Agent skill.
Most listings start keyless, on the shared public tier at lower rate limits. For the registry entries, Glama, PulseMCP, mcp.so and LobeHub, add an API key in the X-API-Key header, or as KEENABLE_API_KEY for the npm bridge, to use your organization’s limits. The skill takes no key. The Claude connector and the Antigravity plugin take no key either, and their pages show how to add Keenable on your own account. The OpenAI plugin is the exception: you sign in to a Keenable account, and usage counts against that organization’s limits and pricing. See ChatGPT and Codex.

Integrations

Connect Keenable web search to your agent stack: LangChain, LlamaIndex, Haystack, MCP and more.

Cursor

Add Keenable to Cursor over MCP with one click, an mcp.json entry or the Keenable CLI, and turn off Cursor’s own web search.

CLI

Install the Keenable CLI, sign in once, add Keenable to Claude Code, Cursor and Codex over MCP, and search, fetch and run monitors from the terminal.