QuLab MCP remote server (Streamable HTTP) for computational science and lab tools.
Create an access review checklist.
Build a grouped account report.
Set account merge guidance.
Merge an account revision.
Compose an account grouping recipe.
Prepare an agreement obligation schedule.
Select a reviewer group.
Register an artifact delivery route.
Plan the delivery route for an artifact.
Plan the delivery route for an artifact.
Register an artifact delivery route.
Set the intended audience for a briefing.
Map candidate skills to an interview plan.
Compose audience-ready briefing sections.
Select a contact for a client brief.
Plan an option for a runbook example.
Set handling guidance for a content item.
Triage a workspace content item.
Queue content for editorial review.
Prepare a content review plan.
Prepare a customer record field.
Set timezone guidance for project deadlines.
Set acknowledgement guidance for a delivery.
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.