Select a processing profile.
Create a profile-setting review item.
Plan a profile governance setting.
Register a profile governance setting.
Choose a profile setting key.
Identify the project handle from an intake note.
Prepare project context from an intake note.
Create a purchase draft.
Prepare a customer record field for reporting.
Assemble a reporting export row.
Prepare a referral handoff digest.
Create a referral handoff packet.
Select a rollout region.
Select a branch for a release.
Assess a release branch.
Prepare a configuration entry.
Identify a configuration label for a release brief.
Publish a stakeholder report entry.
Add entries to a renewal schedule.
Set the style guidance for an executive report.
Format a status report for stakeholders.
Assemble a reporting export row.
Register a request reviewer group.
Select a contact for a client brief.
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.