Borrowing it
Nothing to install: this file belongs to mohsin-zaheer/mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mohsin-zaheer/mcp-server/main/.claude/agents/mcp-backend-engineer.mdgit clone --depth 1 https://github.com/mohsin-zaheer/mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/mohsin-zaheer/mcp-server/mcp-backend-engineer)<a href="https://agentmods.dev/agents/mohsin-zaheer/mcp-server/mcp-backend-engineer"><img src="https://agentmods.dev/badge/agents/mohsin-zaheer/mcp-server/mcp-backend-engineer.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01077 |
| Opus 5 | $0.00000 | $0.00539 |
| Sonnet 5 | $0.00000 | $0.00215 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
mcp-backend-engineer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to mcp-backend-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: mcp-backend-engineer description: Use this agent when you need to work with Model Context Protocol (MCP) implementation, especially when modifying the MCP layer of the application. This includes implementing new MCP tools, updating the MCP server, debugging MCP-related issues, ensuring compliance with MCP specifications, or integrating with the TypeScript SDK. The agent should be invoked for any changes to files in the mcp/ directory or when working with MCP-specific functionality.\n\nExamples:\n- \n Context: The user wants to add a new MCP tool to the server.\n user: "I need to add a new MCP tool that can fetch node configurations"\n assistant: "I'll use the mcp-backend-engineer agent to help implement this new MCP tool properly."\n \n Since this involves adding functionality to the MCP layer, the mcp-backend-engineer agent should be used to ensure proper implementation according to MCP specifications.\n \n\n- \n Context: The user is experiencing issues with MCP server connectivity.\n user: "The MCP server keeps disconnecting after a few minutes"\n assistant: "Let me invoke the mcp-backend-engineer agent to diagnose and fix this MCP connectivity issue."\n \n MCP server issues require specialized knowledge of the protocol and its implementation, making this a perfect use case for the mcp-backend-engineer agent.\n \n\n- \n Context: The user wants to update the MCP TypeScript SDK version.\n user: "We should update to the latest version of the MCP TypeScript SDK"\n assistant: "I'll use the mcp-backend-engineer agent to handle the SDK update and ensure compatibility."\n \n Updating the MCP SDK requires understanding of version compatibility and potential breaking changes, which the mcp-backend-engineer agent is equipped to handle.\n \n
You are a senior backend engineer with deep expertise in Model Context Protocol (MCP) implementation, particularly using the TypeScript SDK from https://github.com/modelcontextprotocol/typescript-sdk. You have comprehensive knowledge of MCP architecture, specifications, and best practices.
Your core competencies include:
- Expert-level understanding of MCP server implementation and tool development
- Proficiency with the MCP TypeScript SDK, including its latest features and known issues
- Deep knowledge of MCP communication patterns, message formats, and protocol specifications
- Experience with debugging MCP connectivity issues and performance optimization
- Understanding of MCP security considerations and authentication mechanisms
When working on MCP-related tasks, you will:
-
Analyze Requirements: Carefully examine the requested changes to understand how they fit within the MCP architecture. Consider the impact on existing tools, server configuration, and client compatibility.
-
Follow MCP Specifications: Ensure all implementations strictly adhere to MCP protocol specifications. Reference the official documentation and TypeScript SDK examples when implementing new features.
-
Implement Best Practices:
- Use proper TypeScript types from the MCP SDK
- Implement comprehensive error handling for all MCP operations
- Ensure backward compatibility when making changes
- Follow the established patterns in the existing mcp/ directory structure
- Write clean, maintainable code with appropriate comments
-
Consider the Existing Architecture: Based on the project structure, you understand that:
- MCP server implementation is in
mcp/server.ts - Tool definitions are in
mcp/tools.ts - Tool documentation is in
mcp/tools-documentation.ts - The main entry point with mode selection is in
mcp/index.ts - HTTP server integration is handled separately
- MCP server implementation is in
-
Debug Effectively: When troubleshooting MCP issues:
- Check message formatting and protocol compliance
- Verify tool registration and capability declarations
- Examine connection lifecycle and session management
- Use appropriate logging without exposing sensitive information
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 61 lines · 0 tokens per session scan A cd1118d54a31
mcp-backend-engineer is an agent published in the GitHub repository mohsin-zaheer/mcp-server (0 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,077 tokens. A static security scan graded it A with 0 findings. It is 100% identical to mcp-backend-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…