Riddle
Servidor MCP de Riddle
Crea, edita, publica y analiza cuestionarios, encuestas, formularios y tests de personalidad en Riddle desde un chat de IA.
Conectar con Riddle
Riddle requiere iniciar sesión. Conéctate con su propia URL:
La primera vez, tu cliente abre la página de inicio de sesión de Riddle. El token queda entre tu cliente y Riddle.
Compartir este servidor
El enlace abre esta página, con la URL y los pasos de configuración.
mcp.tc/i/riddleDescripción
Conecta un asistente de IA a la API de creadores de Riddle. Puedes listar Riddles existentes, crear nuevos cuestionarios, encuestas, formularios y tests de personalidad, editarlos y analizar los resultados desde un chat. Las acciones disponibles en la API de Riddle se pueden activar a través del asistente.
El servidor está alojado en https://www.riddle.com/creator/api/v3/mcp y usa Streamable HTTP. Se requiere una cuenta de Riddle. Los usuarios inician sesión con OAuth en el navegador, y el token hereda los roles y permisos de proyecto de ese usuario. Existe una opción con clave en la URL para agentes sin interfaz, pero se recomienda OAuth.
Qué puedes hacer
- Listar los Riddles existentes en tu cuenta
- Crear cuestionarios, encuestas, formularios y tests de personalidad
- Editar Riddles existentes
- Analizar los resultados y estadísticas de los Riddles
- Iniciar sesión con tu propia cuenta de Riddle mediante OAuth
Herramientas 48
media_upload_linkEscrituraCreate media upload link
media_deletePuede borrarDelete media library file
riddle_template_createEscrituraCreate riddle template
riddle_template_updatePuede borrarUpdate riddle template
riddle_template_listSolo lecturaList riddle templates
riddle_template_public_listSolo lecturaList public riddle templates
riddle_template_getSolo lecturaGet riddle template
riddle_template_useEscrituraCreate riddle from template
riddle_tag_listSolo lecturaList riddle tags
riddle_tag_addEscrituraAdd tag to riddles
riddle_tag_removePuede borrarRemove tag from riddles
riddle_tag_deletePuede borrarDelete riddle tag
Mostrar 36 herramientas más
pingSolo lecturaPing the MCP server
riddle_listSolo lecturaList riddles
riddle_getSolo lecturaGet riddle
riddle_get_embed_codeSolo lecturaGet riddle embed code
riddle_publishPuede borrarPublish or unpublish riddle
riddle_renamePuede borrarRename riddle
riddle_deletePuede borrarDelete riddle
riddle_movePuede borrarMove riddle to another project
whoamiSolo lecturaShow the connected account
question_bank_createEscrituraCreate question bank
question_bank_listSolo lecturaList question banks
question_bank_getSolo lecturaGet question bank
question_bank_renamePuede borrarRename question bank
question_bank_update_notesPuede borrarUpdate question bank notes
question_bank_duplicateEscrituraDuplicate question bank
question_bank_publishPuede borrarPublish question bank
question_bank_item_addEscrituraAdd question bank item
question_bank_item_updatePuede borrarUpdate question bank item
question_bank_discard_changesPuede borrarDiscard question bank changes
question_bank_deletePuede borrarDelete question bank
question_bank_item_deletePuede borrarDelete question bank item
question_bank_get_itemsSolo lecturaGet question bank items
question_bank_tag_addEscrituraAdd tag to question bank
question_bank_tag_removePuede borrarRemove tag from question bank
palette_getSolo lecturaGet brand palette
palette_customizePuede borrarCustomize brand palette
integration_listSolo lecturaList integrations
riddle_builder_createEscrituraBuild a riddle
riddle_builder_updatePuede borrarUpdate a riddle
riddle_builder_validateSolo lecturaValidate a build configuration
reference_getSolo lecturaGet builder reference document
stats_fetchSolo lecturaFetch riddle statistics
project_listSolo lecturaList projects
project_getSolo lecturaGet project
project_get_settingsSolo lecturaGet project settings
riddle_previewSolo lecturaPreview a Riddle
Leídas del servidor en funcionamiento el 17 nov 2026. Solo lectura, Escritura y Puede borrar son indicaciones que declara el servidor; tu cliente decide si te pregunta antes de ejecutar una herramienta.
Prompts de ejemplo
Lista mis Riddles más recientes.
Crea un cuestionario de cinco preguntas sobre capitales europeas.
Crea un test de personalidad con tres páginas de resultados.
Muestra las estadísticas de mi última encuesta.
Configuración
Todos los clientes se conectan a riddle.com, y la primera vez Riddle te pide que inicies sesión. Elige el tuyo; la página recuerda tu elección.
Claude Code
- Ejecútalo en un terminal, en la carpeta de tu proyecto:
claude mcp add --transport http riddle https://www.riddle.com/creator/api/v3/mcp- Inicia Claude Code, escribe
/mcp, elige riddle y selecciona Authenticate. Se abre una ventana del navegador para iniciar sesión en Riddle.
Añade --scope user para que esté disponible en todos los proyectos, no solo en este.
Claude Desktop
- Abre Customize → Connectors, haz clic en + Add y luego en Add custom connector.
- Llámalo Riddle y pega esta URL:
https://www.riddle.com/creator/api/v3/mcp- Haz clic en Add, luego en Connect, e inicia sesión cuando te lo pida Riddle.
El archivo de configuración JSON de Claude Desktop solo inicia servidores locales. Los servidores remotos van por Connectors, y los conectores que añades en claude.ai también aparecen aquí.
claude.ai
- Abre el formulario de conectores en claude.ai. Este botón rellena el nombre y la URL por ti:
Añadir a claude.ai (se abre en una pestaña nueva)
- Comprueba que la URL es
https://www.riddle.com/creator/api/v3/mcpy haz clic en Add. - Haz clic en Connect e inicia sesión cuando te lo pida Riddle.
Los planes gratuitos permiten un conector personalizado. En los planes Team y Enterprise lo añade un propietario en Organization settings → Connectors.
ChatGPT
- En chatgpt.com, ve a Plugins, selecciona + y luego Add custom MCP server.
- Escribe un nombre para el servidor.
- En Connection, pega
https://www.riddle.com/creator/api/v3/mcpcomo URL del servidor y luego, como autenticación, elige OAuth. ChatGPT te envía a Riddle para iniciar sesión. - Marca I understand and want to continue y luego selecciona Create as a plugin.
Poder añadir un servidor MCP personalizado depende de tu plan de ChatGPT y de los permisos de tu espacio de trabajo (en los espacios Business pueden hacerlo los administradores y los propietarios).
Cursor
Añadir a Cursor (se abre en una pestaña nueva)
O añádelo a mano en ~/.cursor/mcp.json (todos los proyectos) o en .cursor/mcp.json (este proyecto):
{
"mcpServers": {
"riddle": {
"url": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}Cursor muestra Needs authentication junto al servidor. Haz clic en el botón de al lado para iniciar sesión.
VS Code
Instalar en VS Code (se abre en una pestaña nueva)
O desde un terminal:
code --add-mcp '{"name":"riddle","type":"http","url":"https://www.riddle.com/creator/api/v3/mcp"}'O haz commit del archivo en el repositorio como .vscode/mcp.json:
{
"servers": {
"riddle": {
"type": "http",
"url": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}VS Code te pide iniciar sesión la primera vez que se inicia el servidor.
Devin Desktop
- Añádelo a
~/.config/devin/mcp_config.json(macOS y Linux) o a%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"riddle": {
"serverUrl": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}- Actualiza la lista de servidores MCP en Cascade e inicia sesión cuando te lo pida.
Devin Desktop es el nuevo nombre de Windsurf. Para los servidores remotos lee serverUrl (o url).
Codex
codex mcp add riddle --url https://www.riddle.com/creator/api/v3/mcp
codex mcp login riddleO edita directamente ~/.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/mcpDespués, dentro de Gemini CLI, ejecuta /mcp auth riddle para iniciar sesión.
Así lo añades al proyecto actual. Añade -s user para usarlo en todas partes.
Cualquier cliente
La mayoría de los clientes aceptan esta forma. Algunos llaman de otra manera al campo de la URL: serverUrl en Devin Desktop, httpUrl en el archivo de ajustes de Gemini CLI.
{
"mcpServers": {
"riddle": {
"type": "http",
"url": "https://www.riddle.com/creator/api/v3/mcp"
}
}
}Zed pone los servidores bajo context_servers en sus ajustes. Cline necesita "type": "streamableHttp"; si no, supone SSE.
¿Tu cliente solo inicia servidores locales? Conéctalo con npx -y mcp-remote https://www.riddle.com/creator/api/v3/mcp.
Insertar
Muestra Riddle en un README o en tu web. Cada inserción enlaza a esta página, usa la URL propia del servidor y no instala cookies. Cómo funcionan las inserciones
La tarjeta, el iframe y el JSON están en inglés. Añade ?lang=it, fr, de o es a su dirección para otro idioma.
Insignia para 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>Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.
Tarjeta para web
<script src="https://mcp.tc/w/riddle.js" async></script>La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala 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>Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.
JSON
La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, la URL propia del servidor, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).
https://mcp.tc/i/riddle.jsonPrompt para la IA
Pégalo en un asistente de programación con IA, como Claude Code o Cursor, y añadirá la tarjeta de Riddle a tu web.
Añade a mi web la tarjeta de mcp.tc de Riddle, un servidor MCP. Es un solo script estático: sin paso de build, sin paquetes que instalar, sin cookies.
Pon esta etiqueta donde deba aparecer la tarjeta. La tarjeta se muestra justo antes de ella:
```html
<script src="https://mcp.tc/w/riddle.js" async></script>
```
Para mostrarla en otro sitio, pon allí este marcador y carga el mismo script una sola vez, por ejemplo antes de `</body>`. Deja el enlace dentro: lo ven los visitantes sin JavaScript.
```html
<div data-mcptc="riddle"><a href="https://mcp.tc/i/riddle">Riddle on mcp.tc</a></div>
```
Opciones:
- `data-theme="light"` o `"dark"` en la etiqueta o el marcador fija los colores. Sin él, la tarjeta sigue el modo claro u oscuro del visitante.
- `data-size="compact"` da una tarjeta más pequeña, sin el eslogan.
- La variable CSS `--mcptc-max-width` en el marcador o en un elemento padre fija el ancho (por defecto `520px`).
- `?lang=` en la URL del script fija el idioma de la tarjeta: `en`, `it`, `fr`, `de` o `es`.
Si el sitio tiene una Content Security Policy, permite `script-src https://mcp.tc` e `img-src data:` (el icono va incrustado).
Para un README u otra documentación en Markdown, usa la insignia:
```markdown
[](https://mcp.tc/i/riddle)
```
Referencia: https://mcp.tc/es/embedHistorial de cambios
Leemos la lista de herramientas de este servidor cada 3 horas y registramos lo que cambia. Última lectura: 18 nov 2026, 05:37 UTC.
-
2 herramientas cambiadas.
Detalles, 11 nov 2026, 14:54 UTC
Cambiadas 2
riddle_builder_createesquema de entradariddle_builder_updateesquema de entrada
-
2 herramientas cambiadas.
Detalles, 11 nov 2026, 11:47 UTC
Cambiadas 2
riddle_builder_createesquema de entradariddle_builder_updateesquema de entrada
-
2 herramientas cambiadas.
Detalles, 2 nov 2026, 11:51 UTC
Cambiadas 2
riddle_builder_createesquema de entradariddle_builder_updateesquema de entrada
-
17 herramientas cambiadas.
Indicación cambiada: puede modificar datos
Detalles, 30 oct 2026, 11:46 UTC
Cambiadas 17
integration_listdescripciónAntesLists 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.
Despué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_deleteindicacionesopenWorldHintno pasa a sí
media_upload_linkindicacionesopenWorldHintno pasa a sí
palette_customizeindicacionesdestructiveHintno pasa a sí
question_bank_discard_changesindicacionesidempotentHintsí pasa a no
question_bank_item_updateindicacionesidempotentHintsí pasa a no
question_bank_publishdescripción y indicacionesAntesMakes 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.Despué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.
openWorldHintno pasa a síidempotentHintsí pasa a no
question_bank_renameindicacionesdestructiveHintno pasa a síidempotentHintsí pasa a no
question_bank_update_notesindicacionesidempotentHintsí pasa a no
riddle_deleteindicacionesopenWorldHintno pasa a sí
riddle_get_embed_coderiddle_previewriddle_renameriddle_template_createriddle_template_updateriddle_template_usestats_fetch -
11 herramientas añadidas, 4 herramientas eliminadas y 14 herramientas cambiadas.
Indicación cambiada: puede modificar datos, Herramienta nueva marcada como destructiva
Detalles, 29 oct 2026, 17:47 UTC
Añadidas 11
question_bank_duplicateEscrituraCopies 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_addEscrituraAdds 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_deletePuede borrarDeletes 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_updatePuede borrarReplaces 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_publishPuede borrarMakes 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_renameEscrituraSets 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_addEscrituraAdds 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_removePuede borrarRemoves 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_notesPuede borrarReplaces 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_addEscrituraPuts 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_removePuede borrarTakes 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.
Eliminadas 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…
Cambiadas 14
pingindicacionesidempotentHintsin indicar pasa a sí
question_bank_createdescripciónAntesCreates 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.Despué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_deletedescripción, título, esquema de entrada y indicacionesAntesDeletes 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…Despué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.
título
AntesDelete question bank
or itemDespuésDelete question bank
- Parámetros eliminados:
targetquestionBankItemId - Ya no obligatorios:
target - Descripción de
questionBankIdAntesThe ID of the question bank to
delete, or of the bank the item belongs to.DespuésThe ID of the question bank to delete.
- Parámetros eliminados:
question_bank_discard_changesdescripciónAntesThrows 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.Despué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_getdescripciónAntesRetrieves 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").Despué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_listdescripciónAntesLists 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…Despué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_getindicacionesidempotentHintsin indicar pasa a sí
riddle_builder_createindicacionesopenWorldHintno pasa a sí
riddle_builder_updateindicacionesdestructiveHintno pasa a síopenWorldHintno pasa a sí
riddle_builder_validateindicacionesopenWorldHintno pasa a sí
riddle_moveriddle_renameriddle_tag_deleteriddle_tag_list -
Inicio del seguimiento: 41 herramientas.
Preguntas frecuentes
¿Puedo pegar mcp.tc/i/riddle en mi cliente MCP?
No. Los enlaces de mcp.tc son páginas, no direcciones de servidores. Conéctate con https://www.riddle.com/creator/api/v3/mcp, para que tu cliente hable directamente con Riddle. De todos modos, el token de inicio de sesión solo funciona ahí. El enlace rápido sirve para compartir: abre esta página, con los pasos de configuración para cada cliente.
¿Riddle necesita una clave de API o iniciar sesión?
Sí, necesitas una cuenta de Riddle. La primera vez que tu cliente se conecta, abre la página de inicio de sesión de Riddle. El token va directamente a la URL propia del servidor, nunca a través de mcp.tc.
¿Riddle es un servidor remoto o local?
Remoto. Lo aloja Riddle en https://www.riddle.com/creator/api/v3/mcp, y usa Streamable HTTP. No hay nada que instalar.
¿Qué puede hacer Riddle?
Tiene 48 herramientas, entre ellas media_upload_link, media_delete y riddle_template_create. Puedes listar los Riddles existentes en tu cuenta, crear cuestionarios, encuestas, formularios y tests de personalidad y editar Riddles existentes.
¿Qué clientes pueden usarlo?
Los clientes MCP remotos que inician sesión con OAuth, siempre que estén registrados en Riddle de antemano o se identifiquen con un Client ID Metadata Document (CIMD): Riddle no ofrece el registro dinámico abierto de clientes (Dynamic Client Registration). Consulta la guía de configuración de Riddle para tu cliente.
¿mcp.tc sigue los cambios de Riddle?
Sí. La pestaña Historial de Riddle muestra cada cambio que encontramos en sus herramientas, hasta las descripciones y los parámetros, además de las versiones nuevas y las ediciones de su responsable. Sigue la ficha para recibir un correo cuando cambie.
¿Quién escribió esta página?
El robot de mcp.tc leyó los metadatos propios de Riddle (su handshake MCP, su lista de herramientas y sus páginas públicas), y un modelo de IA redactó el texto a partir de ellos. Una persona revisa todo lo que las comprobaciones no pueden confirmar. Aun así, el texto puede contener errores, así que si encuentras uno, usa Reportar esta ficha en esta página. Esta traducción la hizo un modelo de IA a partir del texto en inglés.
mcp.tc no tiene relación con Riddle. Esta página se creó a partir de los metadatos públicos de Riddle, comprobados por última vez el 17 nov 2026, y un modelo de IA escribió la descripción, así que puede contener errores. Los nombres y marcas pertenecen a sus titulares. ¿Algo no cuadra? Reportar esta ficha. La traducción la hizo un modelo de IA a partir del texto en inglés.