kendo-angular-unofficial-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_kendo_componentsA | Retrieves a list of all main Kendo UI for Angular components available in the documentation. |
| list_component_topicsA | Given a component ID (e.g., 'grid'), returns a list of subtopics and articles available for that component. Note: For deep API references (components, directives, classes), use the 'list_component_api' tool instead. |
| list_component_apiA | Given a component ID (e.g., 'grid'), returns a list of detailed API references (components, directives, interfaces, services) available for that component. |
| read_kendo_docA | Reads a specific Kendo UI documentation article and returns it in Markdown format. Includes a list of available demo examples at the end. Use read_demo_source to fetch demo source code. |
| read_demo_sourceA | Fetches the source code files for a specific Kendo UI demo example. Use the metaUrl values listed in the 'Demos' section of read_kendo_doc output. |
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 5 tools
Each tool has a clearly distinct purpose: listing all components, retrieving API details, fetching topics/ articles, reading documentation articles, and fetching demo source code. The description of list_component_topics explicitly directs users to list_component_api for deep API references, preventing confusion.
All tools follow a consistent verb_noun pattern: list_, read_. The names are descriptive and predictable, making it easy to infer functionality.
With 5 tools, the server is well-scoped for a documentation API. Each tool covers a necessary operation without being excessive or insufficient.
The tool set covers the full workflow of browsing Kendo UI Angular documentation: discovering components, exploring APIs, reading articles, and examining demo source code. No obvious gaps are present.