Brownpaper AI

ai.brownpaperPublished by brownpaper.aiOfficial publisherv1.0.0Updated Nov 5, 2026

Turn conversations about work processes into process maps: read, draw, correct and export.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Brownpaper AI turns conversations about work processes into process maps that an assistant can read, draw, correct and export.

What you can do
  • Read existing process maps from conversations about how work gets done.
  • Draw new process maps from a described workflow.
  • Correct process maps through follow-up conversation.
  • Export the resulting process maps.
When to use it
Useful when you want to capture a described workflow as a structured process map, refine it iteratively, and take it out of the tool as an export rather than sketching it by hand.
Requirements
A remote MCP endpoint at app.brownpaper.ai over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
Access requires OAuth authorization of a Brownpaper AI account, so the assistant acts within that account's data. Process maps are created and modified, and exports leave the service; review what is shared before exporting.

Installation

In SourceWeft

  1. Open Brownpaper AI 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/ai.brownpaper%2Fbrownpaper/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": {
    "brownpaper-ai": {
      "type": "http",
      "url": "https://app.brownpaper.ai/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. v1.0.0LatestNov 5, 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.