UseKeen Documentation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USEKEEN_API_KEY | Yes | Your UseKeen API key for authentication |
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 |
|---|---|
| usekeen_package_doc_searchB | Search documentation of packages and services to find implementation details, examples, and specifications. The user's query should be as specific as possible to get the best results. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose focused on searching documentation.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'usekeen_package_doc_search' follows a descriptive pattern.
One tool is too few for a server that appears to cover documentation search for packages and services. This minimal set limits functionality and suggests an incomplete or narrow implementation for the domain.
The tool set is severely incomplete for a documentation server. It only provides search functionality, lacking essential operations like browsing documentation categories, retrieving specific documents, or managing documentation updates, which are typical for such domains.