172.4K
AKMCP is the USB-C of AI tools.
Here’s what’s actually happening when Claude accesses GitHub, Notion, or Jira.
There are 3 parts:
→ MCP Host
The AI app you use. Claude Desktop, Cursor, Windsurf, VS Code.
This is where you type your prompt.
It decides when external data is needed.
→ MCP Client
Lives inside the host.
Handles connection to MCP servers.
One client per tool.
→ MCP Server
Wrapper around the tool.
GitHub, Notion, Jira, Slack, Postgres.
Each exposes actions in a standard JSON-RPC format.
Now the flow:
→ You say “create a Jira ticket”
→ Host routes to Jira client
→ Client calls MCP server
→ Server hits Jira API
→ Ticket created
→ Response comes back
No custom integration needed.
The server already exists.
The host already knows how to use it.
That’s the point.
Before MCP
→ M apps × N tools = M×N integrations
After MCP
→ M + N
→ Build once per tool
→ Works across every AI app
This is why GitHub, Notion, Slack, and Figma are shipping MCP servers.
Build once.
Works everywhere.
If you write backend APIs, you already understand this.
MCP is REST for the AI layer.
Save this. You’ll need it.
I teach backend engineering, system design, and Gen Al in 1:1 sessions
→ For working developers across US, Canada, UK,
Japan, Australia
[keyword backend, keyword systemdesign, keyword mcp, keyword aiarchitecture, keyword apis]
@akashcodeofficial
