Skip to main content

Connecting Redbooth to Your AI Assistant

Redbooth's MCP server lets an AI assistant work directly with your live Redbooth data. Once connected, your assistant can read your tasks, task lists, tags, comments, files, and team members – and act on them by creating tasks, updating statuses, leaving comments, or summarizing a workspace.

MCP (Model Context Protocol) is an open standard, not a Claude-only integration, so any MCP-compatible assistant can connect: Claude, ChatGPT, Perplexity, Mistral (Le Chat), Copilot Studio, Gemini Enterprise, WarpAI, and others.

Setup takes about a minute for most assistants. Copilot Studio and Gemini Enterprise need a few extra OAuth steps, which are covered below.

Before you start

  • You need a Redbooth account you can sign in to. The connection is authorized against your own account, so your assistant works with the workspaces you already have access to.
  • You need an AI assistant that supports custom MCP connectors. Support varies by product and, in some cases, by plan – check your assistant's documentation if you don't see a connector option.
  • You need a Redbooth Pro, Business or Enterprise plan.

Step 1: Copy the MCP server URL

Every MCP-compatible assistant needs the same two things: a name for the connector, and the server URL.

  • Name: Redbooth
  • Remote MCP server URL: https://redbooth.com/api/mcp

Step 2: Add Redbooth to your assistant

How you add Redbooth depends on how you use your AI assistant. Follow the section that applies to you.

If you're a member of a team or company account

On team and company plans of AI assistants (for example, Claude Team or Enterprise, or ChatGPT Business or Enterprise), only an owner or admin can add custom connectors. Once they add Redbooth, each member connects their own Redbooth account. If you try to add a custom connector yourself, you'll see a message like "Ask an organization owner to add this for your team."

  1. Check whether Redbooth has already been added. In Claude, go to Customize → Connectors and search for Redbooth. In other assistants, look in the connector settings for a Redbooth connector your organization has already set up.
  2. If Redbooth is listed, click it and select Connect, then continue to Step 3 to authorize your Redbooth account. You don't need to add the URL yourself.
  3. If Redbooth isn't listed, ask an owner or admin of your AI assistant account to add it as a custom connector using the name and URL from Step 1. Once they've added it, it will appear in your connector list and you can connect as described above.

If you use a personal account, or you're an owner or admin

Add Redbooth as a custom connector using the steps for your assistant below. The setting is usually called Connectors, Custom connector, MCP server, or Add integration.

Owners and admins: adding Redbooth once makes it available to everyone in your organization. Each member then connects their own Redbooth account from their connector list.

Claude

  1. Open Claude.ai and go to Customize → Connectors.
  2. Click + Add, then select Add custom connector.
  3. Enter the name and the URL above.
  4. Click Add.

ChatGPT

  1. Go to Settings → Connectors → Add custom connector.
  2. Enter the name and the URL above.

Perplexity

  1. Open Perplexity's connector settings.
  2. Add a custom MCP connector using the name and the URL above.

Mistral (Le Chat)

  1. Open Le Chat's tools/connectors settings.
  2. Add an MCP connector pointing to the URL above.

Copilot Studio

Copilot Studio's automatic setup doesn't always work with Redbooth, so set up OAuth manually:

  1. Open your Redbooth MCP connector and go to the 2. Security tab.
  2. Under Authentication Type, select OAuth 2.0 and fill in:
    • Authorization URL: https://redbooth.com/oauth2/authorize
    • Token URL: https://redbooth.com/oauth2/token
    • Refresh URL: https://redbooth.com/oauth2/token
    • Scope: all
  3. Copy the Redirect URL shown on that tab.
  4. In a new tab, go to https://redbooth.com/oauth2/applications and click Register A New App. Name it (for example, Copilot Studio Connector) and paste the Redirect URL into Return URI. Tick Supports 2FA if your Redbooth account uses two-factor authentication, then click Submit.
  5. Copy the Client ID and Client Secret into the OAuth 2.0 form and click Update connector.
  6. Go to the 5. Test tab, click New connection, and authorize access to your Redbooth account.
  7. Add the Redbooth connector as a tool to a new or existing agent.

Gemini Enterprise

  1. On the Gemini Enterprise home screen, click Add MCP server. Admins can also add one from the Google Cloud console.
  2. Fill in:
    • MCP Server URL: https://redbooth.com/api/mcp
    • Authorization URL: https://redbooth.com/oauth2/authorize
    • Token URL: https://redbooth.com/oauth2/token
    • Scopes: all
  3. In a new tab, go to https://redbooth.com/oauth2/applications and click Register A New App. Name it (for example, Gemini Enterprise Connector) and set Return URI to https://vertexaisearch.cloud.google.com/oauth-redirect. Tick Supports 2FA if your Redbooth account uses two-factor authentication, then click Submit.
  4. Copy the Client ID and Client Secret into the Gemini form and click Add.
  5. In the chat box, click the connectors (puzzle-piece) icon, find Redbooth, and click Connect. Sign in to Redbooth to finish.

WarpAI

  1. Open Warp's MCP configuration.
  2. Add an MCP server entry pointing to the URL above.

Any other MCP client

Look for a Custom connector, MCP server, or Add integration option in the assistant's settings and paste in the same URL.

Step 3: Authorize the connection

After you add the connector, your assistant will prompt you to authorize access to your Redbooth account. Approve the prompt to finish setup.

That's it – you can now ask about your tasks, workspaces, and team directly in conversation, with no separate app or context-switching.

Step 4: Confirm it's working

Ask your assistant a simple read-only question, such as:

"List my Redbooth workspaces."

If you get back your actual workspace names, the connection is live. If the assistant says it has no access or doesn't mention Redbooth at all, see Troubleshooting below.

What your assistant can do

The connection is read and write, which is what makes it more useful than a dashboard.

Read: tasks, task lists, tags, comments, files, and workspace members.

Write: create tasks and subtasks, update task details and status, and leave comments.

Because writes are possible, review what your assistant proposes before confirming – especially when it's creating tasks in bulk from pasted notes.

Example prompts

These are patterns teams use most often. Copy them as-is or adapt the workspace and team names.

Plan your week

"Show me this week's outlook in terms of tasks I need to work on."

Many assistants will render a visual summary – overdue counts, a day-by-day board, urgent items flagged – built from your live task data rather than a fixed report template.

Check team bandwidth before assigning work

"Who on the design team has the lightest task load this week?"

Cross-references workspace members against their open task counts and due dates, so you get a ranked answer instead of a list you'd have to sort yourself.

Find blockers hiding in comments

"Scan comments in the Q3 Launch workspace for anything that sounds blocked or waiting on someone."

Blockers usually live in a comment thread rather than a status field. Your assistant can surface comments containing phrases like "waiting on," "need approval," or "stuck on," with the original comment attached so you can verify it.

Draft a client status update

"Turn the current state of the Acme Corp workspace into a two-paragraph update I can send the client."

Reads what's done, in progress, and upcoming, then drafts client-facing prose instead of a raw task dump. This works best in workspaces that were already structured to be client-readable.

Turn meeting notes into tasks

"Here are my notes from the kickoff call – create tasks for each action item under the right owner."

Paste in raw notes or an email thread. A good assistant will create the tasks with subtasks where the notes call for a checklist, and flag any action item that doesn't name an owner rather than guessing one.

Build a weekly rollup across every workspace

"Give me a weekly outlook: what got completed, what's at risk, and what's new across all my workspaces."

Spans all your workspaces at once, which no single workspace view can do.

Triage by tag across the organization

"Show me every task tagged 'urgent' that's still open, across the whole organization."

Tags are workspace-scoped in the Redbooth UI, so an org-wide tag view normally means opening each project individually. Your assistant can roll them up in one pass.

Troubleshooting

The connector option isn't in my assistant's settings. Not every assistant supports custom MCP connectors, and some gate the feature behind specific plans. Check your assistant's own documentation for MCP or custom connector support.

I see "Ask an organization owner to add this for your team." Your AI assistant account is managed by your organization, so only an owner or admin can add custom connectors. Search your connector list for Redbooth first – it may already be added, in which case you just need to click Connect. If it isn't there, ask an owner or admin to add it. See If you're a member of a team or company account above.

I added the connector but was never asked to authorize. Open the connector's settings in your assistant and look for a Connect, Authorize, or Sign in action. Some assistants only trigger the prompt the first time you ask a Redbooth question.

Gemini Enterprise shows "Failed to obtain refresh token." Make sure Scopes is set to all and the Return URI in your Redbooth app is exactly https://vertexaisearch.cloud.google.com/oauth-redirect.

My assistant can't find a workspace I know exists. The connection uses your own Redbooth account, so your assistant can only see workspaces you're a member of. Confirm you can open the workspace in Redbooth yourself.

The connection worked before and now doesn't. Authorization can expire or be revoked. Remove the connector and add it again, then re-authorize.

Double-check the URL. It must be exactly https://redbooth.com/api/mcp, including https://.

Frequently Asked Questions

Does Redbooth's MCP server only work with Claude?
No. MCP is an open standard, not an Anthropic-exclusive one – OpenAI, Google, Microsoft, and Salesforce all shipped their own MCP support within 13 months of the protocol's launch. Redbooth's MCP server works with any MCP-compatible assistant, including Claude, ChatGPT, Perplexity, Mistral, Copilot Studio, Gemini Enterprise, and WarpAI, using the same server URL.

Do I need to buy an add-on to use Redbooth's MCP server?
No. The MCP server is included in the Pro, Business and Enterprise plans at no extra cost, so there's no separate add-on to purchase. Once you're on one of these plans, all you need to do is authorize the connection in your assistant. Copilot Studio and Gemini Enterprise also need a Redbooth OAuth app registered first, as described in their setup steps above. The MCP server isn't available on the Free plan.

Can my AI assistant create and edit tasks, or only look them up?
Both. The MCP server exposes read access (tasks, comments, files, workspace activity, members) and write access (creating tasks and subtasks, updating task status, adding comments and tags). Whether your assistant uses the write access depends on how you phrase the request – asking it to summarize is read-only; asking it to create tasks from meeting notes uses the write path.

Is my Redbooth data secure when an AI assistant is connected?
The connection is authorized per user, the same way any OAuth-based integration works – you grant access explicitly when you add the connector, and the assistant only sees what your Redbooth account already has permission to see. No workspace data is used to train Redbooth or shared with a third party as part of the connection itself.

Related articles