MCP Seekr Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Server host (optional) | 127.0.0.1 |
| PORT | No | Server port (optional) | 8000 |
| LOG_LEVEL | No | Logging level | INFO |
| SEEKR_API_KEY | No | Your Seekr API key | |
| SEEKR_TIMEOUT | No | API request timeout in seconds | 30 |
| SEEKR_BASE_URL | No | Seekr API base URL | https://engine.seekr.sh |
| SEEKR_MAX_RETRIES | No | Maximum number of API retries | 3 |
| MAX_CALLS_PER_MINUTE | No | Rate limiting: maximum calls per minute | 100 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| seekr_queryA | Query for information using Google query engine. This tool performs web queries to find current information, news, and diverse content. Use this for: current events, news, product information, troubleshooting, recent developments, and real-time information. After getting query results, use seekr_prism to get detailed content from specific URLs. |
| seekr_prismA | Prism and extract detailed text content from a specific webpage URL. Use this tool to get full content from URLs found in query results. This provides more detailed information than query snippets alone. |
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: seekr_query performs web searches to find URLs and information, while seekr_prism extracts detailed content from specific URLs. There is no overlap or ambiguity between querying for information and extracting content from a given URL.
Both tools follow a consistent 'seekr_' prefix pattern with descriptive suffixes (query and prism). This naming convention is uniform and predictable, making it easy to understand the tool's function from its name alone.
With only two tools, the server feels thin for a web search and content extraction domain. While the tools cover core workflows (search and extract), the scope might benefit from additional tools for tasks like filtering results, managing search history, or handling different content types.
The tool set covers the essential workflow of querying for information and extracting detailed content from URLs, with clear guidance on how to use them together. A minor gap is the lack of tools for advanced search parameters or content processing, but agents can effectively perform core tasks with the provided tools.