ProjectBrain MCP

Created By
9 Trinkets3 months ago
ProjectBrain MCP provides project/task/decision/fact/skill/milestone/team-message tools for persistent AI project management.
Overview

What is ProjectBrain MCP?

ProjectBrain MCP is a remote MCP server for persistent project management.
It helps agents and teams track work across sessions with structured tools for tasks, decisions, facts, milestones, and team messaging.

How to use ProjectBrain MCP?

  1. Create a ProjectBrain account and generate an API key (pb_...).
  2. Add the server config and set:
    • AUTH_HEADER=Bearer pb_YOUR_API_KEY
  3. Connect to:
    • https://mcp.projectbrain.tools

Key features

  • Task lifecycle and dependency tracking
  • Decision logging with rationale
  • Durable project facts (shared memory)
  • Reusable skills/procedures
  • Milestone progress tracking
  • Team messaging for human/agent coordination

Use cases

  1. AI-assisted sprint planning and execution
  2. Multi-agent coordination with persistent context
  3. Capturing technical decisions and conventions
  4. Building a searchable project memory for ongoing delivery

Authentication

ProjectBrain MCP requires bearer authentication.
OAuth metadata is exposed via:

  • /.well-known/oauth-protected-resource
  • /.well-known/oauth-authorization-server

Server Config

{
  "mcpServers": {
    "project-brain": {
      "url": "https://mcp.projectbrain.tools",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer pb_YOUR_API_KEY"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
9 Trinkets
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago