Compose a delivery signature section.
Create a delivery acknowledgement.
Set delivery recovery guidance.
Determine a signature requirement.
Build a dispatch manifest.
Set document release selection guidance.
Select a document release.
Select an event callback address.
Set the style guidance for an executive report.
Set confirmation style for a delivery workflow.
Register a delivery confirmation pattern.
Sequence stops for a field route.
Register a handoff recovery policy.
Assign an incident owner.
Build an interview agenda.
Register a queued processing profile.
Update a section and backlink index.
Segment a knowledge note for indexing.
Plan a knowledge-base placement path.
Plan a translation setting.
Plan a lot allocation.
Calculate a metric trend summary.
Register a milestone time interpretation.
Assemble a scheduled operations digest.
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.