Need to connect Datadog MCP Server in ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
I am trying to configure the Datadog MCP Server in ServiceNow. The MCP server does not use a traditional authentication mechanism; however, it requires DD_API_KEY and DD_APPLICATION_KEY to be passed as headers in order to fetch the available tools.
Is there a way to store these headers using a Connection & Credential Alias in ServiceNow? Additionally, while configuring the MCP server, can we select the “Others” option under authentication to pass these headers dynamically?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
@vipulvyas ServiceNow Support External MCP Server Consumption in Service-Now AI Agents Using API Keys.
As I See DATA Dog DD_API_KEY- Will Grant access to Data-Dog MCP Server.
DD_APP_KEY is Responsible for allowing access to observability Data.
In Credential and Connection record i do not think you can store both.
As Per Data Dog Documentation you Can use HTTP Header for Both Keys DD_API_KEY & DD_APP_KEY
Regards
RP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Yes, storing the values in a CCA is the right approach. The key validation point is whether the MCP Server configuration supports custom header propagation when using the "Others" authentication type.
Before implementing a custom solution, test the MCP endpoint using REST API Explorer or a REST Message with:
DD-API-KEY: <key>
DD-APPLICATION-KEY: <key>
If the endpoint successfully returns the tool manifest, then the remaining question is whether your ServiceNow MCP implementation supports passing custom headers from the selected Connection & Credential Alias.
✅ Issue resolved? → Mark as Correct
Found value? → Mark as Helpful