MotionMCP CLAUDE.md

Repository instructions for MotionMCP, a server that lets language models use Motion's task-management API through the Model Context Protocol.

In plain words
What is it for?
They are for building, running unit, integration, and worker tests, checking types, and developing or deploying the Worker.
Why use it?
They provide the commands and test procedures needed to verify changes across the local server and Cloudflare Worker deployment.

Instructions file

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/devondragon/motionmcp/claude-md
Clone the repo
git clone --depth 1 https://github.com/devondragon/MotionMCP
Per session 1,552 This file is loaded in full into every session.
When invoked 1,552 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01552 $0.01552
Opus 5 $0.00776 $0.00776
Sonnet 5 $0.00310 $0.00310
Haiku 4.5 $0.00155 $0.00155

Measured 2d ago against content hash f7ddfb982592, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

MotionMCP 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 2d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

CLAUDE.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Motion MCP Server

MCP server bridging Motion's task management API with LLMs via the Model Context Protocol. Supports both local (stdio) and remote (Cloudflare Workers) deployment.

Common Commands

# Build & Run
npm run build              # Compile TypeScript to dist/
npm run mcp                # Start MCP server (compiled)
npm run mcp:dev            # Start MCP server (ts-node, no build needed)
npm run type-check         # Type checking without emitting files

# Testing (vitest)
npm test                   # Run all unit tests (node + worker projects)
npm test -- handlers.task  # Run a single test file by name fragment
npm test -- --reporter=verbose  # Run with verbose output
npm run test:worker        # Worker auth tests only (runs in workerd)
npm run test:integration   # Integration tests (requires MOTION_API_KEY in .env)

# Worker (Cloudflare)
npm run worker:dev             # Local Worker at http://localhost:8787
npm run worker:deploy          # Deploy to Cloudflare
npm run worker:type-check      # Type-check Worker code (separate tsconfig)

# Verify both entry points compile
npm run build && npm run worker:type-check

# Quick startup smoke test
timeout 3s npm run mcp

Testing

Uses vitest. vitest.config.mts defines two projects that both run under npm test:

  • node — unit tests in tests/**/*.spec.ts, 10s timeout, mocked services, tests/setup.ts silences console.error
  • workertests/worker/**/*.spec.ts, run inside workerd via @cloudflare/vitest-pool-workers

Integration tests live in tests/integration/**/*.integration.test.ts and use their own config.

  • Integration tests: 60s timeout, sequential execution (rate limits), requires MOTION_API_KEY env var
  • Handler tests mock MotionApiService and WorkspaceResolver; service returns use ListResult<T> shape ({ items, truncation })
  • Worker tests cover src/worker.ts authentication. They must run in workerd, not Node: crypto.subtle.timingSafeEqual is a Workers extension Node does not implement, and the path rewrites depend on Workers Request/URL semantics. Bindings come from wrangler.toml with fake MOTION_API_KEY/MOTION_MCP_SECRET values injected in the config, and MotionMCPAgent.serve()/mount() are stubbed so authorized requests are observable without a live MCP session.
  • The config is .mts because @cloudflare/vitest-pool-workers is ESM-only and the package is CommonJS.

Read the full file on GitHub · 125 lines

Changes

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.

  1. 2d ago First seen · 125 lines · 1,552 tokens per session scan A f7ddfb982592

Subscribe to this mod's changes

MotionMCP CLAUDE.md is an instructions file published in the GitHub repository devondragon/MotionMCP (29 stars, last pushed 8d ago), licensed Apache-2.0. It adds 1,552 tokens to every session, about $0.0078 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-30.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens