BTPR IntelligenceMCP documentation

Connect your PR workspace.

BlackTea PR Intelligence is a standalone, OAuth-protected MCP service. It stores durable PR context in its hosted control plane and uses pushed GitHub commits as source evidence.

Endpoint

https://mcp.blacktea.tech/api/mcp

The subdomain root also accepts MCP POST requests while keeping the public product page available on GET.

MCP clients discover OAuth through the protected-resource metadata endpoint. Authorization code flow with PKCE S256 is required. Dynamic client registration is supported.

Scopes

pr_read · pr_draft · pr_review · pr_approve
pr_outreach · pr_publish · pr_admin

An OAuth scope is only one gate. The service also checks workspace membership, server-side capability, classification, quota, exact artifact hash, and—where applicable—a fresh one-time action authorization.

Start a session

  1. Connect the MCP endpoint from Codex, ChatGPT, or another compatible client.
  2. Authorize the smallest scopes needed.
  3. Select a connected workspace, then invoke the continue-pr prompt or call resume_pr_workspace.
  4. For repository evidence, scan a pushed branch and fetch only the authorized source IDs needed for the story.

Codex

codex mcp add blacktea-pr --url https://mcp.blacktea.tech/api/mcp
codex mcp login blacktea-pr --scopes pr_read,pr_draft,pr_review,pr_approve,pr_admin

In every fresh task, call list_pr_workspaces, then resume_pr_workspace with the selected workspace ID. A reviewed repository marker may save the non-secret endpoint and workspace ID; it must never contain a token.

Private GitHub evidence

A workspace administrator starts connect_pr_github_repository without entering a repository first. GitHub authorization and App installation happen before the authenticated BlackTea repository picker shows only organizations and repositories that user can administer. The server performs a final repository-scoped check before storing a signed tenant-bound installation binding. Personal access tokens, GitHub user tokens, App private keys, and installation tokens are never stored in workspace state or returned through MCP.

Legacy workspace continuity

Workspace administrators can import and export the bounded public-relations-plugin.pr/v1 archive. Imported facts remain provisional and artifacts remain drafts. Export omits credentials, private contacts, restricted evidence, approvals, authorizations, audit details, and execution receipts.

Owned channels

Social and newsroom previews report whether an exact tenant, workspace, channel, and destination-bound adapter is verified. Execution remains feature-flagged and requires an exact-content approval, one-time payload authorization, quota, matching idempotency key, and a receipt that echoes the authorized destination and payload hash.

Safety boundary

Every generated artifact begins as a non-distributable draft. The agent cannot approve its own work. Material edits invalidate approvals. Sending and owned-channel publishing stay disabled unless all exact-content, integration, quota, destination, authorization, and idempotency checks pass. Paid press wires are never executed.