# mcp-integration-engineer

This subagent connects MCP servers to clients and coordinates multi-server workflows. It helps when you need fault-tolerant architectures and clean configuration files.

- subagent · `type=agent` · Claude Code · 1083 installs
- Author: davila7
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/davila7/claude-code-templates/tree/HEAD/cli-tool/components/agents/mcp-dev-team/mcp-integration-engineer.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/agents/mcp-integration-engineer

## What it does

The subagent designs architecture patterns for linking MCP servers with client environments. It plans service communication flow. Beyond topology design, it creates declarative setup files and organizes event routing between services.

Reliability mechanisms are built directly into the generated plans. The agent applies circuit breaker logic and retry rules to prevent cascading outages. It also outputs authentication configurations, client setup templates, and monitoring guidelines.

Operating this agent requires permissions for `Read`, `Write`, `Edit`, and `Bash`. Without local shell and file access, it cannot write configuration templates directly to your repository.

## Install

### Claude Code (native platform)

1. **claude-code-templates**
```bash
npx claude-code-templates@latest --agent mcp-dev-team/mcp-integration-engineer
```

2. **Manually: put the files in place**
- File: `.claude/agents/mcp-integration-engineer.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/mcp-integration-engineer.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/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/mcp-integration-engineer.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/davila7/claude-code-templates/tree/HEAD/cli-tool/components/agents/mcp-dev-team/mcp-integration-engineer.md

## When to use it
- orchestrate communication across multiple MCP servers
- configure circuit breaker and retry rules for MCP calls
- generate client configuration templates and security settings
- establish monitoring and alerting for connected servers

## Example prompts
- Use mcp-integration-engineer to orchestrate GitHub and database MCP servers
- Create an MCP client configuration featuring circuit breaker retry policies
- Design an authentication and monitoring workflow for my local MCP services

## Similar
- [frontend-developer](https://affpapa.org/en/nevibecode/agents/voltagent-community-frontend-developer.md) — subagent · 40905 installs
- [dx-optimizer](https://affpapa.org/en/nevibecode/agents/dx-optimizer.md) — subagent · 1198 installs
- [mlops-engineer](https://affpapa.org/en/nevibecode/agents/voltagent-community-mlops-engineer.md) — subagent · 1009 installs
- [postgres-pro](https://affpapa.org/en/nevibecode/agents/postgres-pro.md) — subagent · 897 installs
- [agent-installer](https://affpapa.org/en/nevibecode/agents/agent-installer.md) — subagent · 363 installs
- [embedded-systems](https://affpapa.org/en/nevibecode/agents/embedded-systems.md) — subagent · 279 installs

From the same set: [davila7/claude-code-templates](https://affpapa.org/en/nevibecode/by/davila7/claude-code-templates.md) — 495 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md