Access your Patreon creator data - campaigns, patrons, tiers, and posts.
mcp-name: io.github.KyuRish/patreon-mcp-server 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. Go to Patreon Developer Portal and copy your Creator Access Token. This token gives access to your own campaign data only. Claude Desktop - add to : Claude…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
mcp-name: io.github.KyuRish/patreon-mcp-server 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. Go to Patreon Developer Portal and copy your Creator Access Token. This token gives access to your own campaign data only. Claude Desktop - add to : Claude Code - add to in your project root: Ask your AI assistant things like: "Show me my Patreon campaigns"…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.