@svgrid/mcp - Model Context Protocol server for SvGrid
The SvGrid MCP server gives an AI coding agent real demo source, current documentation, and the curated API reference as callable tools - and then checks the code the agent writes against the real exported surface of the installed version, returning the exact replacement for every wrong prop, column key, and piece of Svelte 4 syntax. No API key. It is listed in the official MCP registry as com.svgrid/svgrid.
Connect
Hosted, with nothing to install: point any MCP client at https://mcp.svgrid.com/mcp, or run claude mcp add --transport http svgrid https://mcp.svgrid.com/mcp. Locally over stdio, which adds the Svelte compiler pass and the SvGrid Studio tools and keeps every byte on your machine: claude mcp add svgrid -- npx -y @svgrid/mcp. Claude Desktop, Cursor, VS Code, and Zed each take the same thing in their own config format.
Tools
The local server exposes 36 tools and the hosted endpoint six. The verification, documentation and example tools are free; the SvGrid Studio generators are commercial.
check_svgrid_code- Check a file against the real exported surface of the installed version and return line-numbered diagnostics, each with the exact replacement.list_examples- List every demo with id, title, and a one-line blurb.get_example_source- Return the full .svelte source of one demo, verbatim, including imports.list_docs- List every documentation page (slug + title).get_doc- Return the markdown for a single doc page.search_docs- Substring search across all docs, with an excerpt around the first hit.get_api_reference- The curated public-API surface, grouped by category.
The Studio generators are introspect_source (infer an EntitySchema from a Drizzle schema file or sample JSON rows) and scaffold_entity (generate runnable SvelteKit files from that schema), plus 27 studio_* tools that drive the same validated project model the visual designer uses: entities, screens, blocks, forms, auth, access, tenancy, data layer, deploy target, theme, and app generation.
Licensing
The verification and documentation tools are free and need no key. The Studio generators run unlicensed but prepend a notice comment to generated files; set SVGRID_LICENSE_KEY in the MCP server's environment for licensed use.
Privacy
Run locally and nothing leaves the machine: no telemetry, no outbound network calls, no key. The hosted endpoint receives whatever you pass a tool - including the source you give check_svgrid_code - and logs the tool name, duration and query, but never the submitted source itself. Use the local server if your code cannot leave the building.