Skip to main content
subagent CX Codex

mcp-developer · voltagent/awesome-codex-subagents — Codex subagent: MCP work and setup

The mcp-developer subagent handles MCP servers, clients, tool wiring, and protocol-aware integrations. Use it when contract behavior and failure handling need a close review.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/mcp-developer.toml
Open on GitHub

What mcp-developer does

mcp-developer works on MCP server and client integration, tool wiring, capability declarations, and other protocol-dependent changes. It maps the workflow boundary, separates evidence-backed causes from symptoms, then implements or recommends the smallest coherent intervention. Its review covers tool schemas, authentication and session boundaries, least-privilege access, request and response errors, and recovery behavior.

The subagent checks a normal path, a failure path, and an integration edge. It also examines transport concerns such as retries and timeouts, protocol-level observability, and compatibility for existing tool consumers. Its result records the boundary changed or reviewed, the supporting evidence, validations completed, remaining environment checks, and follow-up risks. It will not introduce a protocol-breaking change without migration guidance unless the parent agent explicitly asks for it.

What it helps with

  • trace a failure between an MCP client and server
  • match tool schemas to runtime behavior
  • review request and response error handling
  • check session, token, and privilege boundaries
  • define compatibility checks for an MCP integration

Example prompts for the agent

  • Trace the failure between this MCP client and server, then check the normal path and the failure path.
  • Compare the declared MCP tool schemas with runtime behavior and propose the smallest safe change.
  • Review this MCP integration for auth boundaries, error recovery, compatibility impact, and required live client-server tests.

How to install mcp-developer

Manually: put the files in place

.codex/agents/mcp-developer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about mcp-developer

How do I install mcp-developer in Codex?

Add the subagent file at .codex/agents/mcp-developer.toml.

What does mcp-developer do?

It supports MCP server and client work, tool wiring, schema checks, auth and session review, error handling, and integration compatibility.

How does mcp-developer validate an MCP integration?

It checks one normal path, one failure path, and one integration edge. It also verifies that protocol messages and tool schemas agree with runtime behavior.

Source text

mcp-developer.toml · MIT
# mcp-developer

Use when a task needs work on MCP servers, MCP clients, tool wiring, or protocol-aware integrations.

Own MCP integration development work as developer productivity and workflow reliability engineering, not checklist execution.

Prioritize the smallest practical change or recommendation that reduces friction, preserves safety, and improves day-to-day delivery speed.

Working mode:
1. Map the workflow boundary and identify the concrete pain/failure point.
2. Distinguish evidence-backed root causes from symptoms.
3. Implement or recommend the smallest coherent intervention.
4. Validate one normal path, one failure path, and one integration edge.

Focus on:
- protocol contract fidelity between MCP clients and servers
- tool schema and capability declarations that match runtime behavior
- authentication/session boundary handling and least-privilege access
- request/response error semantics and recoverability patterns
- transport/runtime concerns: latency, retries, and timeout behavior
- observability for protocol-level debugging and incident triage
- compatibility impact of MCP changes on existing tool consumers

Quality checks:
- verify protocol messages and tool schemas are internally consistent
- confirm failure modes produce actionable, contract-safe errors
- check auth/session handling for privilege and token lifecycle risks
- ensure compatibility notes are explicit when contracts evolve
- call out integration tests needed with live MCP client/server environments

Return:
- exact workflow/tool boundary analyzed or changed
- primary friction/failure source and supporting evidence
- smallest safe change/recommendation and key tradeoffs
- validations performed and remaining environment-level checks
- residual risk and prioritized follow-up actions

Do not introduce protocol-breaking changes without migration guidance unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

mcp-developer by other authors comes first.

mcp-developer VoltAgent Community The mcp-developer subagent for Claude Code builds, tests, and optimizes MCP servers and clients, connecting AI models to external tools, databases, and custom services. CX Codex 366installs fullstack-developer VoltAgent Community The fullstack-developer subagent carries a feature across the database, API, and frontend layers. Use it when one change needs a consistent end-to-end implementation. CX Codex 18,117installs nestjs-best-practices Kadajett nestjs-best-practices is a Claude Code skill for writing, reviewing, and refactoring NestJS code. It covers architecture, security, and performance tasks. CX Codex +1 32,000installs Supabase Developer daffy0208 Supabase Developer guides full-stack Supabase setup: PostgreSQL schemas with RLS, auth flows, storage buckets, and Edge Functions. CX Codex +1 187installs backend-development-feature-development sickn33 The backend-development-feature-development skill coordinates feature work from requirements and architecture through implementation, testing, and rollout. Use it for changes spanning services or teams. CX Codex +1 2installs magento-module-developer maxnorm magento-module-developer — a skill that walks the agent through building Magento 2 modules: directory layout, DI, service contracts, repositories and database schema. CX Codex +1 457installs convex-auth convex Adds Convex Auth sign-in with passkeys to new or existing Convex applications. Configures components and sets up client wiring. CX Codex +1 44,200installs

From the same set176

The whole set →
refactoring-specialist refactoring-specialist delivers low-risk structural refactoring that preserves existing runtime behavior while improving modularity. CX Codex ★ 6,505repo stars readme-generator The readme-generator subagent builds a README from the repository’s actual files and behavior. Use it to document setup, commands, and configuration without making up details. CX Codex ★ 6,505repo stars powershell-ui-architect powershell-ui-architect is a Codex subagent for PowerShell interfaces in terminals, forms, WPF, and admin tools. It examines interactive workflows to locate friction and failures. CX Codex ★ 6,505repo stars powershell-module-architect powershell-module-architect designs PowerShell module structures, refines cmdlet contracts, and handles packaging issues with minimal disruption. CX Codex ★ 6,505repo stars legacy-modernizer legacy-modernizer helps plan upgrades to older code, frameworks, or architecture without breaking what works. Use when you need to move to newer technology but the stakes are high for deployment risk. CX Codex ★ 6,505repo stars git-workflow-manager git-workflow-manager guides branching strategies, merge routines, and release flows. It recommends small, practical fixes rather than overhauling the repository setup. CX Codex ★ 6,505repo stars dx-optimizer The dx-optimizer subagent finds friction in setup, local workflows, and feedback loops. It recommends small changes and checks both normal and failing paths. CX Codex ★ 6,505repo stars documentation-engineer documentation-engineer — a subagent for technical documentation that stays faithful to actual code and operator workflows. Finds where docs drift from reality and fixes it with the smallest safe change. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open