brief-desk MCP
Allows agents to generate briefs from any GitHub repository via the workspace-brief backend, including live GitHub access configured by repository owner/name and token.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@brief-desk MCPbrief me on the open checkout risks in the sample workspace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
brief-desk
One-repo engineering briefing desk: Next.js + CopilotKit (AG-UI) + Python MCP.
Pick a source (auto, GitHub, docs URL, compare, corpus), run the agent, get a cited brief. Free-form chat can call the same MCP tools. Tool cards, a live plan board, and cancel are built into the UI.
Browser
│
├─ Run agent / demos → POST /api/brief-run → MCP + Groq draft
└─ Free-form chat → CopilotKit → MCP tools
│
▼
Python MCP (backend/)
├── brief_auto / brief_orchestrate
├── brief_eval
├── brief_fetch_url / brief_web_search
├── brief_github_trending / brief_github_search
├── brief_repo_* (ask/overview/file/releases/security)
└── brief_corpus → mcp/corpus/*.mdFeatures
Deterministic run path (
/api/brief-run): gather → draft → eval → reviseAutonomous auto mode (
brief_auto): invents plan from a free-form goalWeb search (
brief_web_search): DuckDuckGo Instant Answer, no API keyGitHub trending (
brief_github_trending): live scrape of github.com/trendingRepo search (
brief_github_search): GitHub Search API shortlistsReleases + security (
brief_repo_releases,brief_repo_security)In-chat tool cards for MCP calls on the free-form path
Live plan board (SSE step events) + Cancel run
Brief history (reopen / copy / download
.md)Optional GitHub sign-in (Supabase): syncs history + saved shortcuts across devices; guest mode stays localStorage
Light / dark / system theme
Bundled sample corpus under
mcp/corpus/(no separate packages)
Related MCP server: revibe-mcp
Setup
cd brief-desk
cp .env.example .env.local
# OPENAI_API_KEY = Groq key (https://console.groq.com)
npm install
# Python MCP (uv installs deps from backend/pyproject.toml)
cd backend && uv sync && cd ..Requires uv and Python 3.11+. See CONTRIBUTING.md.
Run
npm run devPython MCP health: http://127.0.0.1:3108/health (
runtime: python,version: 0.10.0)
Docker Compose
cp .env.example .env.local # set OPENAI_API_KEY
docker compose up --buildSame ports: UI :3000, MCP :3108.
Legacy TypeScript MCP (optional): npm run dev:mcp:ts
Sources
Source | What you set | Behavior |
Auto | free-form goal with |
|
Trending | language + daily/weekly/monthly | live GitHub trending shortlist |
Package | npm or PyPI + package name |
|
Releases | repo + two tags |
|
GitHub |
| guided orchestrate (+ releases/security on risks) |
Docs | public URL | fetch + brief |
Compare | two repos | side-by-side |
Corpus | none | bundled |
Auto goals like “Brief the npm package zod” also invent source_kind: package. Release deltas use brief_repo_release_diff.
Verify
npm test
curl -s http://127.0.0.1:3108/health
curl -s -X POST http://localhost:3000/api/brief-run \
-H 'content-type: application/json' \
-d '{"source":"auto","goal":"Brief facebook/react risks","question":"Brief facebook/react risks"}'CI runs the same suite on every push/PR (.github/workflows/ci.yml).
Render: deploy with the root Dockerfile (Python MCP). After deploy, /health should show "runtime":"python" and "version":"0.10.0".
Vercel: point MCP_URL at that Render /mcp endpoint.
Optional Supabase sync: create a free project, run supabase/schema.sql, enable the GitHub auth provider (callback URL https://<project>.supabase.co/auth/v1/callback), and set NEXT_PUBLIC_SUPABASE_URL + NEXT_PUBLIC_SUPABASE_ANON_KEY on Vercel. Without those env vars the desk stays guest-only.
Stack
Layer | Notes |
UI | CopilotKit React + control panel (Next.js / Vercel) |
Run path |
|
Tools backend | Python MCP Streamable HTTP ( |
Web | DuckDuckGo Instant Answer |
Corpus |
|
Eval | Free heuristic rubric |
License
MIT. See LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
- WitWikiOAuthapp.witwiki
A shared team wiki your coding agents read and write — across every repo and every MCP client.
Turn a GitHub repo or docs site into agent-ready context: pack it or search it, over MCP.
Repo intel for AI coding agents: overview, PRs, contributors, hot files, CI, deps. Remote MCP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEmpower any MCP-compatible AI Agent(MCP Client) with engineering-grade capabilities to understand, modify, run, and deliver real-world code repositories.208 PyPI1,216Apache 2.0
- AlicenseAqualityDmaintenanceEnables analysis of any GitHub repository to get architecture, file roles, execution flows, system design Q\&A, and structured agent context. Works with MCP-compatible clients like Claude Desktop, Cursor, and Windsurf.626 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables natural-language analysis of GitHub repositories by exposing repository metadata, source code retrieval, search, and file reading as MCP tools, with answers grounded in the actual repository content.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to save and retrieve code snippets, perform semantic vector search, generate code style guides and wiki documentation, and orchestrate multi-agent workflows through MCP tools.-