Borrowing it
Nothing to install: this file belongs to abrahamADSK/maya-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/abrahamADSK/maya-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/abrahamADSK/maya-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/abrahamadsk/maya-mcp/claude-md)<a href="https://agentmods.dev/instructions/abrahamadsk/maya-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/abrahamadsk/maya-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.07915 | $0.07915 |
| Opus 5 | $0.03957 | $0.03957 |
| Sonnet 5 | $0.01583 | $0.01583 |
| Haiku 4.5 | $0.00792 | $0.00792 |
Grade A, and why
maya-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
maya-mcp — Critical Context for Claude
Last updated: 2026-04-12 — per-session Vision3D URL is now fully runtime-only: Claude asks the user for the URL on the first Vision3D call, caches it in memory for the rest of the session, and forgets it on MCP restart. No config file field, no pool, no persisted URLs anywhere. This document persists across Claude Code sessions. Consult here to understand the architecture, configuration, and workflows of maya-mcp.
1. Architecture
maya-mcp is a production-grade MCP (Model Context Protocol) server based on FastMCP with 16 MCP tools organized in three layers (plus the optional WorldLabs environment addon):
-
Maya Control (9 direct tools + 1 dispatch tool with 12 actions) — Scene manipulation, modeling, animation, I/O, rendering
- Communicates with Maya via TCP Command Port (default port 8100; moved from the historical 7001 because that port is held by Flame's S+W services on hosts with Autodesk Flame installed)
- Uses
maya_bridge.py(socket bridge) to execute MEL/Python commands - All operations use undo chunks for safe rollback
-
Vision3D Integration (7 actions behind the
maya_vision3ddispatch tool) — Optional addon for AI-powered 3D generation via Vision3D- Communicates via HTTP REST API with Vision3D (port 8000)
- Supports image-to-3D, text-to-3D, and texture painting
- Non-blocking async pattern: submit → poll → download
- Fully per-session URL: the first call that needs a GPU returns
vision3d_url_required. The LLM asks the user for the Vision3D URL in the chat, the user types it, the LLM callsselect_serverwith that URL, and it is cached in memory for the rest of the session. Nothing is written to disk — no config field, no pool, no whitelist. Restarting the MCP server clears the selection. GPU_API_URLenv var is honored as a suggested default the LLM can surface in the prompt, but it is never auto-selected. The user still has to confirm it explicitly viaselect_server.- Not required — maya-mcp works fully without Vision3D
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 472 lines · 7,915 tokens per session scan A 82bd05b7c45c
maya-mcp CLAUDE.md is an instructions file published in the GitHub repository abrahamADSK/maya-mcp (1 stars, last pushed 20d ago), licensed MIT. It adds 7,915 tokens to every session, about $0.0396 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.