rezee

app.rezeePublished by rezee.appOfficial publisherv0.1.0Updated Oct 27, 2026

Issues, pull requests, docs, chat and CI runs across a rezee workspace.

VerifiedStreamable HTTPWeb executableDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that gives an assistant access to issues, pull requests, docs, chat and CI runs across a rezee workspace.

What you can do
  • Work with issues and pull requests in a rezee workspace
  • Read and work with workspace documentation
  • Access team chat
  • Review CI run information
  • All of this is scoped to the connected rezee workspace
When to use it
Useful when your team keeps its issues, pull requests, docs, chat and CI runs in rezee and you want an assistant to reach that context without switching tools.
Requirements
A remote MCP endpoint at api.rezee.app over streamable HTTP. OAuth sign-in to a rezee account and workspace is required; no environment variables or headers are declared.
Before you install
Access is granted through OAuth to a whole workspace, so the assistant may see issues, pull requests, docs, chat and CI data for that workspace. The listed tools are not documented, so confirm whether any of them can write, comment or change data before relying on it.

Installation

In SourceWeft

  1. Open rezee 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/app.rezee%2Frezee/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": {
    "rezee": {
      "type": "http",
      "url": "https://api.rezee.app/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

1
  1. v0.1.0LatestSep 16, 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.