Riddle
Serveur MCP par Riddle
Créer, modifier, publier et analyser des quiz, sondages, formulaires et tests de personnalité dans Riddle depuis un chat IA.
Connecter Riddle
Riddle demande de vous identifier. Connectez votre client à son URL :
Votre client ouvre la page de connexion de Riddle la première fois. Le jeton reste entre votre client et Riddle.
Partager ce serveur
Ouvre cette page, avec l’URL et les étapes de configuration.
mcp.tc/i/riddlePrésentation
Connecte un assistant IA à l’API créateur de Riddle. Vous pouvez lister les Riddles existants, créer des quiz, sondages, formulaires et tests de personnalité, les modifier et analyser les résultats depuis un chat. Les actions disponibles via l’API Riddle peuvent être déclenchées par l’assistant.
Le serveur est hébergé à https://www.riddle.com/creator/api/v3/mcp et utilise Streamable HTTP. Un compte Riddle est requis. Les utilisateurs s’identifient avec OAuth dans le navigateur, et le jeton hérite des rôles et autorisations de projet de cet utilisateur. Une option avec clé dans l’URL existe pour les agents sans interface, mais OAuth est recommandé.
Ce que vous pouvez faire
- Lister les Riddles existants de votre compte
- Créer des quiz, sondages, formulaires et tests de personnalité
- Modifier des Riddles existants
- Analyser les résultats et statistiques des Riddles
- Se connecter avec votre propre compte Riddle via OAuth
Outils 48
media_upload_linkÉcritureCreate media upload link
media_deletePeut supprimerDelete media library file
riddle_template_createÉcritureCreate riddle template
riddle_template_updatePeut supprimerUpdate riddle template
riddle_template_listLecture seuleList riddle templates
riddle_template_public_listLecture seuleList public riddle templates
riddle_template_getLecture seuleGet riddle template
riddle_template_useÉcritureCreate riddle from template
riddle_tag_listLecture seuleList riddle tags
riddle_tag_addÉcritureAdd tag to riddles
riddle_tag_removePeut supprimerRemove tag from riddles
riddle_tag_deletePeut supprimerDelete riddle tag
Afficher 36 outils de plus
pingLecture seulePing the MCP server
riddle_listLecture seuleList riddles
riddle_getLecture seuleGet riddle
riddle_get_embed_codeLecture seuleGet riddle embed code
riddle_publishPeut supprimerPublish or unpublish riddle
riddle_renamePeut supprimerRename riddle
riddle_deletePeut supprimerDelete riddle
riddle_movePeut supprimerMove riddle to another project
whoamiLecture seuleShow the connected account
question_bank_createÉcritureCreate question bank
question_bank_listLecture seuleList question banks
question_bank_getLecture seuleGet question bank
question_bank_renamePeut supprimerRename question bank
question_bank_update_notesPeut supprimerUpdate question bank notes
question_bank_duplicateÉcritureDuplicate question bank
question_bank_publishPeut supprimerPublish question bank
question_bank_item_addÉcritureAdd question bank item
question_bank_item_updatePeut supprimerUpdate question bank item
question_bank_discard_changesPeut supprimerDiscard question bank changes
question_bank_deletePeut supprimerDelete question bank
question_bank_item_deletePeut supprimerDelete question bank item
question_bank_get_itemsLecture seuleGet question bank items
question_bank_tag_addÉcritureAdd tag to question bank
question_bank_tag_removePeut supprimerRemove tag from question bank
palette_getLecture seuleGet brand palette
palette_customizePeut supprimerCustomize brand palette
integration_listLecture seuleList integrations
riddle_builder_createÉcritureBuild a riddle
riddle_builder_updatePeut supprimerUpdate a riddle
riddle_builder_validateLecture seuleValidate a build configuration
reference_getLecture seuleGet builder reference document
stats_fetchLecture seuleFetch riddle statistics
project_listLecture seuleList projects
project_getLecture seuleGet project
project_get_settingsLecture seuleGet project settings
riddle_previewLecture seulePreview a Riddle
Lus directement sur le serveur le 17 nov. 2026. Lecture seule, Écriture et Peut supprimer sont des indications déclarées par le serveur ; c’est votre client qui décide de vous demander confirmation avant d’exécuter un outil.
Exemples de prompts
Liste mes Riddles les plus récents.
Crée un quiz de cinq questions sur les capitales européennes.
Crée un test de personnalité avec trois pages de résultats.
Montre les statistiques de mon dernier sondage.
Configuration
Chaque client se connecte à riddle.com, et Riddle vous demande de vous identifier la première fois. Choisissez le vôtre ; la page retient votre choix.
Claude Code
- Lancez ceci dans un terminal, dans le dossier de votre projet :
claude mcp add --transport http riddle https://www.riddle.com/creator/api/v3/mcp- Démarrez Claude Code, tapez
/mcp, choisissez riddle puis Authenticate. Une fenêtre de navigateur s’ouvre pour la connexion à Riddle.
Ajoutez --scope user pour le rendre disponible dans tous vos projets, pas seulement celui-ci.
Claude Desktop
- Ouvrez Customize → Connectors, cliquez sur + Add, puis sur Add custom connector.
- Nommez-le Riddle et collez cette URL :
https://www.riddle.com/creator/api/v3/mcp- Cliquez sur Add, puis sur Connect, et connectez-vous quand Riddle le demande.
Le fichier de configuration JSON de Claude Desktop ne lance que des serveurs locaux. Les serveurs distants passent par les Connectors, et les connecteurs ajoutés sur claude.ai apparaissent aussi ici.
claude.ai
- Ouvrez le formulaire des connecteurs sur claude.ai. Ce bouton remplit le nom et l’URL pour vous :
Ajouter à claude.ai (s’ouvre dans un nouvel onglet)
- Vérifiez que l’URL est
https://www.riddle.com/creator/api/v3/mcpet cliquez sur Add. - Cliquez sur Connect et connectez-vous quand Riddle le demande.
Les offres gratuites permettent un connecteur personnalisé. Sur les offres Team et Enterprise, un propriétaire l’ajoute dans Organization settings → Connectors.
ChatGPT
- Sur chatgpt.com, allez dans Plugins, sélectionnez +, puis Add custom MCP server.
- Saisissez un nom pour le serveur.
- Dans Connection, collez
https://www.riddle.com/creator/api/v3/mcpcomme URL du serveur, puis pour l’authentification choisissez OAuth. ChatGPT vous envoie chez Riddle pour vous connecter. - Cochez I understand and want to continue, puis sélectionnez Create as a plugin.
La possibilité d’ajouter un serveur MCP personnalisé dépend de votre forfait ChatGPT et des autorisations de votre espace de travail (dans les espaces Business, les administrateurs et les propriétaires le peuvent).
Cursor
Ajouter à Cursor (s’ouvre dans un nouvel onglet)
Ou ajoutez-le à la main dans ~/.cursor/mcp.json (tous les projets) ou .cursor/mcp.json (ce projet) :
{
"mcpServers": {
"riddle": {
"url": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}Cursor affiche Needs authentication à côté du serveur. Cliquez sur le bouton juste à côté pour vous connecter.
VS Code
Installer dans VS Code (s’ouvre dans un nouvel onglet)
Ou depuis un terminal :
code --add-mcp '{"name":"riddle","type":"http","url":"https://www.riddle.com/creator/api/v3/mcp"}'Ou committez-le dans le dépôt, dans .vscode/mcp.json :
{
"servers": {
"riddle": {
"type": "http",
"url": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}VS Code vous demande de vous connecter au premier démarrage du serveur.
Devin Desktop
- Ajoutez-le à
~/.config/devin/mcp_config.json(macOS et Linux) ou%APPDATA%\devin\mcp_config.json(Windows) :
{
"mcpServers": {
"riddle": {
"serverUrl": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}- Actualisez la liste des serveurs MCP dans Cascade et connectez-vous quand c’est demandé.
Devin Desktop est le nouveau nom de Windsurf. Pour les serveurs distants, il lit serverUrl (ou url).
Codex
codex mcp add riddle --url https://www.riddle.com/creator/api/v3/mcp
codex mcp login riddleOu modifiez directement ~/.codex/config.toml :
[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/mcpPuis, dans Gemini CLI, lancez /mcp auth riddle pour vous connecter.
Cela l’ajoute au projet en cours. Ajoutez -s user pour l’utiliser partout.
Tout client
La plupart des clients acceptent cette forme. Certains nomment autrement le champ de l’URL : serverUrl dans Devin Desktop, httpUrl dans le fichier de réglages de Gemini CLI.
{
"mcpServers": {
"riddle": {
"type": "http",
"url": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}Zed place les serveurs sous context_servers dans ses réglages. Cline a besoin de "type": "streamableHttp", sinon il suppose SSE.
Votre client ne lance que des serveurs locaux ? Reliez-le avec npx -y mcp-remote https://www.riddle.com/creator/api/v3/mcp.
Intégrer
Affichez Riddle dans un README ou sur votre site. Chaque intégration renvoie à cette page, utilise l’URL du serveur et ne dépose aucun cookie. Comment fonctionnent les intégrations
La carte, l’iframe et le JSON sont en anglais. Ajoutez ?lang=it, fr, de ou es à leur adresse pour une autre langue.
Badge pour README
[](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>Il suit le mode clair ou sombre du lecteur. Ajoutez ?theme=light ou ?theme=dark pour le fixer, ou ?style=compact pour afficher le symbole sans le nom.
Carte pour site web
<script src="https://mcp.tc/w/riddle.js" async></script>La carte apparaît à l’endroit de la balise. Ajoutez data-theme="dark" ou data-size="compact" à la balise pour la modifier. Le fichier contient tout ce qu’il lui faut : il ne fait aucune autre requête et ne dépose aucun cookie.
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>Utilisez-la sur les pages qui n’autorisent pas les scripts. Ajoutez ?theme=light ou ?theme=dark à l’adresse pour fixer les couleurs.
JSON
La fiche sous forme de données pour vos pages et vos outils : nom, accroche, URL du serveur, outils et liens « Add to ». N’importe quel site peut la lire (CORS ouvert).
https://mcp.tc/i/riddle.jsonPrompt pour l’IA
Collez-le dans un assistant de code IA, comme Claude Code ou Cursor, et il ajoutera la carte de Riddle à votre site.
Ajoute à mon site la carte mcp.tc de Riddle, un serveur MCP. C’est un seul script statique : pas de build, aucun paquet à installer, aucun cookie.
Place cette balise là où la carte doit apparaître. La carte s’affiche juste avant elle :
```html
<script src="https://mcp.tc/w/riddle.js" async></script>
```
Pour l’afficher ailleurs, mets ce conteneur à cet endroit et charge le même script une seule fois, par exemple avant `</body>`. Garde le lien à l’intérieur : les visiteurs sans JavaScript le voient.
```html
<div data-mcptc="riddle"><a href="https://mcp.tc/i/riddle">Riddle on mcp.tc</a></div>
```
Options :
- `data-theme="light"` ou `"dark"` sur la balise ou le conteneur fixe les couleurs. Sans cela, la carte suit le mode clair ou sombre du visiteur.
- `data-size="compact"` donne une carte plus petite, sans l’accroche.
- La variable CSS `--mcptc-max-width` sur le conteneur ou un parent fixe la largeur (`520px` par défaut).
- `?lang=` dans l’URL du script choisit la langue de la carte : `en`, `it`, `fr`, `de` ou `es`.
Si le site a une Content Security Policy, autorise `script-src https://mcp.tc` et `img-src data:` (l’icône est intégrée).
Pour un README ou une autre doc en Markdown, utilise plutôt le badge :
```markdown
[](https://mcp.tc/i/riddle)
```
Référence : https://mcp.tc/fr/embedHistorique des changements
Nous lisons la liste d’outils de ce serveur toutes les 3 heures et notons ce qui change. Dernière lecture : 18 nov. 2026, 05:37 UTC.
-
2 outils modifiés.
Détails, 11 nov. 2026, 14:54 UTC
Modifiés 2
riddle_builder_createschéma d’entréeriddle_builder_updateschéma d’entrée
-
2 outils modifiés.
Détails, 11 nov. 2026, 11:47 UTC
Modifiés 2
riddle_builder_createschéma d’entréeriddle_builder_updateschéma d’entrée
-
2 outils modifiés.
Détails, 2 nov. 2026, 11:51 UTC
Modifiés 2
riddle_builder_createschéma d’entréeriddle_builder_updateschéma d’entrée
-
17 outils modifiés.
Indication changée : peut modifier des données
Détails, 30 oct. 2026, 11:46 UTC
Modifiés 17
integration_listdescriptionAvantLists 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.
AprèsLists 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_deleteindicationsopenWorldHintnon devient oui
media_upload_linkindicationsopenWorldHintnon devient oui
palette_customizeindicationsdestructiveHintnon devient oui
question_bank_discard_changesindicationsidempotentHintoui devient non
question_bank_item_updateindicationsidempotentHintoui devient non
question_bank_publishdescription et indicationsAvantMakes 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.AprèsMakes 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.
openWorldHintnon devient ouiidempotentHintoui devient non
question_bank_renameindicationsdestructiveHintnon devient ouiidempotentHintoui devient non
question_bank_update_notesindicationsidempotentHintoui devient non
riddle_deleteindicationsopenWorldHintnon devient oui
riddle_get_embed_coderiddle_previewriddle_renameriddle_template_createriddle_template_updateriddle_template_usestats_fetch -
11 outils ajoutés, 4 outils retirés et 14 outils modifiés.
Indication changée : peut modifier des données, Nouvel outil indiqué comme destructif
Détails, 29 oct. 2026, 17:47 UTC
Ajoutés 11
question_bank_duplicateÉcritureCopies 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_addÉcritureAdds 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_deletePeut supprimerDeletes 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_updatePeut supprimerReplaces 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_publishPeut supprimerMakes 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_renameÉcritureSets 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_addÉcritureAdds 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_removePeut supprimerRemoves 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_notesPeut supprimerReplaces 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_addÉcriturePuts 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_removePeut supprimerTakes 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.
Retirés 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…
Modifiés 14
pingindicationsidempotentHintnon indiqué devient oui
question_bank_createdescriptionAvantCreates 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.AprèsCreates 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_deletedescription, titre, schéma d’entrée et indicationsAvantDeletes 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…AprèsDeletes 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.
titre
AvantDelete question bank
or itemAprèsDelete question bank
- Paramètres retirés :
targetquestionBankItemId - Plus obligatoires :
target - Description de
questionBankIdAvantThe ID of the question bank to
delete, or of the bank the item belongs to.AprèsThe ID of the question bank to delete.
- Paramètres retirés :
question_bank_discard_changesdescriptionAvantThrows 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.AprèsThrows 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_getdescriptionAvantRetrieves 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").AprèsRetrieves 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_listdescriptionAvantLists 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…AprèsLists 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_getindicationsidempotentHintnon indiqué devient oui
riddle_builder_createindicationsopenWorldHintnon devient oui
riddle_builder_updateindicationsdestructiveHintnon devient ouiopenWorldHintnon devient oui
riddle_builder_validateindicationsopenWorldHintnon devient oui
riddle_moveriddle_renameriddle_tag_deleteriddle_tag_list -
Début de l’observation : 41 outils.
FAQ
Puis-je coller mcp.tc/i/riddle dans mon client MCP ?
Non. Les liens mcp.tc sont des pages, pas des adresses de serveur. Connectez votre client à https://www.riddle.com/creator/api/v3/mcp, pour qu’il parle directement à Riddle. De toute façon, le jeton de connexion ne fonctionne que là. Le lien rapide sert au partage : il ouvre cette page, avec les étapes de configuration pour chaque client.
Riddle a-t-il besoin d’une clé API ou d’une connexion ?
Oui, il vous faut un compte Riddle. La première fois que votre client se connecte, il ouvre la page de connexion de Riddle. Le jeton est envoyé directement à l’URL du serveur et ne passe jamais par mcp.tc.
Riddle est-il un serveur distant ou local ?
Distant. Riddle l’héberge à https://www.riddle.com/creator/api/v3/mcp, et il utilise Streamable HTTP. Il n’y a rien à installer.
Que peut faire Riddle ?
Il a 48 outils, dont media_upload_link, media_delete et riddle_template_create. Vous pouvez lister les Riddles existants de votre compte, créer des quiz, sondages, formulaires et tests de personnalité et modifier des Riddles existants.
Quels clients peuvent l’utiliser ?
Les clients MCP distants qui se connectent avec OAuth, à condition d’être enregistrés auprès de Riddle à l’avance ou de s’identifier avec un Client ID Metadata Document (CIMD) : Riddle ne propose pas l’enregistrement dynamique ouvert des clients (Dynamic Client Registration). Consultez le guide de configuration de Riddle pour votre client.
mcp.tc suit-il les changements de Riddle ?
Oui. L’onglet Historique de Riddle montre chaque changement que nous trouvons dans ses outils, jusqu’aux descriptions et aux paramètres, ainsi que les nouvelles versions et les modifications de son propriétaire. Suivez la fiche pour recevoir un e-mail quand elle change.
Qui a rédigé cette page ?
Le robot de mcp.tc a lu les métadonnées de Riddle (son handshake MCP, sa liste d’outils et ses pages publiques), et un modèle d’IA en a tiré le texte. Une personne examine tout ce que les vérifications ne peuvent pas confirmer. Le texte peut encore contenir des erreurs : si vous en repérez une, utilisez Signaler cette fiche sur cette page. Cette traduction a été réalisée par un modèle d’IA à partir du texte anglais.
mcp.tc n’est pas affilié à Riddle. Cette page a été construite à partir des métadonnées publiques de Riddle, vérifiées pour la dernière fois le 17 nov. 2026, et un modèle d’IA a rédigé la description : elle peut contenir des erreurs. Les noms et marques appartiennent à leurs propriétaires. Quelque chose cloche ? Signaler cette fiche. La traduction a été réalisée par un modèle d’IA à partir du texte anglais.