Standardbeagle Agnt
standardbeagle-agnt is a Claude Code plugin for the Build phase that adds an MCP server for project detection, process management, reverse proxy, and frontend instrumentation.
by standardbeagle · github.com/standardbeagle/agnt
Register agnt MCP when you want your coding agent to detect projects, manage dev processes, proxy local traffic, and capture frontend instrumentation for debugging.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install standardbeagle-agnt@standardbeagle/agntBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:standardbeagle/agnt") and the paste-ready config with skillselion.get_install_config("plugin:standardbeagle/agnt").
What it does
standardbeagle-agnt is a Claude Code plugin bundling an MCP server aimed at day-to-day development ergonomics for solo builders shipping web apps. Instead of juggling separate scripts for finding the right package manager, spawning processes, and capturing what the browser actually sent, agnt centralizes project detection, process management, and a reverse proxy with optional frontend instrumentation and traffic logging. Agents can use it to sketch flows, diagnose UI issues, and correlate requests without leaving the MCP tool surface. The plugin fits builders who live in Cursor or Claude Code during implementation and want observable local stacks rather than production APM. It is integration-heavy MCP plumbing, not a deployment or SEO skill; pair it with your usual test and review practices before ship.
Highlights
- MCP server for development tooling: project detection and process management
- Reverse proxy with traffic logging for local frontend and API debugging
- Browser and frontend instrumentation hooks for diagnostic and wireframe-oriented workflows
- Agent-facing surface so Claude Code can orchestrate dev servers and logged traffic
Why builders use it
Local full-stack debugging is fragmented—agents struggle to detect project layout, manage dev processes, and see real browser traffic without custom scripts.
With agnt MCP registered, your agent can drive a consistent local dev stack with proxy, logging, and frontend diagnostics from one integration.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 3 stars, 0 votes.
FAQ
Who is standardbeagle-agnt for?
It is for developers using Claude Code or compatible agents who want MCP tools for local project detection, dev process management, and frontend traffic diagnostics.
When should I use standardbeagle-agnt?
Use it while building or debugging a web app locally when you need reverse-proxy traffic logging, process management, or browser instrumentation from the agent.
How do I add standardbeagle-agnt to my agent?
Install the standardbeagle/agnt Claude Code plugin, configure the agnt MCP server in your agent's MCP settings, and start your dev stack so tools can detect the project and attach proxy or instrumentation.
Comments
Share how you use standardbeagle-agnt, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.