get_form_submission — dotsy MCP Tool Read-only
get_form_submission
(get form submission) is one of 120 tools on the
dotsy
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_form_submission from your client
- Claude Code dotsy get_form_submission run in your project directory
- Claude Desktop dotsy get_form_submission ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor dotsy get_form_submission ~/.cursor/mcp.json
- VS Code dotsy get_form_submission .vscode/mcp.json
- Zed dotsy get_form_submission ~/.config/zed/settings.json
- Windsurf dotsy get_form_submission ~/.codeium/windsurf/mcp_config.json
- Cline dotsy get_form_submission ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI dotsy get_form_submission ~/.gemini/settings.json
- Grok dotsy get_form_submission .mcp.json (in your project root)
- ChatGPT dotsy get_form_submission Settings → Connectors → Advanced → Developer mode
- Claude.ai dotsy get_form_submission Settings → Connectors → Add custom connector
- LangChain dotsy get_form_submission pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.dotsy.ai/mcpOther tools on this server
- create_site
- get_site
- update_brief
- get_plan
- get_analytics
- set_analytics_provider
- get_custom_code
- set_custom_code
- set_site_icon
- update_site
- rename_site
- publish_site
- get_site_tasks
- get_draft_status
- review_changes
- discard_drafts
- delete_site
- bulk_put_content
- get_site_manifest
- find_replace
- search_content
- graduate_site
- apply_changeset
- import_site_from_url
- get_structure_status
- structure_site_analyze
- structure_site_apply
- get_structure_result
- adapt_site_analyze
- adapt_site_apply
- adapt_site_revert
- get_adapt_status
- list_content
- get_content
- put_content
- stage_content_chunk
- patch_content
- batch_patch_content
- delete_content
- rename_content
- put_post
- inspect_collection
- list_collections
- update_collection
- new_post_template
- get_collection_schema
- put_collection_schema
- set_item_status
- get_board
- list_votes
- remove_votes
- list_suggestions
- moderate_suggestion
- add_idea
- list_ideas
- infer_collection_schema
- reindex_collection
- preview_page
- verify_page
- preflight_site
- start_edit_session
- get_site_outline
- share_section
- detach_section
- get_route
- put_route
- patch_route
- rename_page
- delete_route
- list_goals
- put_goals
- estimate_test
- start_test
- promote_experiment
- delete_draft_test
- set_experiment_note
- get_menu
- put_menu_item
- delete_menu_item
- reorder_menu
- get_menu_doc
- put_menu_doc
- list_assets
- get_asset
- bulk_put_assets
- delete_asset
- optimize_assets
- translate_page
- start_site
- claim_site
- list_skills
- get_skill
- submit_feedback
- get_activity
- list_versions
- restore_version
- undo_publish
- revert_change
- get_account_context
- report_bug
- get_report
- reply_to_report
- add_custom_domain
- get_custom_domain_connect
- reapply_custom_domain_oauth
- refresh_custom_domain
- wait_for_custom_domain
- set_primary_custom_domain
- list_custom_domains
- set_up_bare_domain
- remove_custom_domain
- list_form_submissions
- form_recipients
- list_notifications
- mark_notifications_read
- list_my_sites
- list_pages
- edit_page
- get_site_build_progress
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.