MCP Server for Autodesk ShotGrid REST API

@chordee

リポジトリ

基本情報

カテゴリ

開発者ツール

ライセンス

MIT license

トランスポート

stdio

作者

chordee

MCP Server for Autodesk ShotGrid REST API について

Project repository for mcp-server-shotgrid

MCP Server for Autodesk ShotGrid REST API の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcp-server-shotgrid": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "{REPO_DIR}",
        "main.py",
        "-host",
        "https://your-shotgrid-url",
        "-ci",
        "your_client_id",
        "-cs",
        "your_client_secret"
      ]
    }
  }
}

MCP Server for Autodesk ShotGrid REST API のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is MCP Server for Autodesk ShotGrid REST API?

This MCP server, built with FastMCP, enables LLM agents to programmatically query and manage Autodesk ShotGrid entities (projects, assets, tasks, users, notes, versions, bookings, etc.) via the ShotGrid REST API. It uses OAuth2 authentication and communicates over stdio transport, designed for VFX, animation, and game development pipelines that rely on ShotGrid.

How to use MCP Server for Autodesk ShotGrid REST API?

Obtain your ShotGrid host URL, OAuth2 client ID, and client secret. Run the server with uv run --directory {REPO_DIR} main.py -host https://your-shotgrid-url -ci your_client_id -cs your_client_secret. All three arguments are required. The server exposes MCP tools that your LLM agent can call.

Key features of MCP Server for Autodesk ShotGrid REST API

Connects to Autodesk ShotGrid using OAuth2 authentication.
Exposes ShotGrid REST API operations as MCP tools via FastMCP.
Query projects, users, assets, tasks, notes, versions, bookings, and more.
Retrieve detailed information about specific entities by ID.
Designed for integration with LLM-based workflows (stdio transport).
Modular codebase separating server logic from API wrapper.

Use cases of MCP Server for Autodesk ShotGrid REST API

AI assistant that retrieves project status or shot lists for production managers.
Automated task assignment and note retrieval for review workflows.
Querying recent versions or bookings across multiple projects.
Extracting user and entity information for pipeline tool integration.

よくある質問

What authentication does the server support?

The server uses OAuth2 authentication with a client ID and client secret. Your ShotGrid account must have API access enabled.

What transport does the server use?

The server uses `transport="stdio"` only, as implemented by FastMCP.

What are the runtime requirements?

Python 3.11 is required, along with the `httpx`, `httpx-auth`, and `mcp.server.fastmcp` packages.

Can I customize the available tools?

Yes. The tools are defined in `main.py` and can be extended or modified for your workflow. The underlying ShotGrid REST API logic is in `shotgrid_rest.py`.

How do I find the full argument and return details for each tool?

The function docstrings in `main.py` document all arguments and return values for the available MCP tools.

「開発者ツール」の他のコンテンツ

discoverGPT

Joe Monastiero

discoverGPT is visualAI's MCP gateway for AI commerce: one connection gives Claude 40 tools spanning product search, data-quality review, AI-discovery feeds, and virtual try-on, all backed by a single canonical product c

Vibgrate MCP

Vibgrate

Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

Final POS – Custom POS Builder

Final Commerce

Build custom POS apps with your AI agent. Final's MCP server lets developers scaffold checkout flows, adapt vetted screen blueprints for counter POS, self-checkout kiosks, restaurant ordering and payment terminals, previ

Routebase

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.