Connect Claude Code

This registers an app as an MCP server in Claude Code. Each app hands you the command rather than running it, so a failure lands in your terminal where you can see it.

You need:

Agent Access turned on in the app you are connecting.
The claude CLI installed.

Steps

Open the app’s Agent Access settings. In Cask Film that is Settings > General > Agent Access, then Connect Agent and Claude Code. In Cask Flow it is Settings > Agent access, then the Claude Code row.
Click Copy (Cask Film) or Copy command (Cask Flow).
Paste it into a terminal and run it.

The command looks like this for Cask Film:

claude mcp add -s user cask-studio "/Applications/Cask Studio.app/Contents/MacOS/cask-mcp"

And like this for Cask Flow:

claude mcp add -s user cask-motion "/Applications/Cask Flow.app/Contents/MacOS/cask-mcp"

Copy the command from Settings rather than from here. It names the path of the copy you are actually running, which may not be the one in /Applications.

Run both to drive both apps from one Claude Code session. The two server names do not collide.

Why -s user matters

claude mcp add defaults to local scope, which registers the server for the current working directory only.

Drop the -s user and the command still reports success. The server then works in whichever directory you happened to run it in, and is missing from every other project. That failure is quiet and looks nothing like a configuration mistake.

-s user registers it for your user account, so it is present in every project on this Mac.

Result

claude mcp list shows cask-studio, cask-motion, or both. In a new Claude Code session, /mcp lists them and the tools are available.

Each app reads Claude Code’s config back, so its client list shows Claude Code as connected once the command has run. Removing the entry by hand makes it stop showing.

Connect once. The registration survives app restarts, app upgrades, and Agent Access being switched off and back on.

Reduce the approval prompts

Claude Code auto-allows read-only tools and asks about the rest. To allow a whole server, add this to ~/.claude/settings.json:

{ "permissions": { "allow": ["mcp__cask-studio", "mcp__cask-motion"] } }

Consider what that means before you do it. It covers the tools that spend your credits and the ones that delete things.

If it doesn’t work

Symptom	Cause	Fix
The server works in one project and is missing in others	You ran the command without `-s user`, so it registered at `local` scope	Remove it and run the command again with `-s user`
`command not found: claude`	The Claude Code CLI is not installed or not on your `PATH`	Install it, then run the command again
The server is listed but the tool list is empty	The app is closed, or Agent Access is off	Open the app and check the switch. The tools appear within a few seconds, with no need to restart Claude Code
Every tool call fails saying the app is closed	Same as above	As above
Tools appear but writes are refused	The open project refuses writes	See Fix an agent connection