Allows coding agents to record mobile app animations, analyze frame drops, and automatically apply motion tuning fixes to source code.
Also known as keyframer-dev/inspector, inspector, @keyframerdev/inspector
- Stars
- 6
- Tools
- —
- Downloads, 30 days
- 987
- Latest version
- 0.4.0
- Last commit
- Nov 14, 2026
- License
- MIT
What is Keyframer Inspector MCP?
Keyframer Inspector allows coding agents to record mobile app animations, analyze frame drops, and automatically apply motion tuning fixes to source code.
Summary generated from the project's README
About Keyframer Inspector MCP server
Keyframer Inspector serves as a motion debugger for mobile application developers working with iOS, Android, Flutter, or React Native. It allows users to record app animations and analyze why specific frames dropped. By connecting an app via an SDK to the macOS desktop application, developers can scrub through recordings like a video to see exactly which line of code triggered an animation and how much performance it cost.
The server functions as an MCP bridge for coding agents like Claude Code, Cursor, or Windsurf. Once enabled in the desktop app settings, an agent can use tools to record app scenarios, read traces, and take screenshots. It specifically supports a fix loop using check and recheck commands, where the agent measures performance, modifies the source code, and re-measures until frame drops are resolved. All recordings and data remain local to the Mac unless a user explicitly creates a share link.
What you can do with it
- 1Automated motion tuningAn AI agent can automatically adjust animation durations or spring settings in your source code to fix performance issues.
- 2Debugging frame dropsDevelopers can identify the specific code responsible for animation lag and frame drops.
- 3Autonomous performance fixingA coding agent can run a continuous loop of measuring, changing code, and re-measuring to eliminate motion problems.
- 4CI/CD quality gatingYou can use animation recordings to gate pull requests within your continuous integration pipeline.
Written from the project's README. Every use case is checked against a quote from it.
How to install Keyframer Inspector MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Keyframer Inspector MCP in Claude Code
$ claude mcp add --env 'KEYFRAMER_VITALS_READ_KEY=<YOUR_KEYFRAMER_VITALS_READ_KEY>' inspector -- npx -y @keyframerdev/inspectorInstall Keyframer Inspector MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"inspector": {
"command": "npx",
"args": [
"-y",
"@keyframerdev/inspector"
],
"env": {
"KEYFRAMER_VITALS_READ_KEY": "<YOUR_KEYFRAMER_VITALS_READ_KEY>"
}
}
}
}Install Keyframer Inspector MCP in VS Code
.vscode/mcp.json
{
"servers": {
"inspector": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@keyframerdev/inspector"
],
"env": {
"KEYFRAMER_VITALS_READ_KEY": "<YOUR_KEYFRAMER_VITALS_READ_KEY>"
}
}
}
}Install Keyframer Inspector MCP in VS Code CLI
$ code --add-mcp '{"name":"inspector","type":"stdio","command":"npx","args":["-y","@keyframerdev/inspector"],"env":{"KEYFRAMER_VITALS_READ_KEY":"<YOUR_KEYFRAMER_VITALS_READ_KEY>"}}'Install Keyframer Inspector MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"inspector": {
"command": "npx",
"args": [
"-y",
"@keyframerdev/inspector"
],
"env": {
"KEYFRAMER_VITALS_READ_KEY": "<YOUR_KEYFRAMER_VITALS_READ_KEY>"
}
}
}
}Install Keyframer Inspector MCP in Codex
$ codex mcp add inspector --env 'KEYFRAMER_VITALS_READ_KEY=<YOUR_KEYFRAMER_VITALS_READ_KEY>' -- npx -y @keyframerdev/inspectorInstall Keyframer Inspector MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.inspector] command = "npx" args = ["-y", "@keyframerdev/inspector"] [mcp_servers.inspector.env] KEYFRAMER_VITALS_READ_KEY = "<YOUR_KEYFRAMER_VITALS_READ_KEY>"
Install Keyframer Inspector MCP in Gemini CLI
$ gemini mcp add -s user -e 'KEYFRAMER_VITALS_READ_KEY=<YOUR_KEYFRAMER_VITALS_READ_KEY>' inspector npx -- -y @keyframerdev/inspectorInstall Keyframer Inspector MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"inspector": {
"command": "npx",
"args": [
"-y",
"@keyframerdev/inspector"
],
"env": {
"KEYFRAMER_VITALS_READ_KEY": "<YOUR_KEYFRAMER_VITALS_READ_KEY>"
}
}
}
}Configuration
KEYFRAMER_VITALS_READ_KEYSecretOptional: a Motion Vitals workspace read key (kfw_...) for field_problems and field_compare. Every other tool works without it.
| Name | Description | |
|---|---|---|
| KEYFRAMER_VITALS_READ_KEY | Optional: a Motion Vitals workspace read key (kfw_...) for field_problems and field_compare. Every other tool works without it. | Secret |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubKeyframer Inspector
A motion debugger for apps. Every animation, with the line of code that started it, what it cost, and why frames dropped, recorded on the device and scrubbed like a video. Tune a duration or a spring and write the numbers back to your source. Hand the recording to a coding agent over MCP, or gate pull requests on it in CI.
https://github.com/user-attachments/assets/81d909d3-64fb-431b-a06f-1d20da5d5952
This repository holds the SDKs that go into your app, for every platform, under MIT.
| Platform | Folder | Install |
|---|---|---|
| React Native (Reanimated) | react-native/ |
npm i -D @keyframerdev/inspector |
| iOS (UIKit) | ios/ |
Swift Package Manager: https://github.com/keyframer-dev/inspector |
| Android (Views) | android/ |
debugImplementation("dev.keyframer:keyframer-inspector:<version>") |
| Flutter | flutter/ |
flutter pub add keyframer_inspector |
The apps connect to Keyframer Inspector, the desktop app (below). React Native apps can also use the panel inside Expo's dev tools, no desktop app needed.
Quick start
React Native. Add the Babel plugin in development (before react-native-worklets/plugin), connect,
then press shift+m in Metro and open @keyframerdev/inspector. The
npm README has the details, bare React Native
included, and react-native/example is an Expo app with it all set up.
// babel.config.js (Expo)
plugins: process.env.NODE_ENV !== 'production' ? ['@keyframerdev/inspector/babel'] : []
// your root layout
if (__DEV__) require('@keyframerdev/inspector/devtools').connectDevTools({ app: 'MyApp' })
iOS.
import KeyframerInspector
#if DEBUG
KeyframerInspector.start() // simulator: ws://127.0.0.1:8790
KeyframerInspector.start(.init(host: "192.168.1.20")) // a device: the Mac's LAN address
#endif
Android.
// Application.onCreate (debuggable builds only)
Keyframer.start(this)
ObjectAnimator.ofFloat(title, View.ALPHA, 0f, 1f).kfTrack("title").start()
Flutter.
void main() => runApp(const KeyframerInspector(app: 'My app', appPackage: 'my_app', child: MyApp()));
Each folder's README covers the API, what is reported and how, and its tests.
The desktop app
Keyframer Inspector for macOS (Apple silicon and Intel) is where every SDK connects. Download it from Releases. It is free, signed and notarized, and keeps itself up to date.
-
Every platform, one place. iOS, Android, Flutter and React Native apps connect to it on
ws://<your Mac>:8790: simulators and emulators on their own, devices on the same network with the address the status bar shows. Several apps at once, with a switcher. -
The panel. Record, then drag to scrub: the app follows, back to the screen it was on. Tracks show every animation as segments you can click to tune (duration, delay, spring) live, then apply the numbers to your source. Problems come ranked by the frames they cost, each with where it is, what was running and the fix. Compare two sessions, before and after a change. Open any step in Cursor, VS Code, Zed or Xcode.
-
An MCP server for coding agents. Built in, one switch in Settings, and nothing else to install. Claude Code, Codex, Cursor, VS Code, Windsurf, Zed and Claude Desktop can record your app, run its scenarios, read the trace and the problems, and take screenshots. With
checkandrecheckan agent runs the fix loop: measure, change the code, measure again, until the problems are gone and the motion still works. Settings shows the setup for each client; for Claude Code:claude mcp add --transport http keyframer-inspector http://127.0.0.1:8789/mcp -
A recordings library. Recordings (
.kfrec.json) from the panel, from testers' devices or from share links land in one folder. Double-click one to open it; share links open in the app. -
In the menu bar. Closing the window keeps the relay running. The menu shows the connected apps and the MCP server, with switches for the server and for launching at login.
-
Updates on its own. It checks after launch and every six hours, downloads in the background and installs when you restart or quit. Every update is signed, and the app installs nothing else.
-
Local. Recordings, the relay and the MCP server stay on your Mac. Nothing leaves it unless you make a share link.
Protocol
Every SDK speaks one wire protocol, protocol/inspector.ts: hello, the
signals an app exposes, animation events with their call sites, frames, screens, recordings, and what
an editor sends back (record, scrub, overrides, scenarios). A new platform needs only to speak it.
Issues and contributions
Issues for any platform, the desktop app and the npm package go here. This repository is published from Keyframer's own; pull requests are welcome, and land here once merged there.
License
MIT for everything in this repository (LICENSE). The desktop app is free and closed
source. In the npm package, what runs in your app is MIT (its source is react-native/), and the tools
(the CLI, the MCP server and the panel) are under the Functional Source License; see its
LICENSE.md.
Keyframer Inspector MCP questions
How do I add Keyframer Inspector MCP to Claude Code?
Run claude mcp add --env 'KEYFRAMER_VITALS_READ_KEY=<YOUR_KEYFRAMER_VITALS_READ_KEY>' inspector -- npx -y @keyframerdev/inspector in your terminal. Add --scope user to make it available in every project.
How do I add Keyframer Inspector MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can the agent automatically fix animation issues?
Yes, using the check and recheck commands, an agent can run a fix loop by measuring, changing code, and measuring again until problems are resolved.
Is the data sent to the cloud?
No, recordings, the relay, and the MCP server remain local to your Mac unless you explicitly create a share link.