Connect Datadog to Aurora in Finta

Direct answer: Finta's catalog lists Datadog's remote MCP server with all toolsets at https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=all. Datadog documents OAuth-based access to supported observability tools across logs, metrics, traces, monitors, dashboards, incidents, and security, with site-specific setup and an evolving tool inventory.

This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Datadog remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.

How the Datadog connection works

What you can use it for

• Search authorized logs, metrics, traces, monitors, dashboards, and incident context.
• Investigate an observed reliability problem using source-linked telemetry.
• Prepare a monitor, incident, or dashboard action for human review when a write tool is exposed.
• Limit access by choosing only the Datadog toolsets needed instead of using all toolsets.

These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.

Relationship intelligence workflows for Datadog

Investigate a production issue before an investor demo

Outcome: Have engineering approve any statement that the issue is resolved.

1. Identify the exact service, environment, and time window.
2. Retrieve relevant monitor, log, metric, trace, and incident evidence.
3. Separate observed facts from root-cause hypotheses.
4. Have engineering approve any statement that the issue is resolved.

Human decision: Telemetry supports an internal diagnosis but does not authorize an external reliability claim or production mutation.

Prepare board-level reliability context

Outcome: Have the technical owner approve the source-linked summary.

1. Define the services, period, and measures approved for the report.
2. Retrieve the relevant monitors, incidents, and dashboards.
3. Document gaps, query definitions, and unresolved risks.
4. Have the technical owner approve the source-linked summary.

Human decision: Do not invent uptime, incident counts, or customer impact from incomplete telemetry.

How to connect Datadog to Aurora

1. Confirm the Datadog site or region and derive the current official endpoint for that site.
2. In Aurora, open Apps and select Datadog.
3. Authorize the catalog endpoint and review organization, product, and toolset access.
4. Replace all toolsets with a narrower set if Aurora's catalog flow supports that restriction.
5. Run a read-only monitor or dashboard lookup in a controlled time window.

Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.

Permissions and approval boundary

Use OAuth and the narrowest toolsets and roles possible. Start read-only. Require incident owner approval before monitor changes, incident actions, security operations, or any write. Keep logs, traces, user data, and security findings within the authorized audience.

Limitations to understand

• Datadog MCP is under active development and tool names and coverage can change.
• The correct remote endpoint can depend on the organization's Datadog site or region.
• The Finta catalog currently requests toolsets=all, which is broader than many workflows require.
• Observability data can be incomplete due to retention, sampling, instrumentation, or permission limits.

Verification checklist

• Reconcile the catalog hostname and all-toolsets query with the target Datadog site's current setup guidance.
• Capture OAuth identity, organization, roles, toolsets, and discovered tools.
• Run one safe read-only monitor, dashboard, or incident lookup and retain the receipt.
• Test one controlled write only after approval and verify it in Datadog's audit history.
• Record site, telemetry gaps, retention constraints, and verification date before publication.

Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.

Official provider sources

• Datadog official MCP documentation (docs.datadoghq.com)
• Datadog official MCP documentation 2 (docs.datadoghq.com)
• Datadog official MCP documentation 3 (docs.datadoghq.com)

Related Finta guides

• A related Finta workflow
• MCP permissions and security
• Finta integrations
• Official Finta apps

Use approved Datadog context with Aurora