Repository navigation
chore: wire managed MCP servers into .mcp.json - #422
Closed
developerz-ai[bot] wants to merge 1 commit into
Closed
developerz-ai[bot] wants to merge 1 commit into
developerz-ai[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
A fix is queued and waiting for a machine that can run this repository. Nothing is needed from you right now.
Status for head 🤖 Posted by developerz.ai — an automated agent, not a human. |
Contributor
|
Closing: this re-adds an MCP server that the public-tree guard forbids, which is why CI is red here. The tracked |
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
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.
This merges the managed MCP servers into your existing
.mcp.json— your ownmcpServersentries are kept verbatim; only absent managed keys were added:codegraph— structural code intelligence over a local knowledge graph (codegraph, MIT; stdio, the index is a local SQLite file, no keys). This entry setsDO_NOT_TRACK=1+CODEGRAPH_TELEMETRY=0+CODEGRAPH_NO_UPDATE_CHECK=1, which disable the two outbound calls codegraph v1.5.0 makes (anonymous usage telemetry and a daily release check). Any coding agent opened on this repo gets it.developerz— the developerz.ai platform control plane (streamable HTTP). The bearer is an inert${DEVELOPERZ_API_KEY}shell-env reference — no secret is committed.Two more servers make your agents’ lives noticeably easier, but are suggested, not auto-added — this onboarding pass only lays the unconditional floor; the setup agent (which works on a real checkout) decides what this repo actually needs:
ui-debugger-mcp— autonomous story-in/findings-out UI testing. Only useful if this repo drives a browser (many don't need it); the setup agent adds it automatically when it detects a UI/e2e harness. It needs a key first — connect ui-debugger in your dashboard so the box has one to use.db-mcp-gateway— safe database access for agents through a deployed gateway. This account already connected one, so its agents reach it through the platform's proxieddb_*tools; nothing goes in.mcp.json.Not interested? Just close this PR — the file is config-only and nothing else was touched.
🤖 Opened automatically by developerz.ai (
developerz-ai[bot]), an automated agent, not a human, when the app was installed on this repository. What is this?