Access your Patreon creator data - campaigns, patrons, tiers, and posts.
Access your Patreon creator data - campaigns, patrons, tiers, and posts. The patreon mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.
Give AI assistants access to your Patreon creator data. The first authenticated Patreon MCP server - works with Claude Desktop, Cursor, Windsurf, VS Code Copilot, and any MCP-compatible client.
Everything the assistant can do here goes through one of these:
fetch_identity — Your authenticated profilefetch_campaigns — List all your campaignsfetch_campaign — Campaign details with tier breakdownfetch_members — Paginated patron list (100/page)fetch_posts — Paginated post list (20/page)fetch_post — Single post by IDMember — The Member tool exposed by this serverCampaign — The Campaign tool exposed by this serverTier — The Tier tool exposed by this serverPost — The Post tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need one environment variable: PATREON_ACCESS_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Patreon's toolset — fetch_identity, fetch_campaigns, fetch_campaign and 7 more — is a fair guide to whether it matches your workflow. It is maintained by KyuRish; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| fetch_identity | Your authenticated profile |
| fetch_campaigns | List all your campaigns |
| fetch_campaign | Campaign details with tier breakdown |
| fetch_members | Paginated patron list (100/page) |
| fetch_posts | Paginated post list (20/page) |
| fetch_post | Single post by ID |
| Member | The Member tool exposed by this server. |
| Campaign | The Campaign tool exposed by this server. |
| Tier | The Tier tool exposed by this server. |
| Post | The Post tool exposed by this server. |
{
"mcpServers": {
"patreon": {
"command": "uv",
"args": ["run", "--directory", "/path/to/patreon-mcp-server", "src/patreon_mcp_server/server.py"],
"env": {
"PATREON_ACCESS_TOKEN": "your_token_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PATREON_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.