SoftTech AI Registry
Datadog · Datadog MCP Server

Form management tools

The Datadog MCP Server forms toolset, through which an external AI application can inspect, create, update, publish and clone Datadog Forms and read responses from their linked Datadog data stores. Reasoning happens in the external AI application; Datadog performs the authorised Forms operation. No form-delete operation is exposed through MCP.

Recorded characteristics

Function
Reasoning boundary: user → external AI application → external model reasons → AI selects a Datadog MCP Forms tool → Datadog MCP Server performs the authorised Forms operation. The MCP Server receives the tool call, not the user's prompt or the model's reasoning; it is not the reasoning agent. Bits Chat form creation is a separate Datadog-hosted AI route and is outside this capability. Boundary: the `forms` toolset only. Excludes Workflow Automation tools, Case, Dashboard and Sheets tools, generic data store management, Bits Chat form creation, and Forms API operations not exposed through MCP. Tool inventory (8): - Inspection/read: search_datadog_forms, get_datadog_form (can retrieve the `latest`, `published` or a specific numbered version), get_form_definition_schema - Responses (read): get_form_responses - Management: create_datadog_form, update_datadog_form, publish_datadog_form, clone_datadog_form Inspection tools do not independently establish action-taking. Create: create_datadog_form "Creates a new form in draft state, with a linked data store automatically provisioned." The supplied definition must satisfy Datadog's form definition schema (get_form_definition_schema); the complete set of definition fields is not claimed. Requires Forms Manage and Actions Datastore Manage. Linked data store: automatically provisioned with the form; a persistent Datadog-side object that holds the form's responses. The external AI does not separately design or configure it. The lifecycle relationship between form and data store (including deletion) is unresolved. Update: update_datadog_form "Creates a new draft version of an existing form with an updated definition. Does not publish the form; use publish_datadog_form afterward." Requires Forms Manage. Whether the submitted definition replaces or patches the previous definition is not established. Live version: publication is a separate operation from update; exact live-version behaviour during every draft update is not claimed beyond Datadog's wording. Publish: publish_datadog_form "Publishes a specific draft version of a form, making it the live version respondents see." Requires Forms Manage. Unpublish, rollback, automatic deletion of earlier versions and effects on existing responses are not established. Clone: clone_datadog_form "Copies an existing form, including its latest definition, into a new form with a new data store." Requires Forms Manage and Actions Datastore Manage. Copying of responses, permissions, automations or sharing settings is not established. Delete: NO form-delete operation is established in the MCP forms toolset. The underlying Forms API exposes DELETE /api/v2/forms/{form_id}, but that is not an MCP capability and is not part of this record.
Data access
get_form_responses reads submitted responses from the data store linked to a form (requires the datastore_id from get_datadog_form) and requires Actions Datastore Read. Responses are stored in the linked data store; Datadog notes responses may be anonymous (with Anonymous Responses enabled, respondent emails are not stored). No MCP Forms tool is established for creating, modifying or deleting responses; response-data mutation is outside this capability. External action (no): every positively established persistent action in the forms toolset terminates inside Datadog — form creation, linked data store creation, form version creation, publication and cloning. Not classified yes on the basis of respondents outside the organisation, form sharing, Forms automations, Workflow Automation's external effects, or unestablished sharing configuration in a form definition. Automation boundary: Datadog Forms automations are added through the Forms interface ("At the top of the form, select Automation") and appear under Workflow Automation. The MCP forms tools are not established as creating, configuring or triggering automations; #144's workflow execution is not inherited.
Actions
Can take actions
External actions
No
Human confirmation
Not established
Permission basis
Mixed
Administrative control
Authentication (MCP Server level, applies to all toolsets): OAuth 2.0; Personal Access Token; Service Access Token; API plus application keys. No Forms-specific alternative authentication was found. MCP permissions (separate from resource permissions): mcp_read / mcp_write by operation. Forms and data store permissions by tool: - search_datadog_forms, get_datadog_form, get_form_definition_schema: Forms Read - get_form_responses: Actions Datastore Read - create_datadog_form: Forms Manage and Actions Datastore Manage - update_datadog_form: Forms Manage - publish_datadog_form: Forms Manage - clone_datadog_form: Forms Manage and Actions Datastore Manage Permission basis (mixed): the Datadog MCP Server positively establishes multiple authority models for tool calls, including the forms toolset — (A) authenticated user authority using the user's existing Datadog permissions; (B) service-account authority through supported service credentials. Not mixed because of uncertainty. Form-level access (separate layer): Datadog states that by default only the creator of a form can access it; Form Access (view/edit) and Response Access (view responses) are configured in the Forms product. How these per-form settings interact with MCP calls is not established. Creator identity for MCP-created forms is not publicly established; it is not claimed that the authenticated MCP principal becomes the creator. Data store authority: create and clone require both Forms and Datastore permissions because they create the linked data store. No separate execution identity for data store creation is established; the principal recorded as data store creator/owner is unestablished. Human confirmation (not_established): no Datadog-enforced confirmation for create, update, publish or clone. #144's delete confirmation and client-side MCP approval are not inherited. Tool exposure (separate from permissions): Datadog instructs users to enable the `forms` toolset (or `all`). The general omit_tools control applies at MCP Server configuration level; no Forms-specific omit_tools example is documented. Audit: Datadog states all MCP tool calls are recorded in Audit Trail with the tool name, arguments, user identity and MCP client. No separate Forms-specific change audit is established.
Default state
Conditional
Availability
Default conditional: requires Datadog MCP Server configuration, an external MCP-capable AI application, supported authentication, the `forms` toolset (or `all`) exposed, MCP permissions, Forms permissions, and Datastore permissions for operations creating data stores or reading responses. The Forms tools are not part of default MCP operation. Lifecycle: Registry lifecycle active. This does NOT mean the MCP forms toolset is generally available. Evidence tension: the `forms` toolset is documented and exposed on the MCP Server Tools page; Datadog's current setup page lists `forms` under neither its generally available toolsets nor its Preview toolsets; Datadog Forms itself carries no investigated Preview label; the underlying Forms API endpoints are labelled Preview. Datadog MCP toolset release-status classification: not publicly established. The relationship between the MCP forms toolset's release status and the underlying Forms API Preview status is not publicly established. Versioning: draft versions, the published version, the latest version and numbered-version retrieval are established. Rollback, unpublish, restoration and republishing older versions are not established. Sharing: MCP management of Form Access, Response Access, accepting responses, anonymous responses or sharing settings is not established. Site restrictions: the Datadog MCP Server and Datadog Forms are not supported on app.ddog-gov.com or us2.ddog-gov.com.
Licensing
Requires a Datadog organisation with Datadog Forms; no separate MCP-specific licence for the forms toolset was established.
External model or provider
No fixed model or provider. The external AI application supplies the reasoning model; supported client providers are not attributed to Datadog.
Limitations and uncertainty
1. MCP forms toolset release status is not publicly established. 2. The relationship to the underlying Forms API Preview label is not publicly established. 3. Form creator identity for MCP-created forms is not established. 4. Interaction between per-form access (Form Access, Response Access, creator-only default) and MCP calls is not established. 5. The complete contents of the AI-supplied form definition are not documented. 6. Full-replacement versus partial-update semantics of update_datadog_form are not established. 7. Exact earlier-version behaviour after publication is not established. 8. The effect of publication on existing responses is not established. 9. Whether cloning copies permissions, responses, automations or sharing is not established. 10. Data store lifecycle after form deletion through non-MCP means is not established. 11. No unpublish, rollback or delete MCP tools exist. 12. Whether sharing can be encoded through the form definition is not established. 13. Datadog warns that MCP Server tools are under significant development and subject to change.

Evidence