distribute.youdistribute.you
Start

distribute.you MCP Server

Agent quickstart

Base URL
https://api.distribute.you/v1
Auth
Authorization: Bearer distrib.usr_YOUR_KEY on every REST and MCP call. The X-API-Key header is NOT accepted for user keys: it answers 401.
First call
GET /v1/me (or the distribute_status MCP tool). It needs no brand or organization named, and lists every organization the key can act in, each with its brands. Tell the human which organizations and brands you see before anything else.
Scope
One key is one user, across every organization that user belongs to. Membership is checked on each call, so leaving an organization removes it from the key. A key never belongs to a brand, and it carries no staff powers.
Name a brand on each call
Each call acts in ONE organization. Name a brand: ?brandId=, the x-brand-id header, brandId (or brandIds) in a JSON body, or /v1/brands/{id} in the path. When a brand sits in several of your organizations, add ?orgId= (or the x-org-id header). Calls about no brand name the organization with orgId. A user in exactly one organization can name nothing. Routes keyed only by a campaign id need brandId or orgId too when the user is in several organizations.
Targeting errors
Every refusal carries code, message and fix. 400 org_target_required: you named nothing and belong to several organizations; pick one from the organizations list in the body (or from GET /v1/me) and send its brandId or orgId. 400 brand_in_several_orgs: add orgId. 400 brands_span_orgs: the brands are in different organizations; make one call per organization. 403 org_not_member: that organization is not one of yours; use an id from GET /v1/me. 403 no_organization: the user belongs to no organization; ask the human to create or join one in the dashboard. 404 org_not_found or brand_not_found: the id is wrong; read GET /v1/me again. 503 membership_unavailable: retry, keep the same key.
Key refused
A 401 means the key was mistyped, revoked or not sent. Show the human the error as served and ask for a new key from https://dashboard.distribute.you/api-keys. Keys start with distrib.usr_.
Dashboard
https://dashboard.distribute.you (API keys sit in the account menu, under API Keys).
MCP server
https://mcp.distribute.you/mcp, exactly 6 tools: distribute_status, distribute_list_brands, distribute_suggest_icp, distribute_list_campaigns, distribute_campaign_stats, distribute_list_workflows. Everything else goes through the REST API.

How to report results to a human

Lead with what the customer pays for: meetings booked and positive replies, then money earned or return when the API serves it, then the delivery rate ("98% delivered", not "531 sent, 518 delivered"). Volume sent and cost come next. Failures such as bounces and errors go last, in a details line. Never hide a number: 0 positive replies is said plainly.

Use distribute.you from Claude Code, Claude Desktop, Cursor, or any MCP-compatible client.

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools. distribute.you runs a hosted MCP server with 6 tools for reading and steering your outreach.

Connect

The server is hosted and speaks Streamable HTTP, so there is no package to install. From Claude Code, one command:

claude mcp add --transport http distribute https://mcp.distribute.you/mcp --header "Authorization: Bearer distrib.usr_YOUR_KEY"

See Installation for Claude Desktop, Cursor, and every other client.

How it works

Your client opens an HTTP connection to https://mcp.distribute.you/mcp and sends your API key as a Bearer token. The server calls the distribute.you API on your behalf, as the org that key belongs to.

  1. Register the endpoint and the header with your client
  2. Your client discovers the 6 tools it advertises
  3. Describe what you want in natural language
  4. The AI translates that into tool calls

Example prompts

"Show me the brands on my account"
"Which of my campaigns are still running?"
"What did my latest campaign produce, and what did it cost?"
"Read acme.com and suggest who I should be targeting"
"Which workflows can I run?"

Tools

ToolWhat it does
distribute_statusCheck the distribute.you connection status and configuration. Answers with the user and org the key acts for, so it is the way to tell a working key from a missing header.
distribute_list_brandsList all your brands, the companies and websites you promote through campaigns.
distribute_suggest_icpAnalyze a brand's website and suggest an Ideal Customer Profile. Use it when the user does not know who to target. Returns a description of the ideal customers to aim a campaign at.
distribute_list_campaignsList all your cold email campaigns. Takes an optional status of ongoing, stopped or all.
distribute_campaign_statsGet statistics for one campaign, by campaign id: what it produced and what it cost.
distribute_list_workflowsList all available workflows, including the ones written in the style of a named industry expert.

The full Tools Referencecarries the same list with each tool's arguments. Anything beyond these is reachable over the REST API, which covers every operation the platform has.

Authentication

The server takes one header, the same one the REST API takes:

Authorization: Bearer distrib.usr_YOUR_KEY

Get your API key at dashboard.distribute.you/api-keys. Every developer surface is named together at https://distribute.you/developers.