Kiwi for Datadog
Have the agent on a Kiwi step check Datadog logs, traces and monitors for the service it changed, through Datadog's remote MCP server.
- Your agent works in Datadog through its own connection. Kiwi does not call Datadog and never holds its credentials.
- A workflow skill can list Datadog among the tools it requires. When you supply your agent's available tools to a skill check and Datadog is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Datadog, with notes, under Connections and bind them to the steps that use them. The agent reads them with
list_connections. - The agent can report the tools and plugins it ran with, including its Datadog connection, with
report_configuration. - The agent submits links to its work in Datadog as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Datadog
- Search and analyze a service's logs over a chosen time range.
- Fetch a trace by its ID and search spans to follow a slow or failing request.
- Look up the monitors, incidents and events that concern a service.
- Query a metric and find the dashboards that chart it.
- Search Error Tracking issues for a service.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to Datadog
Add the Datadog MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.datadoghq.com/v1/mcpExample skill
Publish instructions like these as a workflow skill that lists Datadog among its required tools.
Start from the service name and deploy time given in the step's inputs. In Datadog, compare the service's error logs, traces and monitor states for the hour before and the hour after the deploy. Record the monitor links and the log queries you ran in the step's outputs. If a monitor is alerting, report a blocker to the run's Owner; do not mute it.