Skip to content

Grok inspo get_design_system

How to: Grok inspo get_design_system

client:Grok transport:streamable-http tool:get_design_system

Add inspo to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "inspo": {
      "type": "http",
      "url": "https://inspomcp.dev/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    Ask for something get_design_system does. Grok lists the server's tools on connect and calls get_design_system itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that inspo's identifier in your config matches the one above exactly.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Set these first

inspo will not start until these are set, so get_design_system never becomes available.

  • TOGETHER_API_KEY
  • INSPO_CATALOGUE_URL
  • INSPO_PROFILE
  • INSPO_IMAGES
  • INSPO_MAX_TOKENS

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.