SvGrid MCP
The SvGrid MCP server checks agent code against the real SvGrid API and serves docs pinned to the installed version.
- 182 ★ on the repository
- Last commit
Minimal access
Why this level
- The server reads files the agent passes and may send requests to the remote mcp.svgrid.com when HTTP is chosen.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/svgrid-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The server reads files the agent passes and may send requests to the remote mcp.svgrid.com when HTTP is chosen.
This is third-party code. Review the repository files before installing.
What it does
The server sits in the `packages/mcp` folder of the SvGrid monorepo and is published as `@svgrid/mcp`. The model gets exact property, method and event names of the Svelte 5 grid plus the source of every demo as grounding, instead of inventing an API from memory. There are five tools. `svgrid_search` searches docs, demos and the API surface in one call, `svgrid_get` reads one doc, demo or the API in full, `svgrid_check_code` verifies a file against the real API and the Svelte compiler and returns diagnostics with line numbers and a ready replacement, `svgrid_preview` renders a live grid from columns and rows, `svgrid_scaffold` turns a Drizzle schema or sample rows into SvelteKit files. Docs and demos are also served as MCP resources, and four prompts ship ready to run (`build_grid`, `build_sheet`, `explain_api`, `review_grid_code`).
Who it is for. Svelte 5 and SvelteKit developers building tables on SvGrid with Claude Code, Cursor or Zed.
Good fit when
- An agent writes a grid component and verifies it with `svgrid_check_code` right away.
- A fitting demo with grouping or pivot is needed and its source is taken.
- Migrating from another library: the agent catches renamed props like `rowData` and `accessorKey`.
- A SvelteKit page with a grid is scaffolded from a Drizzle schema.
Not a fit when
- The project uses another grid: the server knows only the SvGrid API.
- A type check of the whole project is needed: the tool inspects one file.
- The Svelte compiler is not installed: diagnostics fall back to API rules without a file parse.
Example request
Check the grid file with svgrid_check_code, fix prop names from the hints and show the result in svgrid_preview.MCP
- Transport
- stdio, http
- Authentication
- not required
Limitations
The server knows SvGrid only. Extended library features live in the `@svgrid/enterprise` package and terms are listed on svgrid.com. The Svelte compiler is optional: it is picked up from the project or beside the package, and the `compiler` field in the response says which mode ran. Pre-3.0 tool names still answer but are not listed. The server answers only about SvGrid and its packages, general Svelte questions are left to other sources. The code check reports how it ran (`compiler`), so a no-errors answer without the compiler does not guarantee the file builds.
How to disable. Remove the svgrid entry from the MCP client config. The server is stateless and keeps no data on disk.
FAQ
Which tools does the server have?
Five: `svgrid_search`, `svgrid_get`, `svgrid_check_code`, `svgrid_preview` and `svgrid_scaffold`.
What does svgrid_check_code verify?
Import names, `<SvGrid>` props, column keys and API methods against the installed version, Svelte 5 mistakes (`export let`, `on:`, `createEventDispatcher`) and, when the compiler is available, file syntax.
Is there a remote server?
Yes, `https://mcp.svgrid.com/mcp` over streamable HTTP; locally it runs with `npx -y @svgrid/mcp`.
Which Svelte version is needed?
SvGrid is written for Svelte 5 with runes and the server checks code against exactly those rules.
How do I check a grid file?
Pass the file to `svgrid_check_code`: the response holds diagnostics with line numbers and a ready replacement for each finding.
Discussion
No questions or reviews yet.
Related
MCP serversRevoGrid MCP gives an agent version-aware documentation, examples, migration notes and API types for the RevoGrid data grid.
Svelte's official MCP server and plugin: current docs, component autofixing and Svelte 5 skills
MCP server giving an agent reference answers on Svelte 5 runes and SvelteKit: signatures, parameters and examples at three depths
The @microcharts/mcp server: an agent picks from 106 tiny React charts, gets ready props and receives SVG with alt text
Official MCP server for UI5 Web Components for React: component APIs, documentation and Fiori app templates for the agent
Nuxt MCP Dev
nuxt-mcp-dev / vite-plugin-mcp
A Nuxt module and a Vite plugin start an MCP server on the dev server port so the agent sees config, pages, components, auto-imports and the module graph
README in short
The package README explains why the server has five tools, how code checking works with a diagnostics example, which resources and prompts exist and how to connect the server to Claude Desktop, Claude Code, Cursor and Zed.