Keenable MCP
MCP server for live web search and clean-markdown page fetch over the Keenable web index.
README
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 stdio-only
clients there is a thin npm wrapper (@keenable/mcp) that bridges to the same
endpoint.
Tools
| Tool | Description |
|---|---|
search_web_pages |
Live web search. Args: query (required), plus optional mode, site, published_after / published_before, acquired_after / acquired_before. |
fetch_page_content |
Fetch a URL and return clean markdown. Args: url (required), optional max_chars (default 50000). |
Use it
Remote (recommended)
Any client that supports remote Streamable HTTP servers can connect directly:
{
"mcpServers": {
"keenable": {
"type": "streamable-http",
"url": "https://api.keenable.ai/mcp"
}
}
}
Stdio (Claude Desktop, Cursor, Cline, …)
For clients that only speak stdio, 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 asX-API-Key.KEENABLE_MCP_URL— override the endpoint (defaults tohttps://api.keenable.ai/mcp).
Links
- Docs: https://docs.keenable.ai/mcp-server
- Site: https://keenable.ai
- Registry:
ai.keenable/web-search(Official MCP Registry)
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.