Skip to main content
Connect the GooseWorks MCP server to Claude, ChatGPT, Claude Code, Cursor, Codex, or another compatible client. Your agent can use your GooseWorks brands, campaigns, creatives, files, and tools from that client.

​
What is MCP?

MCP (Model Context Protocol) lets an AI app discover and call tools. The GooseWorks server gives your AI app access to your GooseWorks account. The CLI can configure that connection and install local skill instructions.

​
GooseWorks MCP server

  • URL: https://mcp.gooseworks.ai/mcp
  • Transport: Streamable HTTP
  • Authentication: OAuth where supported, or Authorization: Bearer <your-access-token>
Choose the setup that matches your client: Use credentials and server URLs from the same environment. A staging token should connect to the staging MCP server, not the production URL above.

​
Available tools

The Goose Growth tools reference is generated from the server source. Your client’s current tool list is the authority for what its deployed connection supports; a docs release and server release can arrive at different times. Older guides and clients may use names such as search_skills or submit_remix_batch. Compatibility aliases exist, but new integrations should use the canonical names advertised by their connection. See Ad Remixer MCP for creative generation, campaign planning, credit approval, and the Meta publishing boundary.

​
One-time setup with the CLI

Paste this into your coding agent — Claude Code, Cursor, or Codex — and let it run the install:
The agent runs the install and can print the sign-in URL if no browser opens. Restart your agent when installation finishes so it loads the MCP connection. After restarting, account_whoami verifies access through that connection. No special onboarding command is required. For a manual terminal install:
Keep --mcp on agent-specific installs. --all already includes it. Restart your coding agent after setup so it loads the connection, then ask it to call account_whoami to confirm access.

​
Manual setup (without the CLI)

​
Step 1 — Create an MCP access token

  1. Open Settings → CLI & MCP and expand Manual setup.
  2. Click Create MCP access token. The token has the mcp:access scope and belongs to your user account.
  3. Copy it immediately. The complete token is shown only once.
The token authenticates your client. It does not bypass organization membership, credit requirements, or approvals. For paid generation, your account also needs a default workspace in the intended organization.

​
Step 2 — Add to your MCP client

For Cursor, use ~/.cursor/mcp.json. For Claude Code, use the MCP configuration in ~/.claude.json. Merge the server entry into any existing configuration rather than replacing your other servers.
For Codex, use the CLI setup above to configure its TOML settings. Clients that present a token field should receive the MCP access token in that field, following their connection guide.

​
Step 3 — Restart your editor

Restart your client, then ask GooseWorks which account is connected. It should call account_whoami. Check the organization before starting work.

​
Rotating or revoking

  • Rotate: create a new MCP access token, update each client using the old token, verify the connection, then revoke the old token.
  • Revoke: open Settings → CLI & MCP → Manual setup → Your MCP access tokens, click the token’s trash icon, and confirm. Clients using that token lose access.

​
Adding your own custom MCP servers

Connecting GooseWorks to an external AI app is different from connecting external services to your GooseWorks coworker. Manage the latter through Connections in the web app, using the integrations available to your account.