Repository navigation
chore: wire managed MCP servers into .mcp.json - #27
developerz-ai[bot] wants to merge 2 commits into
Conversation
|
Needs a human: dinndev2/adminer #27: a check keeps ending without a result and needs a look at CI. A check on this pull request ended without a result on the code (GitHub cancelled it, marked it stale, or the job failed before running a single step) and a re-run did not settle it: it ended the same way again, GitHub refused the re-run (this installation has not accepted the app's Actions write permission, the run is too old to re-run, or the repo forbids it), the job's workflow run was still going past the CI wait ceiling, so GitHub would not re-run the job yet, or it is not a job the platform can re-run. Such a job never reported on the code, so no fix was attempted and nothing was split. Look at the CI configuration (a job timeout, a concurrency group, runner availability, the workflow permissions). If GitHub refused the re-run, re-run the job by hand or push a commit; if the job's workflow run was still going, the job is re-runnable once that run finishes, and a re-run by hand would be refused the same way. 🤖 Posted by developerz.ai — an automated agent, not a human. |
|
The developerz.ai bot is closing its own pull request: it has been open for 116 days without being merged. developerz.ai does not leave its own work standing: a pull request it opened that has not landed within 60 days is closed rather than left to go stale. Nothing on the default branch changes, and the branch is kept. If this change is still wanted, reopen this pull request: it is not closed a second time. 🤖 Posted by developerz.ai — an automated agent, not a human. |
🤖 I'm the developerz.ai maintainer bot (
developerz-ai[bot]) — this PR was opened automatically when the app was installed on this repository. What is this?This adds a root
.mcp.jsonwiring the managed MCP servers:codegraph— structural code intelligence over a local knowledge graph (codegraph, MIT; stdio, 100% local, no keys, no egress). 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.db-mcp-gateway— safe database access for agents through a deployed gateway. It involves more than this one repo (a gateway deployment, e.g. in your infra repo, plus creds), so it can't be auto-wired here — see the companion issue for how to add it.Not interested? Just close this PR — the file is config-only and nothing else was touched.