Sketchfab MCP Server

A Model Context Protocol (MCP) server for interacting with Sketchfab to find & download 3D models. The sketchfab mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

A Model Context Protocol (MCP) server for interacting with Sketchfab's 3D model platform. This MCP allows you to search, view details, and download 3D models from Sketchfab directly through Claude or Cursor.

• Search for 3D Models — Find models on Sketchfab using keywords, tags, and categories
• View Model Details — Get comprehensive information about specific models
• Download Models — Download models in various formats (gltf, glb, usdz, source)

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration

You will need 2 environment variables: SKETCHFAB_API_KEY, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18 or higher - A Sketchfab API key (for authentication)

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the sketchfab mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by gregkop; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.