Redbooth

com.redboothPublished by redbooth.comOfficial publisherv0.2.1Updated Oct 30, 2026

Manage Redbooth tasks, task lists, comments, tags and files from Claude and other AI assistants.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote Redbooth MCP server that lets an AI assistant manage tasks, task lists, comments, tags and files in a Redbooth workspace.

What you can do
  • Manage tasks and task lists in Redbooth
  • Add and read comments on tasks
  • Organize work with tags
  • Access files attached to Redbooth items
  • No tool list is published, so exact operations are not documented
When to use it
Useful when your team tracks work in Redbooth and you want an assistant to look up, update or comment on tasks without switching apps. Best suited to users who already have a Redbooth account and want project updates handled conversationally.
Requirements
A Redbooth account with OAuth authorization; the server is a hosted remote endpoint, so no local install is needed. Network access to the Redbooth service is required.
Before you install
OAuth grants the assistant access to your Redbooth workspace, and the server can change tasks, comments, tags and files, so review write actions before approving them. The published tool list is empty, so the exact scope of access is unclear.

Installation

In SourceWeft

  1. Open Redbooth in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.redbooth%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "redbooth": {
      "type": "http",
      "url": "https://redbooth.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.2.1LatestOct 30, 2026
  2. v0.2.0Oct 30, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.