Installation
Invoker runs as an MCP server over stdio. You can add it to Claude Desktop, Claude Code, or run it manually.
Prerequisites
- Node.js 18+ -- Invoker uses
npxto run without a global install.
Verify your Node version:
node --version
# v18.0.0 or higherClaude Desktop
Add Invoker to your Claude Desktop MCP config. Open claude_desktop_config.json and add the invoker entry under mcpServers:
// ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"invoker": {
"command": "npx",
"args": ["-y", "invoker-mcp"]
}
}
}// %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"invoker": {
"command": "npx",
"args": ["-y", "invoker-mcp"]
}
}
}After saving, restart Claude Desktop. You should see Invoker listed in the MCP tools panel.
Claude Code
Add a .mcp.json file to the root of your project:
// .mcp.json
{
"mcpServers": {
"invoker": {
"command": "npx",
"args": ["-y", "invoker-mcp"]
}
}
}Claude Code picks this up automatically when you open the project.
Project-level vs global
Placing .mcp.json in your project root scopes Invoker to that project. You can also add it to ~/.claude/.mcp.json to make it available in every project.
Manual / other MCP clients
Run the server directly over stdio:
npx -y invoker-mcpThis starts the MCP server on stdin/stdout using the standard stdio transport. Point any MCP-compatible client at this command.
Verifying the installation
Once installed, open a Claude conversation and ask:
"What Invoker tools do you have available?"
Claude should list the Invoker tools: deploy, login, list_templates, get_submissions, and others. If you see them, you are ready to go.
Tools not showing up?
- Make sure you restarted Claude Desktop after editing the config
- Check that
npx -y invoker-mcpruns without errors in your terminal - Confirm Node.js 18+ is installed and on your
PATH
Next step
Authentication -- sign in to start deploying.