GridStack 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gridstack_initC | Initialize a new GridStack instance with specified options |
| gridstack_add_widgetC | Add a new widget to the grid |
| gridstack_remove_widgetC | Remove a widget from the grid |
| gridstack_update_widgetC | Update widget properties |
| gridstack_move_widgetC | Move a widget to a new position |
| gridstack_resize_widgetC | Resize a widget |
| gridstack_compactC | Compact the grid layout |
| gridstack_floatC | Enable or disable floating widgets |
| gridstack_columnC | Change the number of columns |
| gridstack_cell_heightC | Update cell height |
| gridstack_marginC | Update grid margin/gap |
| gridstack_batch_updateC | Enable/disable batch update mode for efficiency |
| gridstack_saveC | Save grid layout to JSON |
| gridstack_loadC | Load grid layout from JSON |
| gridstack_enableC | Enable or disable the grid |
| gridstack_destroyC | Destroy the grid instance |
| gridstack_get_grid_itemsC | Get all grid items |
| gridstack_set_responsiveC | Configure responsive breakpoints |
| gridstack_will_it_fitC | Check if a widget will fit at specified position |
| gridstack_is_area_emptyC | Check if an area is empty |
| gridstack_get_cell_heightC | Get current cell height |
| gridstack_get_cell_from_pixelC | Convert pixel coordinates to grid cell position |
| gridstack_onC | Add event listener |
| gridstack_offC | Remove event listener |
| gridstack_make_widgetC | Convert an existing DOM element into a grid widget |
| gridstack_remove_allC | Remove all widgets from the grid |
| gridstack_get_marginB | Get current margin values |
| gridstack_get_columnB | Get current number of columns |
| gridstack_get_floatC | Get current float state |
| gridstack_add_gridC | Create a new grid with options and children (static method) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| GridStack API Documentation | Complete GridStack API reference |
| Basic GridStack Example | Simple GridStack implementation |
| Responsive GridStack Example | Responsive grid with breakpoints |
| React Integration | GridStack with React component |
| Vue Integration | GridStack with Vue component |
| Dashboard Template | Complete dashboard layout template |
| Custom CSS Styles | Custom GridStack styling examples |
| Tailwind CSS Integration | Complete Tailwind CSS setup for GridStack |
| CSS Modules Examples | Component-scoped CSS modules for GridStack |
| Tailwind Dashboard Example | Modern dashboard using Tailwind CSS |
TDQS
Scored across 30 tools
Most tools have distinct purposes, but some overlap exists, such as 'gridstack_init' and 'gridstack_add_grid' both creating grids, and 'gridstack_get_*' tools being similar in retrieval function. Descriptions help clarify differences, but minor confusion could occur in selection.
All tools follow a consistent 'gridstack_verb_noun' pattern with snake_case, making them predictable and readable. The naming convention is uniform across all 30 tools, enhancing usability and reducing cognitive load.
With 30 tools, the count is high and feels heavy for a grid management server, potentially overwhelming agents. While the domain is comprehensive, many tools could be consolidated or omitted without losing functionality, indicating an excessive scope.
The tool set provides complete coverage for grid management, including CRUD operations (add, remove, update), configuration (init, enable, destroy), layout handling (save, load, compact), and utility functions (check fit, convert coordinates). No obvious gaps exist for the stated purpose.