chore: no changes needed for Datadog connector - #111
Open
major-connector-creator[bot] wants to merge 1 commit into
Open
chore: no changes needed for Datadog connector#111major-connector-creator[bot] wants to merge 1 commit into
major-connector-creator[bot] wants to merge 1 commit into
Conversation
Datadog uses the HTTP proxy + MCP proxy pattern (like Browserbase and Langfuse). No custom typed TypeScript client, no custom schemas, no payload builders. Users interact with Datadog via: - HTTP proxy: createProxyFetch from @major-tech/resource-client/next - MCP proxy: Datadog's hosted MCP tools auto-surfaced through the generic MCP reverse-proxy
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
No changes needed in this repository for the Datadog connector.
Datadog uses the HTTP proxy + MCP proxy pattern (like Browserbase and Langfuse). There is no custom typed TypeScript client, no custom schemas, no payload builders. Users interact with Datadog via:
createProxyFetchfrom@major-tech/resource-client/nextfor REST API callsThis is the same pattern as Browserbase and Langfuse — neither has entries in the
resource-clientpackage.Related PRs