vercel / vercel/next-devtools-mcp
CLI instead of MCP
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 822
- Forks
- 67
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
Description
Just curious if it's possible to rewrite the devtools as a CLI which any coding agent can call this removing the bloat from the available context window. I'm thinking this way it might be easier also for different agents to inspect different dev servers from different worktrees that run in parallel
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by clarifying the CLI scope, how coding agents should invoke it, and how separate dev servers and worktrees are identified; done requires an agreed design and implementation that supports those parallel use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100