Skip to content

chore: wire managed MCP servers into .mcp.json - #422

Closed
developerz-ai[bot] wants to merge 1 commit into
mainfrom
developerz/mcp-codegraph
Closed

developerz-ai[bot] wants to merge 1 commit into
mainfrom
developerz/mcp-codegraph

Conversation

@developerz-ai

@developerz-ai developerz-ai Bot commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

This merges the managed MCP servers into your existing .mcp.json — your own mcpServers entries 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 sets DO_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 proxied db_* 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?

@developerz-ai

developerz-ai Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor Author

A fix is queued and waiting for a machine that can run this repository. Nothing is needed from you right now.

  • Red on this head: integration (node, real git)
  • What was done: Fix round tsk_37b6c339aefe197fae46aefc8884faa7 was created for the failing check(s). It has not started: no_screen_key.
  • What happens next: It starts as soon as a machine that can serve it is free, and pushes to this branch. Nothing is needed from you unless that hold is one only you can clear (a missing service, key or onboarding step) — the dashboard inbox lists it.

Status for head 23685c493c79. This comment is updated in place.

🤖 Posted by developerz.ai — an automated agent, not a human.

@dinndev2

Copy link
Copy Markdown
Contributor

Closing: this re-adds an MCP server that the public-tree guard forbids, which is why CI is red here. The tracked .mcp.json is public, so it names only tools a user of this repository can run. Add the server locally with claude mcp add --scope local …; that keeps it out of the tracked file. The platform-side change that stops these pull requests on public repositories is tracked with the maintainers.

@dinndev2 dinndev2 closed this Nov 15, 2026
@developerz-ai
developerz-ai Bot deleted the developerz/mcp-codegraph branch November 15, 2026 05:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant