このMCPでできること
Creates, publishes, and analyzes scored forms and quizzes with branching screen logic, response collection, and CSV export.
機能
ツール
10
ツール
foxform_create_form
Create a FoxForm form
Create a new form, including per-screen conditional logic. Requires a WRITE-scoped API key.
Args:
- title (string): form title (required)
- description (string, optional)
- theme (string, optional): one of midnight|ocean|sunset|forest|lavender|minimal (default sunset = Ember)
- questions (array, optional): array of screen objects ({ id, type, title, required, variableName?, choices?, logic?, ... }); omit to start empty
- thank_you_message (string, optional)
- format ('single_question' | 'single_page' | 'chatbot', optional): how the form is presented (see below)
- sections (array, optional): single_page page groups, [{ id }]
- chatbot_skin ('instagram' | 'whatsapp', optional): chatbot chrome
- chatbot_profile (object, optional): chatbot header profile ({ name, handle, followers_text, phone, status, verified, avatar_url })
Returns: { form } with the created form (including its id and slug). The form starts as a draft — call foxform_publish_form to make it live.
Screen fields are validated: unknown fields are REJECTED instead of being stored and ignored, and branching rules are cross-checked against the screen ids in the same payload.
Form format (DEVF-296 / DEVF-322): pass `format` to choose how the form is presented.
- 'single_question' (default): one screen at a time (classic).
- 'single_page': every screen on one scrollable page. Optionally group screens into pages with `sections`: `[{ id }]` in order (the 'Section N' label comes from position; no editable title).
- 'chatbot': an Instagram/WhatsApp DM-style conversation. Set `chatbot_skin` ('instagram' | 'whatsapp', default instagram) and `chatbot_profile` (all fields optional, each with a fallback). The question/branching engine is unchanged — only the presentation differs.
These fields require the account's form-format feature to be enabled (live in production); when off the API ignores them and the form stays single_question.
CONDITIONAL LOGIC (branching), per screen — stored in `questions[].logic`:
logic.conditionalNavigationV2 = {
enabled: true,
groups: [ // groups are OR-joined; FIRST matching group wins
{
id: "grp-1",
conditions: [ // conditions inside a group are AND-joined
{ id: "cond-1", left: "{{quer_testar}}", operator: "equal_to", right: "Ainda não" }
],
then: { type: "specific_screen", targetScreenId: "s-motivos" }
}
]
}
- `then.type`: 'next_screen' | 'previous_screen' | 'specific_screen' (needs targetScreenId = another screen's `id`) | 'end_form'.
Add `then.url` (+ optional `openNewTab`) to redirect to an external URL instead.
- `operator`: 'equal_to' | 'not_equal_to' | 'greater_than' | 'greater_or_equal_than' | 'less_than' | 'less_or_equal_than' | 'contains'.
- `left`/`right` are EXPRESSION strings: a literal ("10", "Ainda não"), a variable ("{{score}}", "{{minha_var}}" = the screen's `variableName`), or arithmetic ("calc({{peso}}/(({{altura}}/100)*({{altura}}/100)))").
- Comparing an ANSWER: use `left: "{{<variableName of the deciding screen>}}"` and `right` = the option's `label` OR its `value` (both match).
- `{{score}}` is the running sum of `points` on the options picked so far (`choices[].points`, `images[].points`) — that is how score-based branching works.
- A navigation group with no conditions NEVER matches. `enabled: false` stores the rules but disables them.
- Screen-level conditional display uses the same group shape: `logic.display = { enabled: true, groups: [...], showAfterSeconds?: n }` (`then` is ignored — THEN means "show").
- Other logic keys: `logic.autoAdvance = { enabled, delaySeconds? }`, `logic.navigationBehavior = { onButtonClick?, onAutoAdvance?, targetScreenId? }`.
- `logic.conditionalNavigation` (legacy, pre-DEVF-161) is still read and migrated on load — don't author new rules with it.
Unknown fields are REJECTED (they used to be stored and silently ignored): `logic` as an array, or `rules`/`branching`/`conditions`/`goto`/`jump`/`nextScreen` anywhere, are not read by any renderer.
外部アクセスあり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['title'], 'properties': {'theme': {'type': 'string', 'description': 'Theme key (default sunset/Ember)'}, 'title': {'type': 'string', 'maxLength': 255, 'minLength': 1, 'description': 'Form title'}, 'format': {'enum': ['single_question', 'single_page', 'chatbot'], 'type': 'string', 'description': "Form format: 'single_question' (default — one screen at a time), 'single_page' (all screens on one scrollable page, grouped by `sections`), or 'chatbot' (an Instagram/WhatsApp DM-style conversation; set `chatbot_skin` + `chatbot_profile`)."}, 'sections': {'type': 'array', 'items': {'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string'}}, 'additionalProperties': False}, 'description': "single_page only: the page groups as `[{ id }]`, in order. The 'Section N' label is derived from position; sections have no editable title."}, 'questions': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': {}}, 'description': "Screen objects; omit for an empty form. Conditional logic goes in each screen's `logic` (see the tool description)."}, 'description': {'type': 'string', 'maxLength': 2000, 'description': 'Optional description'}, 'chatbot_skin': {'enum': ['instagram', 'whatsapp'], 'type': 'string', 'description': "chatbot only: chat chrome to imitate — 'instagram' (default) or 'whatsapp'."}, 'chatbot_profile': {'type': 'object', 'properties': {'name': {'type': 'string', 'description': "Display name in the chat header (both skins; default 'Sua Marca')."}, 'phone': {'type': 'string', 'description': 'Shown phone number (WhatsApp skin only).'}, 'handle': {'type': 'string', 'description': 'Instagram @handle (Instagram skin only).'}, 'status': {'type': 'string', 'description': 'Header status line (both skins; empty on WhatsApp shows the phone).'}, 'verified': {'type': 'boolean', 'description': 'Blue verified badge (Instagram only; default true).'}, 'avatar_url': {'type': 'string', 'description': "Avatar image URL; falls back to the name's initials."}, 'followers_text': {'type': 'string', 'description': 'Free text under the name, e.g. followers/posts (Instagram only).'}}, 'description': 'chatbot only: the profile shown in the chat header.', 'additionalProperties': False}, 'thank_you_message': {'type': 'string', 'maxLength': 2000}}, 'additionalProperties': False}
foxform_export_responses
Export responses as CSV
Export all responses for a form as CSV text (one row per response, columns = questions). Large exports are truncated — use foxform_list_responses with pagination for very large datasets.
Args:
- form_id (string)
Returns: raw CSV text.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['form_id'], 'properties': {'form_id': {'type': 'string', 'minLength': 1, 'description': 'Form ID'}}, 'additionalProperties': False}
foxform_get_form
Get a FoxForm form
Fetch a single form by ID, including its full question list, per-screen conditional logic and settings.
Args:
- form_id (string): the form's ID (from foxform_list_forms)
- response_format ('markdown' | 'json')
Returns { form, public_url }: the full form object (id, title, description, slug, status, theme, questions[], thank_you_message, timestamps, plus `format` and — when set — `sections`, `chatbot_skin`, `chatbot_profile`) plus `public_url` — the public link (`https://forms.foxform.app/<slug>`), which is live only when status is 'published'. Use `public_url` verbatim; never build the URL yourself (the public domain is forms.foxform.app, not foxform.app).
Each screen in `questions[]` carries its own `logic` (branching / conditional display) and, for choice screens, `choices[]`/`images[]` with their `points` and `value`. The markdown output summarises every rule; use response_format 'json' to get the exact stored objects (that's the shape foxform_update_form expects back).
Form format (DEVF-296 / DEVF-322): pass `format` to choose how the form is presented.
- 'single_question' (default): one screen at a time (classic).
- 'single_page': every screen on one scrollable page. Optionally group screens into pages with `sections`: `[{ id }]` in order (the 'Section N' label comes from position; no editable title).
- 'chatbot': an Instagram/WhatsApp DM-style conversation. Set `chatbot_skin` ('instagram' | 'whatsapp', default instagram) and `chatbot_profile` (all fields optional, each with a fallback). The question/branching engine is unchanged — only the presentation differs.
These fields require the account's form-format feature to be enabled (live in production); when off the API ignores them and the form stays single_question.
CONDITIONAL LOGIC (branching), per screen — stored in `questions[].logic`:
logic.conditionalNavigationV2 = {
enabled: true,
groups: [ // groups are OR-joined; FIRST matching group wins
{
id: "grp-1",
conditions: [ // conditions inside a group are AND-joined
{ id: "cond-1", left: "{{quer_testar}}", operator: "equal_to", right: "Ainda não" }
],
then: { type: "specific_screen", targetScreenId: "s-motivos" }
}
]
}
- `then.type`: 'next_screen' | 'previous_screen' | 'specific_screen' (needs targetScreenId = another screen's `id`) | 'end_form'.
Add `then.url` (+ optional `openNewTab`) to redirect to an external URL instead.
- `operator`: 'equal_to' | 'not_equal_to' | 'greater_than' | 'greater_or_equal_than' | 'less_than' | 'less_or_equal_than' | 'contains'.
- `left`/`right` are EXPRESSION strings: a literal ("10", "Ainda não"), a variable ("{{score}}", "{{minha_var}}" = the screen's `variableName`), or arithmetic ("calc({{peso}}/(({{altura}}/100)*({{altura}}/100)))").
- Comparing an ANSWER: use `left: "{{<variableName of the deciding screen>}}"` and `right` = the option's `label` OR its `value` (both match).
- `{{score}}` is the running sum of `points` on the options picked so far (`choices[].points`, `images[].points`) — that is how score-based branching works.
- A navigation group with no conditions NEVER matches. `enabled: false` stores the rules but disables them.
- Screen-level conditional display uses the same group shape: `logic.display = { enabled: true, groups: [...], showAfterSeconds?: n }` (`then` is ignored — THEN means "show").
- Other logic keys: `logic.autoAdvance = { enabled, delaySeconds? }`, `logic.navigationBehavior = { onButtonClick?, onAutoAdvance?, targetScreenId? }`.
- `logic.conditionalNavigation` (legacy, pre-DEVF-161) is still read and migrated on load — don't author new rules with it.
Unknown fields are REJECTED (they used to be stored and silently ignored): `logic` as an array, or `rules`/`branching`/`conditions`/`goto`/`jump`/`nextScreen` anywhere, are not read by any renderer.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['form_id'], 'properties': {'form_id': {'type': 'string', 'minLength': 1, 'description': 'Form ID'}, 'response_format': {'enum': ['markdown', 'json'], 'type': 'string', 'default': 'markdown', 'description': "Output format: 'markdown' (human-readable) or 'json' (machine-readable)"}}, 'additionalProperties': False}
foxform_get_form_analytics
Get form analytics
Aggregated analytics for a form: overview KPIs (total responses, form views, response rate, avg response time), the responses-over-time timeline, and per-question stats.
Args:
- form_id (string)
- response_format ('markdown' | 'json')
Returns: { overview, timeline: [{date,count}], questions: [...], response_time_distribution?, views_timeline? }.
Note: form_views / response_rate are null until the form has tracked views (forward-only).
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['form_id'], 'properties': {'form_id': {'type': 'string', 'minLength': 1, 'description': 'Form ID'}, 'response_format': {'enum': ['markdown', 'json'], 'type': 'string', 'default': 'markdown', 'description': "Output format: 'markdown' (human-readable) or 'json' (machine-readable)"}}, 'additionalProperties': False}
foxform_get_response
Get a single response
Fetch one response by its ID (from foxform_list_responses).
Args:
- response_id (string)
- response_format ('markdown' | 'json')
Returns the full response object (id, form_id, answers, submitted_at, metadata).
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['response_id'], 'properties': {'response_id': {'type': 'string', 'minLength': 1, 'description': 'Response ID'}, 'response_format': {'enum': ['markdown', 'json'], 'type': 'string', 'default': 'markdown', 'description': "Output format: 'markdown' (human-readable) or 'json' (machine-readable)"}}, 'additionalProperties': False}
foxform_list_forms
List FoxForm forms
List the forms owned by the authenticated FoxForm account, newest first.
Args:
- page (number): 1-based page number (default 1)
- limit (number): page size, 1-100 (default 20)
- response_format ('markdown' | 'json'): output format (default markdown)
Returns: { total, page, limit, count, forms: [{ id, title, status, slug, public_url, questions_count, updated_at }] }
The public link of a form is `public_url` (`https://forms.foxform.app/<slug>`) — always use this exact value, do NOT build the URL yourself (the public domain is forms.foxform.app, not foxform.app). `public_url` is only live when `status` is 'published'.
Use this first to discover form IDs, then call foxform_get_form / foxform_get_form_analytics.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'page': {'type': 'integer', 'default': 1, 'minimum': 1, 'description': '1-based page number'}, 'limit': {'type': 'integer', 'default': 20, 'maximum': 100, 'minimum': 1, 'description': 'Page size (1-100)'}, 'response_format': {'enum': ['markdown', 'json'], 'type': 'string', 'default': 'markdown', 'description': "Output format: 'markdown' (human-readable) or 'json' (machine-readable)"}}, 'additionalProperties': False}
foxform_list_responses
List form responses
List submitted responses for a form, newest first.
Args:
- form_id (string): the form's ID
- page (number): 1-based page (default 1)
- limit (number): page size, 1-100 (default 20)
- response_format ('markdown' | 'json')
Returns: { total, page, limit, count, responses: [{ id, submitted_at, answers }] }.
For aggregate metrics use foxform_get_form_analytics; for a full dump use foxform_export_responses.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['form_id'], 'properties': {'page': {'type': 'integer', 'default': 1, 'minimum': 1}, 'limit': {'type': 'integer', 'default': 20, 'maximum': 100, 'minimum': 1}, 'form_id': {'type': 'string', 'minLength': 1, 'description': 'Form ID'}, 'response_format': {'enum': ['markdown', 'json'], 'type': 'string', 'default': 'markdown', 'description': "Output format: 'markdown' (human-readable) or 'json' (machine-readable)"}}, 'additionalProperties': False}
foxform_publish_form
Publish a form
Publish a form so it's live at its public URL and can accept responses. Requires a WRITE-scoped API key.
Args:
- form_id (string)
Returns: { form, public_url } — the published form (status 'published') and its live public link `https://forms.foxform.app/<slug>`. When sharing the link with the user, use `public_url` EXACTLY as returned; do NOT build the URL yourself (the public domain is forms.foxform.app, NOT foxform.app or the API/app domain). (May fail with a plan-limit error on Free accounts.)
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['form_id'], 'properties': {'form_id': {'type': 'string', 'minLength': 1, 'description': 'Form ID'}}, 'additionalProperties': False}
foxform_unpublish_form
Unpublish a form
Unpublish a form (takes it offline; stops accepting responses). Requires a WRITE-scoped API key.
Args:
- form_id (string)
Returns: a confirmation message.
破壊的操作あり
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['form_id'], 'properties': {'form_id': {'type': 'string', 'minLength': 1, 'description': 'Form ID'}}, 'additionalProperties': False}
foxform_update_form
Update a FoxForm form
Update an existing form's fields, including each screen's conditional logic (branching). Requires a WRITE-scoped API key. Only the fields you pass are changed.
Args:
- form_id (string): the form to update (required)
- title (string, optional)
- description (string, optional)
- theme (string, optional)
- questions (array, optional): replaces the FULL screen list — there is no per-screen patch. To add logic to one screen: call foxform_get_form with response_format 'json', edit that screen's `logic`, and send the whole array back.
- thank_you_message (string, optional)
- format ('single_question' | 'single_page' | 'chatbot', optional)
- sections (array, optional): single_page page groups, [{ id }]
- chatbot_skin ('instagram' | 'whatsapp', optional)
- chatbot_profile (object, optional): chatbot header profile ({ name, handle, followers_text, phone, status, verified, avatar_url })
Returns: { form } with the updated form.
Screen fields are validated: unknown fields are REJECTED instead of being stored and ignored (the API accepts arbitrary keys but no renderer reads them), `then.targetScreenId` must be the id of a screen in the same payload, and `{{variables}}` that no screen exposes come back as warnings.
Form format (DEVF-296 / DEVF-322): pass `format` to choose how the form is presented.
- 'single_question' (default): one screen at a time (classic).
- 'single_page': every screen on one scrollable page. Optionally group screens into pages with `sections`: `[{ id }]` in order (the 'Section N' label comes from position; no editable title).
- 'chatbot': an Instagram/WhatsApp DM-style conversation. Set `chatbot_skin` ('instagram' | 'whatsapp', default instagram) and `chatbot_profile` (all fields optional, each with a fallback). The question/branching engine is unchanged — only the presentation differs.
These fields require the account's form-format feature to be enabled (live in production); when off the API ignores them and the form stays single_question.
CONDITIONAL LOGIC (branching), per screen — stored in `questions[].logic`:
logic.conditionalNavigationV2 = {
enabled: true,
groups: [ // groups are OR-joined; FIRST matching group wins
{
id: "grp-1",
conditions: [ // conditions inside a group are AND-joined
{ id: "cond-1", left: "{{quer_testar}}", operator: "equal_to", right: "Ainda não" }
],
then: { type: "specific_screen", targetScreenId: "s-motivos" }
}
]
}
- `then.type`: 'next_screen' | 'previous_screen' | 'specific_screen' (needs targetScreenId = another screen's `id`) | 'end_form'.
Add `then.url` (+ optional `openNewTab`) to redirect to an external URL instead.
- `operator`: 'equal_to' | 'not_equal_to' | 'greater_than' | 'greater_or_equal_than' | 'less_than' | 'less_or_equal_than' | 'contains'.
- `left`/`right` are EXPRESSION strings: a literal ("10", "Ainda não"), a variable ("{{score}}", "{{minha_var}}" = the screen's `variableName`), or arithmetic ("calc({{peso}}/(({{altura}}/100)*({{altura}}/100)))").
- Comparing an ANSWER: use `left: "{{<variableName of the deciding screen>}}"` and `right` = the option's `label` OR its `value` (both match).
- `{{score}}` is the running sum of `points` on the options picked so far (`choices[].points`, `images[].points`) — that is how score-based branching works.
- A navigation group with no conditions NEVER matches. `enabled: false` stores the rules but disables them.
- Screen-level conditional display uses the same group shape: `logic.display = { enabled: true, groups: [...], showAfterSeconds?: n }` (`then` is ignored — THEN means "show").
- Other logic keys: `logic.autoAdvance = { enabled, delaySeconds? }`, `logic.navigationBehavior = { onButtonClick?, onAutoAdvance?, targetScreenId? }`.
- `logic.conditionalNavigation` (legacy, pre-DEVF-161) is still read and migrated on load — don't author new rules with it.
Unknown fields are REJECTED (they used to be stored and silently ignored): `logic` as an array, or `rules`/`branching`/`conditions`/`goto`/`jump`/`nextScreen` anywhere, are not read by any renderer.
破壊的操作あり
外部アクセスあり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['form_id'], 'properties': {'theme': {'type': 'string'}, 'title': {'type': 'string', 'maxLength': 255, 'minLength': 1}, 'format': {'enum': ['single_question', 'single_page', 'chatbot'], 'type': 'string', 'description': "Form format: 'single_question' (default — one screen at a time), 'single_page' (all screens on one scrollable page, grouped by `sections`), or 'chatbot' (an Instagram/WhatsApp DM-style conversation; set `chatbot_skin` + `chatbot_profile`)."}, 'form_id': {'type': 'string', 'minLength': 1, 'description': 'Form ID'}, 'sections': {'type': 'array', 'items': {'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string'}}, 'additionalProperties': False}, 'description': "single_page only: the page groups as `[{ id }]`, in order. The 'Section N' label is derived from position; sections have no editable title."}, 'questions': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': {}}, 'description': "Replaces the full screen list. Conditional logic goes in each screen's `logic` (see the tool description)."}, 'description': {'type': 'string', 'maxLength': 2000}, 'chatbot_skin': {'enum': ['instagram', 'whatsapp'], 'type': 'string', 'description': "chatbot only: chat chrome to imitate — 'instagram' (default) or 'whatsapp'."}, 'chatbot_profile': {'type': 'object', 'properties': {'name': {'type': 'string', 'description': "Display name in the chat header (both skins; default 'Sua Marca')."}, 'phone': {'type': 'string', 'description': 'Shown phone number (WhatsApp skin only).'}, 'handle': {'type': 'string', 'description': 'Instagram @handle (Instagram skin only).'}, 'status': {'type': 'string', 'description': 'Header status line (both skins; empty on WhatsApp shows the phone).'}, 'verified': {'type': 'boolean', 'description': 'Blue verified badge (Instagram only; default true).'}, 'avatar_url': {'type': 'string', 'description': "Avatar image URL; falls back to the name's initials."}, 'followers_text': {'type': 'string', 'description': 'Free text under the name, e.g. followers/posts (Instagram only).'}}, 'description': 'chatbot only: the profile shown in the chat header.', 'additionalProperties': False}, 'thank_you_message': {'type': 'string', 'maxLength': 2000}}, 'additionalProperties': False}
履歴
最近のツール変更
変更
foxform_update_form
2026年9月27日2:49
変更
foxform_create_form
2026年9月27日2:49
変更
foxform_get_form
2026年9月27日2:49
追加
foxform_unpublish_form
2026年9月17日12:53
追加
foxform_publish_form
2026年9月17日12:53
追加
foxform_update_form
2026年9月17日12:53
追加
foxform_create_form
2026年9月17日12:53
追加
foxform_export_responses
2026年9月17日12:53
追加
foxform_get_form_analytics
2026年9月17日12:53
追加
foxform_get_response
2026年9月17日12:53
追加
foxform_list_responses
2026年9月17日12:53
追加
foxform_get_form
2026年9月17日12:53
追加
foxform_list_forms
2026年9月17日12:53
関連MCP
類似のMCPサーバー
ClusterHack
dev.clusterhack/clusterhack
Supports hackathon operations including events, registrations, teams, submissions, judging, schedules, companies and leaderboards.
Fluid Recall
com.fluidrecall/mcp
Manages spaced-repetition flashcards with decks, due schedules, reviews, deadline planning, notes, exports, and optional mailbox …
getjobzi-mcp
io.github.getjobzi/getjobzi-mcp
Searches UK jobs and supports resume analysis, job matching, cover letters, career planning, skill-gap analysis, and salary bench…
ScholarNet — Study Plan & Thesis Tools
com.0xpi.scholar/study-tools
Creates study plans, thesis statements, citations, flashcards, quizzes, and tutor explanations for students.
Career Command
io.github.jgaethle10/career-command
Provides paid interview practice and career preparation, including question generation, answer evaluation, story recovery, and in…
AnkiMCP Server
ai.ankimcp/anki-mcp-server-addon
Exposes a local Anki flashcard collection to AI assistants.
Anki MCP Server
ai.ankimcp/anki-mcp-server
Manages Anki flashcards, notes, media, decks, and adaptive review through AnkiConnect.
MaCalculatriceEnLigne
io.github.tresor4k/macalc-mcp
Provides calculators for French and Belgian taxes, salaries, pensions, VAT, loans, health metrics, education scores, fitness, and…