Skip to content

Grok 3DAssets.dev list_ai_models

How to: Grok 3DAssets.dev list_ai_models

client:Grok transport:streamable-http tool:list_ai_models

Add 3DAssets.dev to Grok

  1. 01

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

{
  "mcpServers": {
    "catalogue": {
      "type": "http",
      "url": "https://3dassets.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that 3DAssets.dev'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

3DAssets.dev will not start until these are set, so list_ai_models never becomes available.

  • THREEDASSETS_API_KEY

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.