For EveryoneUpdated August 2026

Fanflet MCP and OAuth

Connect Claude, ChatGPT, or any MCP client. OAuth 2.1 with PKCE, named scopes, Pro+ gate. First-run: create, add a link or library item, publish URL + QR. No API keys and no public sandbox.

When to use Fanflet MCP

Connect an AI agent when a speaker, sponsor, or admin wants the agent to operate inside their Fanflet workspace: list fanflets, add resource blocks, read analytics, manage sponsor connections. Attendees still scan a QR code on the public site. Fanflet is not a public REST dump of speaker data, and speaker-generated pages are not offered for model training.

Connect with OAuth 2.1

No API keys

MCP OAuth with PKCE is the supported path. There is no self-serve API-key product and no public sandbox. Use a real Pro or Studio speaker account, a sponsor account, or localhost.
1

Read discovery documents

Start at /llms.txt and the OpenAPI spec at /openapi.json. Protected resource metadata lives at /.well-known/oauth-protected-resource/api/mcp.
2

Register the client

POST to /api/mcp/register with allowlisted redirect URIs. Claude and ChatGPT connector callbacks are already allowed, plus http://localhost.
3

Authorize with PKCE

Send the user to /api/mcp/authorize with response_type=code and code_challenge_method=S256. Exchange the code at /api/mcp/token.
4

Call MCP

GET, POST, or DELETE /api/mcp with Authorization: Bearer. Tools are scoped to the signed-in role.

Scopes

Named OAuth scopes match scopes_supported in RFC 9728 metadata. Request exactly one.

  • speaker — fanflets, resources, subscribers, analytics. Requires Pro or Studio.
  • sponsor — connections, leads, campaigns.
  • audience — saved fanflets and following.
  • admin — platform operator tools.

Pro and Studio gate

Speakers on the Free plan receive HTTP 403 subscription_required before any tool runs. Upgrade at /pricing. Sponsor, audience, and platform_admin roles are not gated by that check.

Speaker first-run over MCP

A Pro or Studio speaker agent can publish a first fanflet without the web UI:

  1. speaker_create_fanflet — draft
  2. speaker_add_resource_block with type=link, or speaker_list_library_items then speaker_add_library_block to attach an existing library item
  3. speaker_publish_fanflet — returns the public URL plus the existing QR image at /api/qr/{fanfletId}

File upload is not available over MCP. Free speakers still receive HTTP 403 before any of these tools run.