HOLD FOR LAUNCH private bridge MCP server setup guide#365
Open
mindymo wants to merge 6 commits into
Open
Conversation
New page covering how to connect a private/network-local MCP server to C1 through the bridge agent, with no inbound firewall rules required. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- "ConductorOne download center" → "C1 download center" (prose rule) - Add outcome sentence after Step 1 <Steps> block - Add intro sentence before Step 4 <Steps> block (was directly after heading) - Add outcome sentence after Step 4 <Steps> block - "Step 6 — Verify" → "Step 6 — Verify the connection" (heading must be descriptive out of context) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Fix button name: "Create credential" → "Rotate credential" - Fix step order: enter display name before clicking Create bridge - Update download link to dist.conductorone.com/ConductorOne/bridge-client - Replace placeholder Kubernetes/Docker note with real deployment tabs, including actual ECR image path and manifests - Fix credential rotation section button names (Rotate/Revoke → Rotate credential/Revoke credential) - Simplify Step 6 log-tailing prose Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Lead with the barrier (private network, no inbound firewall changes) rather than the mechanism. Trim from four sentences to two. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
mindymo
changed the title
Collaborator
Author
|
@jessstarr-hub @jugonzalez12 Hiya! I'm on vacation next week, so here's a draft PR for the bridge docs based on what's in Julián's Notion doc and the registry docs. Please review this and make any adjustments (you can point an agent at the PR and tell it what to do), then approve/merge it when ready. I'm around all day tomorrow if you have questions about any of this. Thanks! |
- Replace feature-gate note with "Activation required" pattern (AIAM must be enabled; contact support to get bridge connectivity turned on) - Remove placeholder from release note; add contact CTA and AIAM prerequisite Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
product/admin/mcp-bridge.mdx— a new setup guide for connecting a private/local MCP server to C1 using the bridge agent (bridge-client), with no inbound firewall rules requireddocs.jsonunder the existing "MCP server setup guides" nav group alongside Datadogbridge.yaml, validating and running the agent, registering the server in C1, reviewing discovered tools, verifying, troubleshooting, and rotating credentialsNotes for reviewers
This is a first draft from internal developer docs. The design team flagged that the source doc had accuracy issues, so several things still need verification against the actual product UI:
bridge-config-checkis the correct binary nameTest plan
🤖 Generated with Claude Code