Hey everyone
I wanted to share a project I’ve been working on recently: MCP Suite, a complete collection of 22 MCP (Model Context Protocol) servers designed to support developers across the entire software development lifecycle.
The idea was to go beyond a single tool and instead create a cohesive ecosystem of MCP servers that can actually talk to each other.
What is MCP Suite?
MCP Suite is a TypeScript monorepo that provides intelligent, composable servers covering:
Code & repository management
Scrum / Agile project management
Time tracking and productivity
Project economics & cost awareness
Developer utilities and automation
Knowledge and context sharing across tools
Each server focuses on a specific responsibility, but they’re not isolated.
The key part: server-to-server communication
All MCP servers in the suite communicate through a typed event system.
This allows workflows like:
A project event triggering updates in time tracking
Code changes influencing project metrics
Agile planning data flowing into reporting or analysis tools
The goal is to treat MCP servers like building blocks, not silos.
Why I built this
I noticed that most dev tools solve one problem really well, but fall apart when you try to connect everything together. With MCP Suite, I wanted to explore what happens when:
Hey everyone I wanted to share a project I’ve been working on recently: MCP Suite, a complete collection of 22 MCP (Model Context Protocol) servers designed to support developers across the entire software development lifecycle.
The idea was to go beyond a single tool and instead create a cohesive ecosystem of MCP servers that can actually talk to each other.
What is MCP Suite?
MCP Suite is a TypeScript monorepo that provides intelligent, composable servers covering:
Code & repository management
Scrum / Agile project management
Time tracking and productivity
Project economics & cost awareness
Developer utilities and automation
Knowledge and context sharing across tools
Each server focuses on a specific responsibility, but they’re not isolated.
The key part: server-to-server communication
All MCP servers in the suite communicate through a typed event system. This allows workflows like:
A project event triggering updates in time tracking
Code changes influencing project metrics
Agile planning data flowing into reporting or analysis tools
The goal is to treat MCP servers like building blocks, not silos.
Why I built this
I noticed that most dev tools solve one problem really well, but fall apart when you try to connect everything together. With MCP Suite, I wanted to explore what happens when:
Context is shared
Tools are composable
Automation spans multiple domains (code, planning, economics)
Everything is open source, modular, and meant to be extended or reused.
Feedback welcome
I’d love feedback from:
People experimenting with MCP
Tool builders
Anyone interested in AI-assisted developer workflows
Repo here https://github.com/fedcal/Tech-MCP
Happy to answer questions or discuss design choices!