Handsontable MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_docA | Fetch Handsontable documentation for a specific topic and framework. Returns the documentation as markdown. |
| search_docsA | Search for Handsontable documentation topics by keyword. Returns matching API endpoints, guide topics, and categories. |
| list_categoriesA | List all available documentation categories with their topics. Useful for browsing the documentation structure. |
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 3 tools
Each tool has a clearly distinct purpose: fetching a specific doc, listing categories, and searching. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case: get_doc, list_categories, search_docs.
With 3 tools, the set is well-scoped for a documentation server, covering essential operations without being too sparse or excessive.
The tool surface covers searching, listing categories, and fetching specific docs, providing a complete workflow for documentation access.