Rowbrief

com.inkcroftPublished by inkcroft.comOfficial publisherv0.1.0Updated Oct 24, 2026

One project plan that you, your team and each of your AIs read and write.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Rowbrief is a remote MCP server for a shared project plan that you, your team and your AIs can read and write.

What you can do
Provides a shared project plan as a common workspace for a person, their team and their AI assistants, with both reading and writing access. No individual tools are listed in the supplied material, so the exact operations are not documented here.
When to use it
Consider it when several people and their AI assistants need to work from one shared project plan instead of separate copies.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. Authentication is required and uses OAuth; no environment variables or headers are declared.
Before you install
The plan is writable, so an assistant can change shared content that your team relies on. Access is granted through OAuth to a hosted third-party service, so project data is stored with that provider.

Installation

In SourceWeft

  1. Open Rowbrief 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.inkcroft%2Frowbrief/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": {
    "rowbrief": {
      "type": "http",
      "url": "https://rowbrief.inkcroft.com/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.0LatestOct 24, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.