Connect an AI app

The Workilo connector lets you use Workilo from your AI app: Claude, OpenAI Codex, ChatGPT, Cursor, VS Code with GitHub Copilot, Gemini CLI, or any app that supports MCP. Your AI app reads a client's brand context, writes in that client's voice and saves the result to Workilo. You review it there.

The Workilo connector is in private beta. Ask support@workilo.io to join.

What a connected AI app can and can't do

With Workilo connected, your AI app can:

  • Read your clients, their brand context, content pieces, media and workflows.
  • Save drafts. Posts, articles and Reel scripts land in the Queue as Needs review. The app can suggest a date and attach media, but nothing is scheduled until you approve it.
  • Plan. The app can add planned items to the content calendar. They sit on the calendar and board, not in the Queue, until someone fills them in.
  • Attach media from the client's library and render brand cards on the client's brand template. Cards are drawn from the template, not generated by AI.
  • Edit a draft that has not been approved yet.

Connected AI apps can never approve, schedule or publish. Pieces wait in your Queue. The connector has no tool to delete pieces, clients or media, or to change brand settings. Once a piece is approved, scheduled or published, your AI app can no longer edit it. Changes after that happen in Workilo.

Connect your AI app

You connect once per app. Use this as the MCP server URL:

https://mcp.workilo.io/mcp

Pick your app below. Apps that support MCP sign-in open Workilo in your browser, where you sign in and click Allow. On the consent page the app shows with the access it is asking for and where your data goes. You can switch off optional access. Brand context is always on because the connector needs it. If you switch off creating and editing drafts, the app can't save to Workilo.

Claude

claude.ai, Claude Desktop and Cowork.

  1. In Claude, open Customize → Connectors.
  2. Click + Add, then Add custom connector.
  3. Enter a name, like Workilo, and paste the Workilo MCP URL above as the MCP server URL. Click Continue.
  4. Claude checks the server, then opens Workilo in your browser.
  5. Sign in if asked, check what Claude can do, and click Allow.

Claude Code

The Claude Code command line.

claude mcp add --transport http workilo https://mcp.workilo.io/mcp
  1. Run the command.
  2. In Claude Code, type /mcp, choose workilo and pick Authenticate.
  3. Workilo opens in your browser. Sign in if asked and click Allow.

With a connector key instead of a browser sign-in:

claude mcp add --transport http workilo https://mcp.workilo.io/mcp --header 'Authorization: Bearer ${WORKILO_MCP_KEY}'

The command keeps ${WORKILO_MCP_KEY} in single quotes, so Claude Code saves the placeholder and fills it in from your environment at startup.

OpenAI Codex

The Codex CLI, plus the Codex IDE extension and desktop app.

codex mcp add workilo --url https://mcp.workilo.io/mcp
codex mcp login workilo
  1. Run both commands. The second one opens Workilo in your browser.
  2. Sign in if asked, check the access and click Allow within a few minutes.

With a connector key instead of a browser sign-in:

codex mcp add workilo --url https://mcp.workilo.io/mcp --bearer-token-env-var WORKILO_MCP_KEY

Codex reads the key from WORKILO_MCP_KEY when it starts. If you use the IDE extension or desktop app, start it from a shell that has the variable set.

The Codex CLI is the tested route. The IDE extension and desktop app use the same ~/.codex/config.toml, where the command adds a [mcp_servers.workilo] entry you can also edit by hand.

Codex can keep connected tools out of sight until it searches for them. If it says it can’t see Workilo, ask it to search its tools for Workilo, for example: “Search your tools for Workilo and list my clients.”

ChatGPT

Custom connectors in the ChatGPT web and desktop apps.

Not tested yet. We have not connected this app to Workilo in a live account yet. If a step does not match what you see, email support@workilo.io.

  1. In ChatGPT settings, open Plugins (it used to be called Apps and Connectors) and turn on Developer mode under Advanced.
  2. Choose Add custom MCP server (older versions say Add a custom connector) and paste the Workilo MCP URL as the server URL.
  3. Choose OAuth as the authentication and accept the notice about custom servers.
  4. Sign in to Workilo if asked, check the access and click Allow.

Custom servers are not available on every ChatGPT plan, and ChatGPT’s menus change, so look for the same names if a label has moved.

Cursor

The Cursor editor.

Not tested yet. We have not connected this app to Workilo in a live account yet. If a step does not match what you see, email support@workilo.io.

{
  "mcpServers": {
    "workilo": {
      "url": "https://mcp.workilo.io/mcp"
    }
  }
}
  1. Add the config to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
  2. Open Cursor’s MCP settings and connect workilo.
  3. Workilo opens in your browser. Sign in if asked and click Allow.

With a connector key instead of a browser sign-in:

{
  "mcpServers": {
    "workilo": {
      "url": "https://mcp.workilo.io/mcp",
      "headers": {
        "Authorization": "Bearer ${env:WORKILO_MCP_KEY}"
      }
    }
  }
}

Cursor fills in ${env:WORKILO_MCP_KEY} from your environment, so the key itself is never in the file.

VS Code (GitHub Copilot)

VS Code with Copilot agent mode.

Not tested yet. We have not connected this app to Workilo in a live account yet. If a step does not match what you see, email support@workilo.io.

{
  "servers": {
    "workilo": {
      "type": "http",
      "url": "https://mcp.workilo.io/mcp"
    }
  }
}
  1. Add the config to .vscode/mcp.json, or run MCP: Add Server from the command palette and choose HTTP.
  2. Start the workilo server from the file or the MCP: List Servers command.
  3. Workilo opens in your browser. Sign in if asked and click Allow.

With a connector key instead of a browser sign-in:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "workilo-key",
      "description": "Workilo connector key",
      "password": true
    }
  ],
  "servers": {
    "workilo": {
      "type": "http",
      "url": "https://mcp.workilo.io/mcp",
      "headers": {
        "Authorization": "Bearer ${input:workilo-key}"
      }
    }
  }
}

VS Code asks for the key when the server starts and keeps it out of the file.

Your organization can turn off MCP servers for Copilot. If the server does not show up, ask your admin.

Gemini CLI

The Gemini command line.

Not tested yet. We have not connected this app to Workilo in a live account yet. If a step does not match what you see, email support@workilo.io.

gemini mcp add --scope user --transport http workilo https://mcp.workilo.io/mcp
  1. Run the command.
  2. In a Gemini CLI session, run /mcp auth workilo.
  3. Workilo opens in your browser. Sign in if asked and click Allow.

With a connector key instead of a browser sign-in:

{
  "mcpServers": {
    "workilo": {
      "httpUrl": "https://mcp.workilo.io/mcp",
      "headers": {
        "Authorization": "Bearer <your connector key>"
      }
    }
  }
}

Put this in ~/.gemini/settings.json and paste your key in place of the placeholder. Gemini CLI’s docs only show a literal key in headers, so keep the file out of git.

Other

Any app that supports MCP over HTTP.

  1. Add a remote (HTTP) MCP server and paste the Workilo MCP URL.
  2. Apps that support MCP sign-in find Workilo’s OAuth settings on their own. Sign in and click Allow.

With a connector key instead of a browser sign-in:

Authorization: Bearer <your connector key>

If your app has no MCP sign-in, send this header with every request. Keep the key in a secrets manager.

Connector keys

For scripts, CI or a machine with no browser, use a connector key instead of signing in:

  1. In Workilo, open Profile → AI connectors and find Connector keys.
  2. Click New key, name it and pick what it can do. Expiry choices are 30 days, 90 days, 1 year, Never.
  3. Copy the key now. Workilo shows it once, and it starts with gsk_.
  4. Put it in an environment variable called WORKILO_MCP_KEY, then use the key setup shown for your app above.

Never commit a config file with the key in it. A key only works on the Workilo connector, not the rest of the Workilo API.

Use it in Claude day to day

These tips are for Claude. Other apps have their own menus.

  • Turn it on in a chat. Click +, then Connectors, and switch Workilo on.
  • Approve each tool. Claude's connector settings list Workilo's tools in two groups, Read-only tools and Write/delete tools, each set to Needs approval by default. In a chat you see "Claude wants to use a tool from Workilo" with the arguments, and choose Decline, Allow once or Always allow. Claude labels this group Write/delete tools for every connector. Workilo has no delete tool, so Claude can't delete pieces.
  • Start from a Workilo prompt. Click +, then Connectors, then Add from Workilo. You get the Social Media Campaign, Enhanced Article Creation and Thread Master workflows, plus any custom workflows you have built. In Claude Code they appear as /workilo:social-media-campaign and so on. A prompt asks for a client by name or ID, and for any workflow inputs it needs.
  • Pick the client. Claude works on the clients you are a member of. A Workilo prompt asks for one client by name or ID, and you can ask Claude to switch to a different client at any time.
  • Find the result. Open the Queue and look under Needs review. Approve, schedule and publish there. Planned items are on the calendar.

The tools your AI app sees:

Read-only tools Write/delete tools
Get brand context Create content piece for review
Get client details Edit content piece draft
Get content piece Attach media to content piece
Get workflow runbook Add planned items to the content calendar
List client media Render brand card (template, no AI)
List Workilo clients
List content pieces
List Workilo workflows

Ask your AI app to list your Workilo workflows to see which ones it can run.

Manage access

Open Profile → AI connectors.

  • Active connections lists each app you have approved, with its permissions, when it connected and when it was last used.
  • Revoke a connection and confirm. The app loses access on its next request. In Claude, it then says Workilo needs you to sign in again and offers Reconnect. Click it, then Allow.
  • Two entries with the same name usually mean you signed in twice. Each sign-in is its own connection, so revoking the one you aren't using doesn't affect the other.
  • Connector keys are revoked with Revoke, then a second Revoke to confirm. Anything using the key stops working, and the key shows a Revoked or expired badge.

Your data

Workilo stores your brand context, clients, drafts and media in Toronto. Once you connect, whatever a Workilo tool returns goes to the AI app you connect and is processed by that app’s provider under your terms with them.

In Claude: Workilo stores your brand context, clients, drafts and media in Toronto. Once you connect, anything a Workilo tool returns goes to your Claude app and is processed by Anthropic (United States) under your Claude terms.

See the per-provider routing.

Troubleshooting

Your AI app says Workilo needs you to sign in again. The connection was revoked or has expired. Connect again from your app, then click Allow. In Claude, click Reconnect on the card. In Claude Code, type /mcp, choose workilo and pick Authenticate.

The consent page says the link is invalid, expired or already used. The link expires after a few minutes and works once. Go back to your AI app and start the connection again. If it says the approval started in a different browser, finish it in the browser you started from.

Your AI app can't find a client. It only sees clients you are a member of. Ask it to list your Workilo clients and use a name from that list. If two clients share a name, give the client ID.

Your AI app can see a client but can't edit it. You have view access only. Ask the workspace owner for edit access.

Your AI app won't edit a piece. The piece is approved, scheduled or published. Edit it in Workilo, or move it back to review first.

Your connector key says it doesn't include a permission. A key's permissions are fixed when you create it. Create a new key with the permission, update WORKILO_MCP_KEY and restart your AI app.

Your app can't connect, or asks for a client ID. Use the MCP URL above and choose OAuth if the app offers a choice. If it has no MCP sign-in, use a connector key.

The connector says your trial has ended, a payment failed or your email isn't verified. Fix that in Workilo, then ask your AI app again. See plans and billing.

Your AI app says it hit a limit. Wait a few minutes and try again.

Still stuck? Contact support.

Spin up your digital crew today

No code. No waiting. Just Workilo.

14-day free trial · No credit card required · Cancel anytime, or book a demo for a 30-day trial