Briefly MCP

Briefly MCP lets an AI agent work inside one Briefly project through a scoped API token. The agent can list project context, read and update briefs, and create briefs, roadmap items, card-tracker cards, and meeting notes.

The agent does not need access to the Briefly source code, Firebase project, or a service account key.

Requirements

• Node.js 20 or newer
• A client that supports MCP servers, such as Claude Desktop, Claude Code, Cursor, or another MCP-compatible tool
• A Briefly Agent token generated by the project owner

Owner Setup

1. Open the project in Briefly.
2. Go to Team or Members.
3. Add the agent's email address with the Agent role.
4. Copy the generated MCP config while the token is shown.
5. Paste that config into the agent client's MCP settings.
6. Restart the agent client so it loads the Briefly tools.

Briefly stores only a hash of the token. If the token is lost, generate a new one from the project member list.

Claude Desktop

For the simplest Mac setup, copy the Claude Desktop install command generated by Briefly, paste it into Terminal, then restart Claude Desktop.

The command looks like this:

npx -y @beginthework/briefly-mcp@latest install --client claude-desktop --server-name briefly-project-agent --api-url https://us-central1-briefs-begin.cloudfunctions.net/agentApi

It prompts for the Briefly token, updates Claude Desktop's MCP config, and creates a backup of the existing file.

You can also add the generated server block manually to claude_desktop_config.json:

{
  "mcpServers": {
    "briefly-project": {
      "command": "npx",
      "args": ["-y", "@beginthework/briefly-mcp@latest"],
      "env": {
        "BRIEFLY_AGENT_API_URL": "https://us-central1-briefs-begin.cloudfunctions.net/agentApi",
        "BRIEFLY_AGENT_TOKEN": "PASTE_BRIEFLY_AGENT_TOKEN_HERE"
      }
    }
  }
}

Cursor

Add the generated server block to .cursor/mcp.json:

{
  "mcpServers": {
    "briefly-project": {
      "command": "npx",
      "args": ["-y", "@beginthework/briefly-mcp@latest"],
      "env": {
        "BRIEFLY_AGENT_API_URL": "https://us-central1-briefs-begin.cloudfunctions.net/agentApi",
        "BRIEFLY_AGENT_TOKEN": "PASTE_BRIEFLY_AGENT_TOKEN_HERE"
      }
    }
  }
}

Suggested Agent Instructions

Give the agent a short instruction file alongside the MCP config:

# Briefly Project Agent

You have access to the Briefly MCP tools for one project.

Use `list_context` before creating work so you can find the right roadmap and card tracker IDs.

Create content only when asked by the project owner. Prefer drafts over final decisions unless the owner says otherwise.

Use:
- `get_brief` to load an existing brief before revising it
- `update_brief` to revise an existing brief in place (prefer this over creating a duplicate)
- `create_brief` for brand-new product briefs, strategy docs, specs, and HTML briefs
- `add_roadmap_item` for phases, milestones, and larger planned work
- `add_card` for execution tasks in the card tracker
- `create_meeting_note` for meeting summaries and decisions

Never expose the Briefly token in chat, commits, documents, or screenshots. If it is exposed, tell the owner to rotate it.

Multiple Projects

Add the same agent email to each Briefly project separately. Each project gets its own token and MCP server entry. This keeps access scoped and lets the owner revoke one project without affecting the others.

Development

For local package development:

npm install
npm start

For production owner onboarding, use the npx -y @beginthework/briefly-mcp@latest config generated inside Briefly.