Keenable MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEENABLE_API_KEY | No | Optional API key for higher rate limits | |
| KEENABLE_MCP_URL | No | Override the endpoint URL | https://api.keenable.ai/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_web_pagesA | Live web search over the Keenable web index. Describe the ideal page, not keywords. Use date/site filters to narrow results. |
| fetch_page_contentA | Fetch and extract content from a web page. Returns the page content in markdown format. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one fetches content from a specific page, the other searches the web. There is no overlap.
Both tools use a consistent verb_noun pattern in snake_case: 'fetch_page_content' and 'search_web_pages'.
Only 2 tools, which is below the typical 3-15 range, but the domain is narrow (web search and page fetching), so it may be acceptable.
The set covers the basic workflow of searching and fetching content. Minor gaps exist (e.g., no tool to list search results separately), but the core functionality is complete.