Riddle
MCP-Server von Riddle
Quizze, Umfragen, Formulare und Persönlichkeitstests in Riddle aus einem KI-Chat erstellen, bearbeiten, veröffentlichen und auswerten.
Mit Riddle verbinden
Riddle braucht eine Anmeldung. Verbinde dich mit seiner eigenen URL:
Dein Client öffnet beim ersten Mal die Anmeldung von Riddle. Das Token bleibt zwischen deinem Client und Riddle.
Diesen Server teilen
Öffnet diese Seite mit der URL und den Einrichtungsschritten.
mcp.tc/i/riddleÜber den Server
Verbindet einen KI-Assistenten mit der Riddle-Creator-API. Du kannst vorhandene Riddles auflisten, neue Quizze, Umfragen, Formulare und Persönlichkeitstests erstellen, sie bearbeiten und Ergebnisse aus einem Chat heraus auswerten. Aktionen, die über die Riddle API verfügbar sind, lassen sich über den Assistenten auslösen.
Der Server wird unter https://www.riddle.com/creator/api/v3/mcp gehostet und nutzt Streamable HTTP. Ein Riddle-Konto ist erforderlich. Du meldest dich per OAuth im Browser an, und der Token übernimmt die Projektrollen und Berechtigungen des jeweiligen Benutzers. Für Headless-Agents gibt es eine Option mit Schlüssel in der URL, empfohlen wird jedoch OAuth.
Was du damit machen kannst
- Vorhandene Riddles in deinem Konto auflisten
- Quizze, Umfragen, Formulare und Persönlichkeitstests erstellen
- Bestehende Riddles bearbeiten
- Riddle-Ergebnisse und Statistiken auswerten
- Anmeldung mit deinem eigenen Riddle-Konto per OAuth
Tools 48
media_upload_linkSchreibtCreate media upload link
media_deleteKann löschenDelete media library file
riddle_template_createSchreibtCreate riddle template
riddle_template_updateKann löschenUpdate riddle template
riddle_template_listLiest nurList riddle templates
riddle_template_public_listLiest nurList public riddle templates
riddle_template_getLiest nurGet riddle template
riddle_template_useSchreibtCreate riddle from template
riddle_tag_listLiest nurList riddle tags
riddle_tag_addSchreibtAdd tag to riddles
riddle_tag_removeKann löschenRemove tag from riddles
riddle_tag_deleteKann löschenDelete riddle tag
36 weitere Tools anzeigen
pingLiest nurPing the MCP server
riddle_listLiest nurList riddles
riddle_getLiest nurGet riddle
riddle_get_embed_codeLiest nurGet riddle embed code
riddle_publishKann löschenPublish or unpublish riddle
riddle_renameKann löschenRename riddle
riddle_deleteKann löschenDelete riddle
riddle_moveKann löschenMove riddle to another project
whoamiLiest nurShow the connected account
question_bank_createSchreibtCreate question bank
question_bank_listLiest nurList question banks
question_bank_getLiest nurGet question bank
question_bank_renameKann löschenRename question bank
question_bank_update_notesKann löschenUpdate question bank notes
question_bank_duplicateSchreibtDuplicate question bank
question_bank_publishKann löschenPublish question bank
question_bank_item_addSchreibtAdd question bank item
question_bank_item_updateKann löschenUpdate question bank item
question_bank_discard_changesKann löschenDiscard question bank changes
question_bank_deleteKann löschenDelete question bank
question_bank_item_deleteKann löschenDelete question bank item
question_bank_get_itemsLiest nurGet question bank items
question_bank_tag_addSchreibtAdd tag to question bank
question_bank_tag_removeKann löschenRemove tag from question bank
palette_getLiest nurGet brand palette
palette_customizeKann löschenCustomize brand palette
integration_listLiest nurList integrations
riddle_builder_createSchreibtBuild a riddle
riddle_builder_updateKann löschenUpdate a riddle
riddle_builder_validateLiest nurValidate a build configuration
reference_getLiest nurGet builder reference document
stats_fetchLiest nurFetch riddle statistics
project_listLiest nurList projects
project_getLiest nurGet project
project_get_settingsLiest nurGet project settings
riddle_previewLiest nurPreview a Riddle
Am 17. Nov. 2026 vom laufenden Server gelesen. „Liest nur“, „Schreibt“ und „Kann löschen“ sind Hinweise, die der Server selbst angibt; dein Client entscheidet, ob er vor dem Ausführen eines Tools nachfragt.
Beispiel-Prompts
Liste meine neuesten Riddles auf.
Erstelle ein Quiz mit fünf Fragen über europäische Hauptstädte.
Erstelle einen Persönlichkeitstest mit drei Ergebnisseiten.
Zeige mir die Statistiken meiner neuesten Umfrage.
Einrichtung
Jeder Client verbindet sich mit riddle.com, und beim ersten Mal fragt Riddle nach deiner Anmeldung. Wähl deinen; die Seite merkt sich deine Wahl.
Claude Code
- Führe das in einem Terminal in deinem Projektordner aus:
claude mcp add --transport http riddle https://www.riddle.com/creator/api/v3/mcp- Starte Claude Code, tippe
/mcp, wähle riddle und dann Authenticate. Ein Browserfenster öffnet sich für die Anmeldung bei Riddle.
Ergänze --scope user, damit er in jedem Projekt verfügbar ist, nicht nur in diesem.
Claude Desktop
- Öffne Customize → Connectors, klick auf + Add und dann auf Add custom connector.
- Nenne ihn Riddle und füge diese URL ein:
https://www.riddle.com/creator/api/v3/mcp- Klick auf Add, dann auf Connect, und melde dich an, wenn Riddle danach fragt.
Die JSON-Konfigurationsdatei von Claude Desktop startet nur lokale Server. Remote-Server laufen über Connectors, und Connectors, die du auf claude.ai hinzufügst, erscheinen auch hier.
claude.ai
- Öffne das Connector-Formular auf claude.ai. Dieser Button füllt Name und URL für dich aus:
Zu claude.ai hinzufügen (öffnet in einem neuen Tab)
- Prüfe, dass die URL
https://www.riddle.com/creator/api/v3/mcplautet, und klick auf Add. - Klick auf Connect und melde dich an, wenn Riddle danach fragt.
Kostenlose Pläne erlauben einen benutzerdefinierten Connector. In Team- und Enterprise-Plänen fügt ihn ein Owner unter Organization settings → Connectors hinzu.
ChatGPT
- Geh auf chatgpt.com zu Plugins, wähle + und dann Add custom MCP server.
- Gib einen Namen für den Server ein.
- Füge unter Connection
https://www.riddle.com/creator/api/v3/mcpals Server-URL ein und wähle als Authentifizierung OAuth. ChatGPT schickt dich zur Anmeldung zu Riddle. - Setz den Haken bei I understand and want to continue und wähle dann Create as a plugin.
Ob du einen eigenen MCP-Server hinzufügen kannst, hängt von deinem ChatGPT-Tarif und den Berechtigungen deines Workspace ab (in Business-Workspaces können es Admins und Owner).
Cursor
Zu Cursor hinzufügen (öffnet in einem neuen Tab)
Oder trag ihn von Hand in ~/.cursor/mcp.json (alle Projekte) oder .cursor/mcp.json (dieses Projekt) ein:
{
"mcpServers": {
"riddle": {
"url": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}Cursor zeigt neben dem Server Needs authentication. Klick auf die Schaltfläche daneben, um dich anzumelden.
VS Code
In VS Code installieren (öffnet in einem neuen Tab)
Oder aus einem Terminal:
code --add-mcp '{"name":"riddle","type":"http","url":"https://www.riddle.com/creator/api/v3/mcp"}'Oder committe ihn ins Repository in .vscode/mcp.json:
{
"servers": {
"riddle": {
"type": "http",
"url": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}VS Code bittet dich beim ersten Start des Servers um eine Anmeldung.
Devin Desktop
- Füge ihn zu
~/.config/devin/mcp_config.json(macOS und Linux) oder%APPDATA%\devin\mcp_config.json(Windows) hinzu:
{
"mcpServers": {
"riddle": {
"serverUrl": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}- Aktualisiere die Liste der MCP-Server in Cascade und melde dich an, wenn du gefragt wirst.
Devin Desktop ist der neue Name von Windsurf. Für Remote-Server liest es serverUrl (oder url).
Codex
codex mcp add riddle --url https://www.riddle.com/creator/api/v3/mcp
codex mcp login riddleOder bearbeite ~/.codex/config.toml direkt:
[mcp_servers.riddle]
url = "https://www.riddle.com/creator/api/v3/mcp"Gemini CLI
gemini mcp add --transport http riddle https://www.riddle.com/creator/api/v3/mcpFühre dann in Gemini CLI /mcp auth riddle aus, um dich anzumelden.
Damit fügst du ihn dem aktuellen Projekt hinzu. Ergänze -s user, um ihn überall zu nutzen.
Jeder Client
Die meisten Clients akzeptieren diese Form. Manche nennen das URL-Feld anders: serverUrl in Devin Desktop, httpUrl in der Einstellungsdatei von Gemini CLI.
{
"mcpServers": {
"riddle": {
"type": "http",
"url": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}Zed legt Server in seinen Einstellungen unter context_servers ab. Cline braucht "type": "streamableHttp", sonst nimmt es SSE an.
Dein Client startet nur lokale Server? Dann binde den Server über npx -y mcp-remote https://www.riddle.com/creator/api/v3/mcp ein.
Einbinden
Zeig Riddle in einem README oder auf deiner Website. Jede Einbindung verlinkt auf diese Seite, nutzt die eigene URL des Servers und setzt keine Cookies. So funktionieren Einbindungen
Karte, iframe und JSON sind auf Englisch. Häng ?lang=it, fr, de oder es an ihre Adresse an, um eine andere Sprache zu bekommen.
README-Badge
[](https://mcp.tc/i/riddle)<a href="https://mcp.tc/i/riddle"><img src="https://mcp.tc/i/riddle/badge.svg" alt="Riddle on mcp.tc" height="20"></a>Es folgt dem hellen oder dunklen Modus der Lesenden. Hänge ?theme=light oder ?theme=dark an, um ihn festzulegen, oder ?style=compact, um das Zeichen ohne Schriftzug zu zeigen.
Website-Karte
<script src="https://mcp.tc/w/riddle.js" async></script>Die Karte erscheint dort, wo das Tag steht. Füge dem Tag data-theme="dark" oder data-size="compact" hinzu, um sie zu ändern. Die Datei enthält alles, was sie braucht, stellt also keine weiteren Anfragen und setzt keine Cookies.
iframe
<iframe src="https://mcp.tc/embed/riddle" title="Riddle on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Nutze es auf Seiten, die keine Skripte erlauben. Hänge ?theme=light oder ?theme=dark an die Adresse an, um die Farben festzulegen.
JSON
Der Eintrag als Daten für deine eigenen Seiten und Tools: Name, Kurzbeschreibung, die eigene URL des Servers, Tools und die „Add to“-Links. Jede Website kann ihn lesen (CORS ist offen).
https://mcp.tc/i/riddle.jsonKI-Prompt
Füg ihn in einen KI-Coding-Assistenten wie Claude Code oder Cursor ein, und er baut die Karte von Riddle in deine Website ein.
Füge meiner Website die mcp.tc-Karte für den MCP-Server Riddle hinzu. Es ist ein einziges statisches Skript: kein Build-Schritt, kein Paket zu installieren, keine Cookies.
Setz dieses Tag dorthin, wo die Karte erscheinen soll. Die Karte erscheint direkt davor:
```html
<script src="https://mcp.tc/w/riddle.js" async></script>
```
Um sie woanders zu zeigen, setz dort diesen Platzhalter ein und lade dasselbe Skript nur einmal, zum Beispiel vor `</body>`. Lass den Link darin stehen: Besucher ohne JavaScript sehen ihn.
```html
<div data-mcptc="riddle"><a href="https://mcp.tc/i/riddle">Riddle on mcp.tc</a></div>
```
Optionen:
- `data-theme="light"` oder `"dark"` am Tag oder Platzhalter legt die Farben fest. Ohne das Attribut folgt die Karte dem hellen oder dunklen Modus der Besucher.
- `data-size="compact"` ergibt eine kleinere Karte ohne Kurzbeschreibung.
- Die CSS-Variable `--mcptc-max-width` am Platzhalter oder einem Elternelement legt die Breite fest (Standard `520px`).
- `?lang=` in der Skript-URL legt die Sprache der Karte fest: `en`, `it`, `fr`, `de` oder `es`.
Wenn die Website eine Content Security Policy hat, erlaube `script-src https://mcp.tc` und `img-src data:` (das Icon ist eingebettet).
Für ein README oder andere Markdown-Dokumentation nimm stattdessen das Badge:
```markdown
[](https://mcp.tc/i/riddle)
```
Referenz: https://mcp.tc/de/embedÄnderungsverlauf
Wir lesen die Tool-Liste dieses Servers alle 3 Stunden und halten fest, was sich ändert. Zuletzt gelesen: 18. Nov. 2026, 05:37 UTC.
-
2 Tools geändert.
Details, 11. Nov. 2026, 14:54 UTC
Geändert 2
riddle_builder_createEingabeschemariddle_builder_updateEingabeschema
-
2 Tools geändert.
Details, 11. Nov. 2026, 11:47 UTC
Geändert 2
riddle_builder_createEingabeschemariddle_builder_updateEingabeschema
-
2 Tools geändert.
Details, 2. Nov. 2026, 11:51 UTC
Geändert 2
riddle_builder_createEingabeschemariddle_builder_updateEingabeschema
-
17 Tools geändert.
Hinweis geändert: kann Daten verändern
Details, 30. Okt. 2026, 11:46 UTC
Geändert 17
integration_listBeschreibungVorherLists the Google Sheets and webhook integrations of a project as {items: [{id, type, name, connectedRiddles}]}. "name" is the value a build takes as publish.integrations.googlesheets / .webhook to connect that integration to a Riddle. A Google Sheet can only be connected in the Creator - with none listed, ask the user to add one there. A Riddle with a FileUpload form field cannot be published without a Google Sheets integration.
NachherLists the Google Sheets and webhook integrations of a project as {items: [{id, type, name, connectedRiddles}]}. "name" is the value a build takes as publish.integrations.googlesheets / .webhook to connect that integration to a Riddle. A Google Sheet can only be connected in the Creator - with none listed, ask the user to add one there. A Riddle with a FileUpload form field cannot be published without a Google Sheets integration. Reads the stored records only - contacts neither Google nor any webhook.
media_deleteHinweiseopenWorldHintnein wird zu ja
media_upload_linkHinweiseopenWorldHintnein wird zu ja
palette_customizeHinweisedestructiveHintnein wird zu ja
question_bank_discard_changesHinweiseidempotentHintja wird zu nein
question_bank_item_updateHinweiseidempotentHintja wird zu nein
question_bank_publishBeschreibung und HinweiseVorherMakes every item's draft content its published content - what a QuestionBank block of a live Riddle actually draws at view time - so the change reaches participants
immediately.The previously published content of each item is overwritten, and a pending item delete (question_bank_item_delete on a published item) is purged for good at this point. A bank with unpublished changes still works in a block, it just draws its last published state; question_bank_discard_changes is the opposite step. Read question_bank_get_items with and without published: true first when unsure what will change. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.NachherMakes every item's draft content its published content - what a QuestionBank block of a live Riddle actually draws at view time - so the change reaches participants immediately: every Riddle using the bank is republished and re-draws its questions, even when nothing changed. The previously published content of each item is overwritten, and a pending item delete (question_bank_item_delete on a published item) is purged for good at this point. A bank with unpublished changes still works in a block, it just draws its last published state; question_bank_discard_changes is the opposite step. Read question_bank_get_items with and without published: true first when unsure what will change. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
openWorldHintnein wird zu jaidempotentHintja wird zu nein
question_bank_renameHinweisedestructiveHintnein wird zu jaidempotentHintja wird zu nein
question_bank_update_notesHinweiseidempotentHintja wird zu nein
riddle_deleteHinweiseopenWorldHintnein wird zu ja
riddle_get_embed_coderiddle_previewriddle_renameriddle_template_createriddle_template_updateriddle_template_usestats_fetch -
11 Tools hinzugefügt, 4 Tools entfernt und 14 Tools geändert.
Hinweis geändert: kann Daten verändern, Neues Tool als destruktiv markiert
Details, 29. Okt. 2026, 17:47 UTC
Hinzugefügt 11
question_bank_duplicateSchreibtCopies a question bank and all of its items into a new, independent bank (editing one never affects the other) in projectId or the key's project. The source is left untouched. This is the one write a public template id is accepted for, and the way to change a template: duplicate it and edit the copy. Needs full access: riddle://reference/concepts/access.
question_bank_item_addSchreibtAdds ONE new question/item to a question bank; nothing existing is changed (question_bank_item_update replaces an item, question_bank_item_delete removes one). There is no universal item shape: read riddle://reference/question-bank/block-type-columns before the first add into a bank you have not populated - it lists the valid blockType values per Riddle type and the "columns" each expects (the blockTypeColumns listing is that document, not a tool). The item lands in the bank's DRAFT - question_bank_publish is what makes it something a QuestionBank block draws. "hasChanges" in the response says whether the bank now has unpublished changes. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
question_bank_item_deleteKann löschenDeletes ONE question/item of a question bank and touches nothing else. On a never-published item the delete is immediate and permanent; on a published one it only leaves the DRAFT - a live Riddle keeps drawing that item until question_bank_publish purges it, and question_bank_discard_changes brings it back until then. Permanent once purged: there is no trash and no restore. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
question_bank_item_updateKann löschenReplaces the content of ONE existing question/item of a question bank entirely - not a merge: blockType, category, difficulty and columns must all be sent even when unchanged, and a column or value left out is gone from the draft. blockType is immutable: a different value is rejected rather than retyping the item (delete it with question_bank_item_delete and add a new one instead). Read the item with question_bank_get_items first and send it back with its value ids intact. The change lands in the bank's DRAFT - question_bank_publish makes it live, question_bank_discard_changes throws every unpublished change away again. "hasChanges" in the response says whether the bank now has unpublished changes. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
question_bank_publishKann löschenMakes every item's draft content its published content - what a QuestionBank block of a live Riddle actually draws at view time - so the change reaches participants immediately. The previously published content of each item is overwritten, and a pending item delete (question_bank_item_delete on a published item) is purged for good at this point. A bank with unpublished changes still works in a block, it just draws its last published state; question_bank_discard_changes is the opposite step. Read question_bank_get_items with and without published: true first when unsure what will change. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
question_bank_renameSchreibtSets the title of a question bank. The title is metadata rather than DRAFT content, so it takes effect immediately AND permanently, is unaffected by publishing or discarding and never counts as an unpublished change. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
question_bank_tag_addSchreibtAdds a tag to a question bank, by tagName or tagId from riddle_tag_list - exactly one of the two, as riddle_tag_add does. Question bank tags and Riddle tags are ONE set per project, not two: the same tag applies to banks and Riddles and has the same id in both, which is why the ids come from riddle_tag_list. Reuses the project's tag of that name or creates it, and re-tagging changes nothing. question_bank_tag_remove takes it off again. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
question_bank_tag_removeKann löschenRemoves a tag from a question bank, by tagName or tagId from riddle_tag_list - exactly one of the two. Never creates anything: a tag the bank does not carry is an error. A tag nothing uses any more is deleted from the project, where "nothing" includes Riddles: a tag a Riddle still uses survives its last bank. Deleting a tagged bank cleans up the same way. This only ever takes the tag off THIS bank; riddle_tag_delete removes the label from the project itself. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
question_bank_update_notesKann löschenReplaces the plain-text maintainer notes of a question bank (never shown to participants) - the previous notes are overwritten entirely, not appended to, so read them with question_bank_get first and send everything that should remain. Notes are metadata rather than DRAFT content: the change takes effect immediately AND permanently, is unaffected by publishing or discarding and never counts as an unpublished change. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
riddle_tag_addSchreibtPuts a tag on Riddles - ONE assignment per Riddle, never the tag itself (riddle_tag_list reads the labels of a project, riddle_tag_remove takes a tag off again, riddle_tag_delete removes a label). Gives one Riddle (UUID) or many (UUIDs, max 100) the tag named by tagName - created in each Riddle's OWN project if it has none of that name, so one call can span projects - or by tagId, which exists in one project and therefore works only for that project's Riddles. Re-tagging changes nothing and no tag needs a publish. There is no projectId here: a tag lives in the project of the Riddle it is put on, which is where the scope comes from. Returns the tag plus all tags of the Riddle, and with UUIDs the {bulk, operation, summary, results} envelope with one entry per Riddle, a failure (no edit permission, a tagId from another project) reported as that entry's "error" without stopping the others. Only if the Riddle's origin.writableByThisKey is true (riddle_get, riddle_list): riddle://reference/…
riddle_tag_removeKann löschenTakes a tag off Riddles - ONE assignment per Riddle (riddle_tag_add puts it on, riddle_tag_delete removes a label nothing carries). Untags one Riddle (UUID) or many (UUIDs, max 100), by tagName or tagId, and creates nothing: a tag the Riddle or its project does not have is an error for that Riddle. Untagging the LAST carrier deletes the tag itself from the project, unless a question bank still uses it - so a tag rarely has to be deleted by hand, and a tag removed that way is gone for good (re-adding creates a new one with a new id). Returns the tag plus all remaining tags of the Riddle, and with UUIDs the {bulk, operation, summary, results} envelope with one entry per Riddle, a failure reported as that entry's "error" without stopping the others. Only if the Riddle's origin.writableByThisKey is true (riddle_get, riddle_list): riddle://reference/concepts/access.
Entfernt 4
question_bank_itemAdds or replaces ONE question/item of a question bank, by "action" - deleting one is question_bank_delete. There is no universal item shape: read riddle://reference/question-bank/block-type-columns before the first "add" into a bank you have not populated - it lists the valid blockType values per Riddle type and the "columns" each expects (the blockTypeColumns listing is that document, not a tool). "update" replaces the item's content entirely, so blockType, category, difficulty and columns must all be sent even when unchanged, and blockType is immutable: a different value is rejected rather than retyping the item (delete it and add a new one instead). Both change the bank's DRAFT - question_bank_manage(action: "publish") is what makes a change something a QuestionBank block draws, and question_bank_discard_changes throws every unpublished change away again. "hasChanges" in the response says whether the bank now has unpublished changes. Rejected for a public template id. Needs full ac…
question_bank_manageEverything that acts on a question bank as a whole, by "action" - the items themselves are question_bank_item, and the two calls that only destroy are question_bank_delete and question_bank_discard_changes. A public template id is accepted for "duplicate" only and rejected by every other action. "rename" sets the title and "updateNotes" replaces the plain-text maintainer notes (never shown to participants): both are metadata rather than DRAFT content, so they take effect immediately AND permanently, are unaffected by publishing or discarding and never count as an unpublished change. "publish" makes every item's draft content its published content - what a QuestionBank block actually draws at view time - and is when a pending item delete is finally purged; a bank with unpublished changes still works in a block, it just draws its last published state. "duplicate" copies the bank and all of its items into a new independent bank (editing one never affects the other) in projectId or the ke…
question_bank_tagAdds a tag to a question bank or removes one from it, by tagName or tagId from riddle_tag_list - exactly one of the two, as riddle_tag does. Question bank tags and Riddle tags are ONE set per project, not two: the same tag applies to banks and Riddles and has the same id in both, which is why the ids come from riddle_tag. "add" reuses the project's tag of that name or creates it, and re-tagging changes nothing. "remove" never creates anything - a tag the bank does not carry is an error - and a tag nothing uses any more is deleted from the project, where "nothing" includes Riddles: a tag a Riddle still uses survives its last bank. Deleting a tagged bank cleans up the same way. This only ever adds or removes the tag on THIS bank; riddle_tag_delete removes the label from the project itself. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
riddle_tagPuts a tag on Riddles or takes it off again, by "action" - ONE assignment per Riddle, never the tag itself (riddle_tag_list reads the labels of a project, riddle_tag_delete removes one). "add" gives one Riddle (UUID) or many (UUIDs, max 100) the tag named by tagName - created in each Riddle's OWN project if it has none of that name, so one call can span projects - or by tagId, which exists in one project and therefore works only for that project's Riddles; re-tagging changes nothing and needs no publish. "remove" takes the tag off again and creates nothing: a tag the Riddle or its project does not have is an error for that Riddle. Untagging the last carrier deletes the tag itself, unless a question bank still uses it - so a tag rarely has to be deleted by hand. There is no projectId here: a tag lives in the project of the Riddle it is put on, which is where the scope comes from. Both actions return the tag plus all tags of the Riddle, and with UUIDs the {bulk, operation, summary, resu…
Geändert 14
pingHinweiseidempotentHintnicht angegeben wird zu ja
question_bank_createBeschreibungVorherCreates a new, empty question bank for the given Riddle type ("Quiz" or "Poll"). Add items with
question_bank_item(action: "add"),then reference the returned "id" as "questionBankId" on a QuestionBank block of a riddle_builder_create call of the matching "type" - a bank created for "Quiz" can only be referenced from a Quiz, never a Poll, and vice versa. A bank lives in one project and can only be referenced from Riddles of that same project, so pass the projectId of the project the Riddle belongs to; omitting it creates the bank in the project the API key is scoped to. Needs full access: riddle://reference/concepts/access.NachherCreates a new, empty question bank for the given Riddle type ("Quiz" or "Poll"). Add items with question_bank_item_add, then reference the returned "id" as "questionBankId" on a QuestionBank block of a riddle_builder_create call of the matching "type" - a bank created for "Quiz" can only be referenced from a Quiz, never a Poll, and vice versa. A bank lives in one project and can only be referenced from Riddles of that same project, so pass the projectId of the project the Riddle belongs to; omitting it creates the bank in the project the API key is scoped to. Needs full access: riddle://reference/concepts/access.
question_bank_deleteBeschreibung, Titel, Eingabeschema und HinweiseVorherDeletes a question bank
or ONE of its items - "target" says which,andnothing else deletes either. target "bank" removes the bank andevery item it holds (its tags cleaned up exactly asquestion_bank_tag(action: "remove") does), andisrejectedwith QUESTION_BANK_INTERDEPENDENCY while a Riddle of the bank's own project still references it - counting the DRAFT and, on a published Riddle, the live version too, so a block removed from a draft does not release the bank until that Riddle is republished; read "deletingABank" in riddle://reference/question-bank/overview before deleting one.target "item" takes questionBankItemId and touches nothing else: on a never-published item the delete is immediate and permanent, on a published one it only leaves the DRAFT - a live Riddle keeps drawing that item until question_bank_manage(action: "publish") purges it, and question_bank_discard_changes brings it back until then. Both are permanent for the caller:there is no trash and no restore.Reject…NachherDeletes a question bank and every item it holds (its tags cleaned up exactly as question_bank_tag_remove does) - one item alone is question_bank_item_delete. Rejected with QUESTION_BANK_INTERDEPENDENCY while a Riddle of the bank's own project still references it - counting the DRAFT and, on a published Riddle, the live version too, so a block removed from a draft does not release the bank until that Riddle is republished; read "deletingABank" in riddle://reference/question-bank/overview before deleting one. Permanent: there is no trash and no restore. Rejected for a public template id - a template is copied with question_bank_duplicate, never deleted. Needs full access: riddle://reference/concepts/access.
Titel
VorherDelete question bank
or itemNachherDelete question bank
- Entfernte Parameter:
targetquestionBankItemId - Nicht mehr Pflicht:
target - Beschreibung von
questionBankIdVorherThe ID of the question bank to
delete, or of the bank the item belongs to.NachherThe ID of the question bank to delete.
- Entfernte Parameter:
question_bank_discard_changesBeschreibungVorherThrows away every unpublished change to a question bank's items at once, resetting each of them to its last published content. Irreversible - there is no undo and no copy of the discarded draft. A pending item delete comes back; an item ADDED since the last publish has no published state and is left alone, so this is not "restore the bank as it was published". Only items are affected: the title and the notes are metadata outside the draft/publish split and never change here. Read the two sides before calling - question_bank_get_items reads the draft, the same call with published: true reads exactly the state this resets to - and prefer
question_bank_manage(action: "publish")whenever the draft is what should survive. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.NachherThrows away every unpublished change to a question bank's items at once, resetting each of them to its last published content. Irreversible - there is no undo and no copy of the discarded draft. A pending item delete comes back; an item ADDED since the last publish has no published state and is left alone, so this is not "restore the bank as it was published". Only items are affected: the title and the notes are metadata outside the draft/publish split and never change here. Read the two sides before calling - question_bank_get_items reads the draft, the same call with published: true reads exactly the state this resets to - and prefer question_bank_publish whenever the draft is what should survive. Rejected for a public template id. Needs full access: riddle://reference/concepts/access.
question_bank_getBeschreibungVorherRetrieves one question bank by id: title, riddleType, tags, notes, its categories/blockTypes and whether it has unpublished changes. The items themselves are question_bank_get_items, not included here. Works on a built-in template id from question_bank_list(scope: "templates") to see what it holds before duplicating - a template reads back without owner and tags/notes, belonging to nobody. "categories" and "blockTypeCategoryMap" are different slices and can disagree: "categories" comes from every DRAFT item, while "blockTypeCategoryMap" (categories per blockType) counts only PUBLISHED ones - a category used only by unpublished items is in "categories" but missing for its blockType there until
question_bank_manage(action: "publish").NachherRetrieves one question bank by id: title, riddleType, tags, notes, its categories/blockTypes and whether it has unpublished changes. The items themselves are question_bank_get_items, not included here. Works on a built-in template id from question_bank_list(scope: "templates") to see what it holds before duplicating - a template reads back without owner and tags/notes, belonging to nobody. "categories" and "blockTypeCategoryMap" are different slices and can disagree: "categories" comes from every DRAFT item, while "blockTypeCategoryMap" (categories per blockType) counts only PUBLISHED ones - a category used only by unpublished items is in "categories" but missing for its blockType there until question_bank_publish.
question_bank_listBeschreibungVorherLists question banks. Scope "own" (the default) lists the banks of a project - the same ones the Creator shows; pass a projectId to look into another project, omit it for the project the API key is scoped to (your personal ones on a user API key). Paginated {items, page, pageSize, total, hasMore}. Scope "templates" lists the built-in starter banks instead - pre-filled banks anyone can copy with
question_bank_manage(action: "duplicate")to get real content immediately instead of starting empty. It takes riddleType and nothing else (a handful of them, nothing to page or search) and answers with id, title, PUBLISHED "itemCount", DRAFT "draftItemCount", which blockTypes those items are (null when that cannot be told yet) and a few example categories out of "categoryCount". A template that was never published reports "itemCount": 0 however many questions it holds - judge its real size by "draftItemCount", the number a duplicate would give you, and read the chosen id withquestion_bank_get…NachherLists question banks. Scope "own" (the default) lists the banks of a project - the same ones the Creator shows; pass a projectId to look into another project, omit it for the project the API key is scoped to (your personal ones on a user API key). Paginated {items, page, pageSize, total, hasMore}. Scope "templates" lists the built-in starter banks instead - pre-filled banks anyone can copy with question_bank_duplicate to get real content immediately instead of starting empty. It takes riddleType and nothing else (a handful of them, nothing to page or search) and answers with id, title, PUBLISHED "itemCount", DRAFT "draftItemCount", which blockTypes those items are (null when that cannot be told yet) and a few example categories out of "categoryCount". A template that was never published reports "itemCount": 0 however many questions it holds - judge its real size by "draftItemCount", the number a duplicate would give you, and read the chosen id with question_bank_get and question_bank_…
reference_getHinweiseidempotentHintnicht angegeben wird zu ja
riddle_builder_createHinweiseopenWorldHintnein wird zu ja
riddle_builder_updateHinweisedestructiveHintnein wird zu jaopenWorldHintnein wird zu ja
riddle_builder_validateHinweiseopenWorldHintnein wird zu ja
riddle_moveriddle_renameriddle_tag_deleteriddle_tag_list -
Beginn der Beobachtung: 41 Tools.
Häufige Fragen
Kann ich mcp.tc/i/riddle in meinen MCP-Client einfügen?
Nein. mcp.tc-Links sind Seiten, keine Server-Adressen. Verbinde dich mit https://www.riddle.com/creator/api/v3/mcp, damit dein Client direkt mit Riddle spricht. Das Anmelde-Token funktioniert ohnehin nur dort. Der Quick-Link ist zum Teilen da: Er öffnet diese Seite, mit Einrichtungsschritten für jeden Client.
Braucht Riddle einen API-Schlüssel oder eine Anmeldung?
Ja, du brauchst ein Konto bei Riddle. Wenn sich dein Client zum ersten Mal verbindet, öffnet er die Anmeldeseite von Riddle. Das Token geht direkt an die eigene URL des Servers, nie über mcp.tc.
Ist Riddle ein Remote- oder ein lokaler Server?
Remote. Riddle hostet ihn unter https://www.riddle.com/creator/api/v3/mcp, und er spricht Streamable HTTP. Es gibt nichts zu installieren.
Was kann Riddle?
Er hat 48 Tools, darunter media_upload_link, media_delete und riddle_template_create. Du kannst damit vorhandene Riddles in deinem Konto auflisten, Quizze, Umfragen, Formulare und Persönlichkeitstests erstellen, und bestehende Riddles bearbeiten.
Welche Clients können ihn nutzen?
Remote-MCP-Clients, die sich mit OAuth anmelden, sofern sie vorab bei Riddle registriert sind oder sich mit einem Client ID Metadata Document (CIMD) ausweisen: Riddle bietet keine offene dynamische Client-Registrierung (Dynamic Client Registration). Schau für deinen Client in die Einrichtungsanleitung von Riddle.
Verfolgt mcp.tc Änderungen an Riddle?
Ja. Der Tab Verlauf von Riddle zeigt jede Änderung, die wir an seinen Tools finden, bis hin zu Beschreibungen und Parametern, dazu neue Versionen und Änderungen seines Betreibers. Folge dem Eintrag, um eine E-Mail zu bekommen, wenn er sich ändert.
Wer hat diese Seite geschrieben?
Der Roboter von mcp.tc hat die eigenen Metadaten von Riddle (seinen MCP-Handshake, seine Tool-Liste und öffentliche Seiten) gelesen, und ein KI-Modell hat daraus den Text entworfen. Ein Mensch prüft alles, was die Prüfungen nicht bestätigen können. Der Text kann trotzdem falsch sein; wenn dir ein Fehler auffällt, nutze Eintrag melden auf dieser Seite. Diese Übersetzung hat ein KI-Modell aus dem englischen Text erstellt.
mcp.tc steht in keiner Verbindung zu Riddle. Diese Seite entstand aus den öffentlichen Metadaten von Riddle, zuletzt geprüft am 17. Nov. 2026, und ein KI-Modell hat die Beschreibung geschrieben, sie kann also Fehler enthalten. Namen und Marken gehören ihren Inhabern. Stimmt etwas nicht? Eintrag melden. Die Übersetzung hat ein KI-Modell aus dem englischen Text erstellt.