DEV Community

Cover image for MCP Servers for Agentic Dev Platforms

MCP Servers for Agentic Dev Platforms

Juraj on May 22, 2025

For the past couple of months, the concept of MCP has been booming. MCP (Model Context Protocol) was developed and released by the end of 2024 by A...
Collapse
 
rishabh_bajpai_57d64cac3b profile image
Rishabh Bajpai

I think MCP is great if you are integrating it in an ai platform like cursor and Claude which can by default use nlp to create actual db queries. However I tried to do a setup for integrating it into my own app which has my own llm models and whatnot. The project is completely from scratch so no Claude or cursor. What I found out that’s it’s just some flexible structure behind the scenes. I wrote my own mcp server for Postgres and it sort of felt redundant. Maybe I did not understand mcp clearly but if i am to create mcp endpoints and then call those endpoints according to user query which by the way I would have to generate by nlp. What is the point of mcp then ? If anyone could explain it to, please do, I will highly appreciate it. According to my understanding though, it might be good for already built ai agents like Claude and cursor but not for a completely custom product where agent is just a part of a project.

Collapse
 
petarcvit profile image
Petar Cvitanović

Hey, I had thoughts similar to yours. At first glance, it was just another way to wrap your existing APIs and endpoints.
However, when I dug a bit deeper, I found that MCP allows you to expose actions and resources to the agents in a way that makes them aware of what they can work with.
For example, if you want your agent to work with your Grafana instance and create dashboards, the agent would need to call the Grafana API. But in this case, it has no way to know what the API looks like, what endpoints to call, and what to expect. Through an MCP server, the agent knows what actions it can call and what inputs/outputs are expected (this is sorted through how MCPs are designed to have special endpoints telling the agent what it can use). I think of it as an interface that a service provider (Grafana in the example) can implement to allow agents to interact with it.
In its implementation, it is using HTTP (if we are talking about SSE servers), so it might seem like a simple proxy, but it's more about conforming APIs to a standard that agents can communicate with

Collapse
 
rishabh_bajpai_57d64cac3b profile image
Rishabh Bajpai

I agree, in the end I think it’s about standardisation for ai agents.

Collapse
 
srbhr profile image
𝚂𝚊𝚞𝚛𝚊𝚋𝚑 𝚁𝚊𝚒

MCPs are here to stay, Google is also doubling down on it!

Collapse
 
karadza profile image
Juraj

Yes!

Collapse
 
nevodavid profile image
Nevo David

yeah this is awesome tbh, making all that setup easier is huge for me - you think more teams will switch to this kinda shared approach or do people hang on to old ways outta habit?

Collapse
 
karadza profile image
Juraj

The old ways are not that old at this moment still 😅
We shall see!

Collapse
 
fernandezbaptiste profile image
Bap

💪

Collapse
 
karadza profile image
Juraj

💪

Collapse
 
tmnt-12 profile image
Théo Marceau

👀

Collapse
 
karadza profile image
Juraj

👀👀

Collapse
 
layer91 profile image
Laviggi Ayer

Cool!

Collapse
 
karadza profile image
Juraj

🤗

Collapse
 
jmilic1 profile image
Jura Milić

Cool article!

Collapse
 
karadza profile image
Juraj

Thanks!

Collapse
 
lmercep profile image
Luka

Great context example

Collapse
 
karadza profile image
Juraj

🙏

Collapse
 
jakovg1 profile image
Jakov

Pretty cool feature, thanks for sharing :D

Collapse
 
karadza profile image
Juraj

My pleasure!