Datadog Power installs/connects incorrectly: no tools available and Connect fails with "Missing server info"

[boluwaji-deriv]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

Ubuntu 22.04

Kiro Version

Kiro Web

Bug Description

The Datadog Observability Power appears installed, but Kiro shows "No tools available" and the Connect flow fails with:

Missing server info
Cannot connect: server name or URL is unavailable.

Observed behavior:

• Postman works and is registered under powers.mcpServers as:
  power-postman-postman
• Datadog is registered differently, under top-level mcpServers as:
  datadog
• Expected power-scoped key appears to be:
  power-datadog-datadog
• Kiro gateway returns:
  No mcpOAuth provider registered for serverName='datadog'

Additional evidence:

• Direct Datadog MCP access works with valid Datadog API/Application credentials.
• The Datadog MCP endpoint initializes and exposes tools when called directly.
• The failure appears specific to Kiro’s gateway/proxy/OAuth registration flow.
• The Datadog power package includes mcp.json with type: "http", which may not be handled by the Kiro Powers Connect button, causing the missing server info error.

Expected behavior:
Installing the Datadog Power should register its MCP server under powers.mcpServers using the Kiro power naming convention, trigger the OAuth/connect flow successfully, and expose Datadog tools in Kiro sessions.

Actual behavior:
The power appears installed, but no tools are available. The Connect button cannot start because server metadata is missing/unavailable, and the Kiro gateway has no OAuth provider registered for serverName='datadog'.

Impact:
Datadog Power is unusable in Kiro even though Datadog credentials and the MCP endpoint are valid.

Environment:

• Kiro Web / Kiro Powers
• Power: Datadog Observability
• Working comparison: API Testing with Postman

Steps to Reproduce

1. Open Kiro Web at app.kiro.dev.
2. Go to Settings > Powers.
3. Install or open the Datadog Observability Power.
4. Click Connect for Datadog Observability.
5. Observe that the connection fails with:
   Missing server info
   Cannot connect: server name or URL is unavailable.
6. Start or open a Kiro Web session where the Datadog Power should be available.
7. Ask Kiro to use Datadog tools or inspect available tools.
8. Observe that the Datadog Power shows "No tools available".

Comparison case:

1. In the same Kiro Web account, install/open API Testing with Postman.
2. Connect Postman.
3. Observe that Postman registers correctly and exposes tools, while Datadog does not.

Expected Behavior

When the Datadog Observability Power is installed in Kiro Web, Kiro should register the Datadog MCP server as a power-scoped MCP server, start the Connect/OAuth flow successfully, and expose Datadog tools in Kiro sessions.

The Connect button should not fail with "Missing server info". After connection, the Datadog Power should behave like the working Postman Power: tools should be available instead of showing "No tools available".

Conversation ID

https://app.kiro.dev/session/9083d70b-81ff-4e0c-a874-27b83b6c354c

Additional Context

No response

[github-actions]

Thanks for opening this issue and providing such a thorough investigation into the Datadog Power registration behavior! It's clear that the power isn't being registered under the expected powers.mcpServers naming convention, which is preventing the connect flow and tool discovery from working properly. A maintainer will review this shortly — your detailed comparison with the working Postman power is really helpful for tracking this down!