Set severity-based assignment guidance.
Select a service capacity window.
Set source-agreement guidance.
Resolve imported field values.
Build a stakeholder metric digest.
Build a stakeholder configuration report.
Format a status report for stakeholders.
Register an event callback address.
Set supplier-name matching guidance.
Reconcile supplier names.
Prepare supplier purchasing terms.
Build a support case comment.
Digest a support intake marker.
Add a support case follow-up.
Prepare a support intake digest.
Build a translation job entry.
Plan a translation setting.
Build a translation job entry.
Compare workspace access lists.
Find the reference marker for a knowledge item.
Write a workspace export file.
Plan a knowledge-base placement path.
Write a workspace export file.
MCP server for managing Caddy web servers via the admin API.
About Development MCP servers
Development is the broadest category on mcp.site. It covers servers that give an AI agent hands-on access to the software lifecycle: sandboxed shells and terminals, version-specific library documentation, package registries, test runners, debuggers, build and deploy pipelines, and project tools such as issue trackers. Most run locally over stdio because they need your filesystem or toolchain; a growing share run as hosted endpoints you connect with an API key or OAuth.
When choosing one, start with what the agent should be able to do without asking you, then check how the server scopes that access. Good servers expose a small, typed set of tools, document every environment variable, and let you restrict paths or repositories. Prefer listings with an Official badge or a recently updated repository, and read the install snippet for your client before adding credentials.