MCP setup

Use GoForAgent with Claude, Cursor, and Codex today, then upgrade to MCP.

Copy a workflow handoff packet into your coding agent today. The future MCP package will automate the same tool contract through one GoForAgent account and shared credits.

Get API key Browse tools

future mcp.config.json

{
  "mcpServers": {
    "goforagent": {
      "command": "npx",
      "args": ["@goforagent/mcp@latest"],
      "env": {
        "GOFORAGENT_API_KEY": "gfa_xxx"
      }
    }
  }
}

`@goforagent/mcp` is the intended install contract, not a published dependency in this MVP. Use handoff packets first while the dashboard validates the mature tools.

Use today without MCP backend

Paste one handoff packet into the agent already working on the repo.

The current product path is copy-first: generate a packet in `/dashboard/workflows`, paste it into Codex, Cursor, or Claude, then use Image, Remove BG, and Video dashboard routes as mature tools.

Codex

Paste the packet as the next local coding-agent task. Codex can create files, update manifests, and report manual dashboard steps.

Paste the Codex handoff from /dashboard/workflows into this repo and follow the run order.

Cursor

Paste the packet into Cursor chat while the target project is open. Cursor can turn it into repo tasks and asset placeholders.

Use this Cursor handoff to plan assets under public/assets/goforagent and return the manifest.

Claude

Paste the packet into Claude Code or Claude Desktop with project context attached. Claude can keep the manifest synchronized.

Follow this Claude handoff, call mature tools manually today, and return paths plus follow-up.

Future MCP gateway

The same server shape should work across the main coding-agent clients once the package ships.

Claude Desktop / Claude Code

Add the GoForAgent MCP server to the local Claude config and expose scoped tool calls inside project sessions.

~/Library/Application Support/Claude/claude_desktop_config.json

Cursor

.cursor/mcp.json

Codex / local agents

Use the same command and API key in a local agent runtime that supports MCP server definitions.

~/.codex/mcp.json

When to automate

Build the gateway only after the copy-first workflow proves demand.

The MVP intentionally keeps MCP as a contract preview. GoForAgent should earn a backend worker when users repeatedly copy handoffs, open mature tools from workflows, and need credits or task status in one shared record.

Repeated pack usage

Users choose workflow packs and copy handoffs more often than they use isolated tools.

Manual steps bottleneck

The same users ask for automatic routing across Image, Remove BG, Video, and later Music or Speech.

Credits need one audit trail

Support and billing need to see which agent, pack, and tool consumed credits inside one workflow.

Task status matters

Users want one workflow job id, polling status, retries, and final manifest instead of separate dashboard runs.

Available tools

Start with a small registry that maps to existing za-one capabilities.

The first public registry stays narrow: three production dashboard tools plus broader catalog placeholders for the next MCP gateway phase.

agent_generate_image

Generate hero art, icons, product visuals, and landing page imagery.

/api/image/gpt-image-2-0/generate

dashboard live

agent_remove_background

Create transparent PNG assets from generated images, product photos, and portraits.

/api/image/remove-bg/generate

dashboard live

agent_generate_video

Generate short videos from prompts or reference images for launch and social assets.

/api/video/kling3/generate

dashboard live

agent_create_music

Create music tracks and audio ideas through the shared catalog.

/api/v1/audio/music

future gateway

agent_create_speech

Generate speech, voice, and narration assets for workflow packs.

/api/v1/audio/speech

future gateway

Agent calls

The runner now shows current handoffs and the future MCP request shape.

Use `/dashboard/workflows` today to copy a target-specific agent handoff, prompt, file manifest, or JSON preview. The later gateway can execute the same shape automatically.

Open workflow runner

Copy a full handoff

The current no-backend path: paste one target-specific packet into Codex, Cursor, Claude, or another local agent.

# GoForAgent workflow handoff

Target agent: Codex
Pack: Landing Page Asset Pack
Output folder: public/assets/goforagent/landing-page

Codex usage notes:
- Paste this packet as the next Codex task in the repo you want to update.
- Return repo-relative paths and a short verification note.

Project brief:
SaaS launch page for an AI meeting notes product

Run order:
1. Generate visual directions - agent_generate_image
2. Create transparent cutouts - agent_remove_background
3. Add launch motion - agent_generate_video

Acceptance checklist:
- Create or plan every file under the output folder.
- Return final file paths, status, and manual follow-up.

Create an asset pack

The high-level workflow tool the agent gateway should expose first.

{
  "tool": "agent_create_asset_pack",
  "arguments": {
    "pack": "landing-page",
    "brief": "SaaS launch page for an AI meeting notes product",
    "output_root": "public/assets/goforagent",
    "output_format": "asset_manifest",
    "tools": [
      "agent_generate_image",
      "agent_remove_background",
      "agent_generate_video"
    ],
    "expected_assets": [
      {
        "path": "public/assets/goforagent/landing-page/hero-16x9.webp",
        "type": "Hero image",
        "tool": "agent_generate_image"
      },
      {
        "path": "public/assets/goforagent/landing-page/product-cutout.png",
        "type": "Transparent PNG",
        "tool": "agent_remove_background"
      }
    ]
  }
}

Return a manifest

The response shape agents can use before file download, zip packaging, or repo writes.

{
  "pack": {
    "id": "landing-page",
    "title": "Landing Page Asset Pack"
  },
  "output_root": "public/assets/goforagent",
  "assets": [
    {
      "path": "public/assets/goforagent/landing-page/hero-16x9.webp",
      "type": "Hero image",
      "tool": "agent_generate_image",
      "status": "planned"
    },
    {
      "path": "public/assets/goforagent/landing-page/product-cutout.png",
      "type": "Transparent PNG",
      "tool": "agent_remove_background",
      "status": "planned"
    }
  ]
}

Generate one asset

The single-tool fallback for Claude, Cursor, Codex, and local agents.

{
  "tool": "agent_generate_image",
  "arguments": {
    "prompt": "Hero image for a practical AI developer tool landing page",
    "aspect_ratio": "16:9",
    "save_to": "public/images/hero.webp"
  }
}