Factory

Add Cakewalk's MCP Gateway to Factory's Droid CLI with one droid mcp add command. OAuth runs through the interactive /mcp manager.

Factory's Droid CLI uses droid mcp add to register MCP servers. One command points Droid at the Cakewalk gateway. OAuth runs through the in-session /mcp interactive manager on first connection.

Install Method

CLI command. Droid stores the server config in ~/.factory/mcp.json (user scope) or .factory/mcp.json in the project root (project scope, shared via Git).

Step 1: Run droid mcp add

In your terminal, run:

droid mcp add cakewalk https://mcp-gateway.getcakewalk.io/mcp --type http

Running this command from outside a project directory typically registers at user scope. Running it from inside a project (where .factory/mcp.json exists or is created) registers at project scope and can be shared with your team via Git.

Step 2: Authenticate

Start a Droid session and run:

/mcp

Droid opens the interactive MCP manager. Select the cakewalk server, follow the browser prompt to authenticate with your Cakewalk account and approve the Connection.

Verifying It Works

In a Droid session, run /mcp to open the manager. The cakewalk server appears with its connection status and the tools it exposes. In Cakewalk, the Factory card on My Agents flips to Connected after the first agent call.

Troubleshooting

• Server missing from /mcp: confirm the scope. A server added at one project's .factory/mcp.json does not appear in another. Re-run droid mcp add from the right directory, or add at user scope with no .factory/mcp.json present in the current directory.
• OAuth browser prompt does not appear: open /mcp in Droid and trigger the authentication flow from the interactive manager directly.

Other Install Paths

You can skip the CLI and edit ~/.factory/mcp.json (user) or .factory/mcp.json (project) directly. The CLI command above produces the same effect; manual edit is the alternative for teams managing config in source control.

Learn more

• MCP configuration in Droid from Factory.