MCP

The MCP server exposes BeHooked generation as tools an AI client can call. The model picks the app and parameters; you approve the run.

Generations cost real credits

An MCP client spends the same balance as the dashboard. Tool approval dialogs show the tool and its arguments — not always the price. Ask for a cost estimate before approving a batch.

Setup

1. Create an API key in the dashboard under Profile → API keys. Copy it now; it is shown once.

2. Add the server to your client config. For Claude Desktop, edit claude_desktop_config.json:

   claude_desktop_config.json

   {
     "mcpServers": {
       "behooked": {
         "command": "npx",
         "args": ["-y", "@behooked/mcp-server"],
         "env": {
           "BEHOOKED_API_KEY": "YOUR_API_KEY_HERE"
         }
       }
     }
   }

   Config file locations:

   # macOS
   ~/Library/Application Support/Claude/claude_desktop_config.json
   
   # Windows
   %APPDATA%\Claude\claude_desktop_config.json

3. Restart the client fully. Not a window close — quit and reopen. The config is read once at launch.

4. Verify. Ask the client to list available BeHooked apps. A list means the server is connected.

Troubleshooting

Server does not appear after restart. Almost always invalid JSON — a trailing comma or an unescaped Windows backslash. Validate the file before blaming the server.

Authentication failed. Key wrong, revoked, or carrying whitespace from the copy. Re-paste it.

npx not found. Node is not on the launcher’s PATH. GUI apps do not inherit a shell profile, so a PATH set in .zshrc is invisible here — use an absolute path to npx.

Tools listed but every call fails. Check the balance first. A zero balance fails at call time, not at connection time.