Back to Community
Agent MCP: The Multi-Agent Framework That Changed How I Build Software
Confident_Chest5567 May 13, 2025
302 likes
# Agent MCP: The Multi-Agent Framework That Changed How I Build Software
https://preview.redd.it/6wft4ewq1l0f1.jpg?width=1009&format=pjpg&auto=webp&s=bdba9f8a8b6ce52d5a3ef3bf3b801b5bb5dbf7f7
Quick update on my dev environment: I've completely moved from **Cursor** to **Claude Code Max** and **RooCode**.
**Why?**
* No more middlemen limiting the model's capabilities.
* Significantly lower costs and errors.
If you want **raw AI power** without artificial constraints, these direct integrations are the way to go. This post is for those ready to take AI coding to the next level.
# The Core Innovation: Persistent Context & Coordinated Agents
After months of hitting limitations with single-AI assistants, I built **Agent MCP** \- a coordination framework that lets multiple AI agents work together on complex projects. Here's what makes it different from anything you've tried before:
The biggest game-changer is the **Main Context Document (MCD)** approach. Before writing a line of code, I create a comprehensive blueprint of the entire system (architecture, API endpoints, data models, UI components). This becomes the shared "ground truth" for all agents.
Unlike standard AI sessions that forget everything, Agent MCP maintains:
* **RAG-based knowledge retrieval:** Agents can query specific information without context stuffing.
* **File status tracking:** Prevents conflicts when multiple agents modify the same codebase.
* **Task coordination:** Agents know what others are working on and don't duplicate work.
* **Project context database:** Central storage for critical information that persists across sessions.
# How The Multi-Agent System Actually Works ⚙️
The framework uses a hierarchical model:
1. **Admin Agent:** Coordinates work, breaks down tasks, maintains the big picture.
2. **Worker Agents:** Specialized by capability (frontend, backend, data, testing).
3. **Auto Mode:** The most powerful feature - agents autonomously work through tasks without constant prompting.
Worker agents operate in a **Plan/Act protocol**:
* **Plan Mode:** Query project context, check file status, determine dependencies.
* **Act Mode:** Execute precisely, update file metadata, record implementation notes.
* **Memory Workflow:** Each completed task enriches the knowledge base with implementation details.
# Real-World Results
I have built and launched multiple full-stack apps with Agent MCP in a couple of hours that would have taken me a couple of days:
* Frontend components implemented in parallel by one agent while another built APIs.
* Components were properly synchronized because agents shared knowledge.
* Each agent documented its work in the central context system.
* Complex features implemented without me having to manage context limitations.
* Each agent works perfectly well with MCP tools so you can have an agent that tests using playwright and another one implementing.
# Key Technical Features That Make This Possible
* **Embeddings-based RAG system:** Indexes all project files for semantic retrieval.
* **SQLite state database:** Maintains project state between sessions.
* **Visual dashboard:** Real-time monitoring of agent activity and relationships.
* **Context optimization:** Stores information centrally to reduce token usage.
* **Task parallelization:** Identifies independent tasks for concurrent execution.
# Open Source & Feedback
I've open-sourced the entire framework at: [**https://github.com/rinadelph/Agent-MCP**](https://github.com/rinadelph/Agent-MCP)
Would love feedback from others building with multiple AI agents. What are your experiences?
https://preview.redd.it/1q9xlmn52l0f1.png?width=2539&format=png&auto=webp&s=23fd2373421916323bd1b8eb142be28e6b6ccc36
# My opinion after 2 months 🗓️
After 2 months of almost daily use, I've found the most valuable aspect is the **dramatic reduction in context-switching**. The agents maintain deep knowledge of implementation details I'd otherwise have to remember or re-explain. For complex systems, this is a complete **game-changer**.
If anybody wants to reach out to discuss ideas, my discord is: basicxchannel
Comments
More Community
View allSomeone did a deep dive into Cursor Agent and discovered that it was literally just Claude Code with a process that does search and replace to brand it as Cursor Agent
[https://gist.github.com/jasonkneen/4c065df2d7a95610e4fd30c3e3398b17](https://gist.github.com/jasonkneen/4c065df2d7a95610e4fd30c3e3398b17)
D
DrySalamander9728 178
How I use Cursor 10+ hours a day without torching my Claude Opus 4.6 limits
Anyone else here doing full-stack Next.js in Cursor and watching the Claude quota evaporate before lunch? I used to be in the same boat — massive context windows from all the components, pages, and DB logic would smoke the default limits fast. Not anymore. I’ve been on this setup for weeks and basically never hit a wall while still getting top-tier answers. Here’s exactly what I do: **1. .cursorrules is non-negotiable** I keep one in the root of every project. The key line I added: “Never explain the code to me. Just output the code blocks.” That single rule saves me thousands of output tokens a day. No more walls of “here’s what I changed and why” — just the goods. **2. Stopped using Cursor’s built-in Claude quota** I killed the default Cursor Pro subscription for the heavy stuff. Instead I use my own API keys and point Cursor’s “OpenAI Compatible” base URL at LLM Router Gateway. Inside [llmrouter](https://llmrouter.app/) routing settings I set up simple tags routing like this: * **UI & CSS tweaks**: gemini-3.1-flash → gpt-5.4-mini * **Deep backend / complex logic**: claude-opus-4.6 → deepseek-v3.2 * **General / quick questions**: llama-4-scout I sorted the fallback chains by speed vs intelligence. The router auto-detects the query type, so 90% of my UI polish and small fixes go to Gemini (basically free + huge context). I only actually hit Claude Opus 4.6 when I’m doing nasty database refactors or tricky architecture stuff. My Anthropic bill dropped \~70% overnight. **3. Cmd+K for everything small** Don’t open the full chat sidebar just to rename a variable or extract a component. Highlight the code, hit Cmd+K, let a fast model handle the inline edit. Saves a ton of tokens and feels way snappier. That’s it. Super simple but it completely changed how much I can actually use Cursor in a day. How are you all managing the limits? Using a Cursor Team? Or did you build your own router hacks too? Drop your setups — always looking to steal better ideas.
Y
Youssef_Wardi 310
Cursor V3 is a significant regression
So I used to be a big cursor fan - striked the right balance between trusting the AI and being able to check the work. The new version however, sucks. Worktrees are now essentially AI initiated magic git commands that require manual approval, which is slow and annoying, and means I have to read through a bunch of git guff, and I have to wait like a minute before it does any real work for it to essentially do something that can be duplicated with a script, and it doesn't work well half the time - it had to retry twice to apply worktree changes! The new agent screen is pretty useless, because now you need to go and select a bunch of information that previously would be entirely obvious from context i.e. alt-tabbing into a specific repo's IDE. I don't like this direction and if they continue, I might start looking at competitors. Cursor is clearly aimed at and used by developers who can read code and want to read the code produced by AI. I use Claude Code if I want to just trust the AI.
E
ExaminationNo8522 212
Introducing Cursor 3
We’re introducing Cursor 3. It is simpler, more powerful, and built for a world where all code is written by agents, while keeping the depth of a development environment. With the new Cursor, you can run as many agents as you want, everywhere you want: locally, in a worktree, on remote ssh, and in the cloud. And it has the best parts of the editor available when you need them. The new interface is available as a separate window that complements the IDE. Update Cursor to try it. We recently launched Composer 2, a frontier model with high limits. Then, with cloud, we gave agents their own computers so they can work truly autonomously. And now with Cursor 3, we’re releasing a new interface to collaborate with agents on software.
L
lrobinson2011 184
Cursor 3 out now
Cursor 3 out now
G
Graniteman 125
They kinda cute
They kinda cute
S
sugandalai 828