mcp-zenkit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENKIT_API_KEY | Yes | Your Zenkit API key |
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 |
|---|---|
| zenkitB | Raw Zenkit API access. Complete control over any Zenkit operation via direct API calls. Pass method, path, and optional body. |
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
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined as raw API access.
With only one tool named 'zenkit', there is no inconsistency. The name matches the server's domain and is clear.
A single tool for a server providing Zenkit access feels thin. While the tool is powerful, it lacks specialization, making the set minimal.
The tool provides raw API access to all Zenkit operations, offering complete coverage of the domain. No obvious gaps exist.