Riddle MCP

Riddle gives Claude the same reach over your interactive content that you have in the Riddle Creator web app: building, editing, publishing, organising, branding and analytics. The whole cycle happens in one conversation instead of across a dozen browser tabs. Start from a brief and Claude builds the piece, whether that's a quiz, poll, personality test, form, predictor, leaderboard, minigame or story. It gets assembled block by block, styled with your brand palette, then published with the embed code ready for your site. From there it doesn't stop at "created". Claude can read back any existing Riddle in full, change the parts that need changing (questions, answers, results, scoring, copy, design), validate it, and republish. Then pull the engagement numbers: overview stats plus breakdowns by project or by individual Riddle. That closes the loop. Analyse what a live Riddle is doing, find the question people drop off at, rewrite it, republish, and check the numbers again next week. Each step is a tool call, so Claude can run the whole cycle across your content library and tell you what it changed and why. Question banks, templates, projects and tags are all reachable too, so an improvement made once gets reused across everything you publish. The connection is scoped by OAuth to the account that authorises it, and respects that account's project roles and permissions. Notes on advertising and external content Riddle is not an advertising product and the connector serves no ads or sponsored content of its own. Worth naming up front, because it looks like the prohibited category at a glance: Riddle has an Ad block, available in all Riddle types, which the connector can place when a user asks for it. It carries no advertising from Riddle or any network. It references an ad slot the customer configured in their own project, or an iframe URL they supply, in content they own and publish themselves.