Distribution
tech.distributionPublished by distribution.techOfficial publisherv1.37.0Updated Oct 26, 2026
Priced X creators, campaigns from a goal, plan changes, mandated payment links, proof and results.
Overview
Remote MCP server for Distribution that lets an assistant price X creators, build campaigns from a goal, plan changes, and issue mandated payment links with…
- What you can do
- Price X creators and assemble campaigns from a stated goal.
- Plan and adjust campaign changes.
- Create mandated payment links tied to the brand's mandate.
- Retrieve proof and results for campaigns.
- No individual tools are listed in the manifest, so exact operations are not documented here.
- When to use it
- Useful when an assistant needs to run influencer-style campaigns on X: estimating creator costs, drafting a campaign from a goal, and tracking payment links, proof and results inside one workspace.
- Requirements
- A remote endpoint at app.distribution.tech over streamable HTTP, with OAuth required. An API key must be created on the Developers screen and sent as a Bearer token in the Authorization header; the key carries the scopes and the mandate the brand set.
Installation
In SourceWeft
- Open Distribution in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/tech.distribution%2Fdistribution/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"distribution": {
"type": "http",
"url": "https://app.distribution.tech/api/mcp"
}
}
}Tools
0Version history
15- v1.37.0LatestOct 26, 2026
- v1.36.0Oct 25, 2026
- v1.34.0Oct 23, 2026
- v1.32.0Oct 23, 2026
- v1.31.0Oct 22, 2026
- v1.30.0Oct 22, 2026
- v1.29.0Oct 22, 2026
- v1.26.3Oct 21, 2026
- v1.26.2Oct 21, 2026
- v1.26.1Oct 21, 2026
- v1.25.1Oct 19, 2026
- v1.25.0Oct 19, 2026
- v1.24.0Oct 19, 2026
- v1.21.0Oct 18, 2026
- v1.18.0Oct 16, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
