The agent writes the function flawlessly. The function calls a column that doesn’t exist.
You sigh, open psql, run \d users, copy the actual schema back into the chat. The agent apologises. The function is now correct. You did the integration by hand, again, like you’ve done a hundred times this year. Open a tab, copy something, paste it back. Switch to Jira, find the ticket, paste the title in. Open Figma, screenshot the frame, drag it in.
The agent is brilliant at the code. The agent is blind to every system your code talks to.
MCP — the Model Context Protocol — is the fix. It’s a wire format for letting agents call typed tools that talk to external systems. Instead of you copy-pasting the Postgres schema, the agent runs postgres.describe_table("users") itself, sees the result, and writes a function against the actual columns. Instead of you reading the Jira ticket, it runs jira.get_ticket("AUTH-412") and reads the title, description, and acceptance criteria directly.
This isn’t theoretical anymore. Every major AI coding tool added MCP support this year — Claude Code, Codex, opencode, Copilot, Cursor. Whatever you use, the protocol is the same. The MCP server you install for Jira works across all of them.
What people actually run:
- Issue trackers — Jira, Linear, GitHub Issues. The agent reads the ticket it’s working on, posts updates, closes it on merge.
- Databases — Postgres, MySQL, SQLite. “Check the actual schema before you write this query.” No more guessing column names.
- Cloud consoles — AWS, Cloudflare, Vercel. List buckets, check deployment status, read logs without leaving the editor.
- Design tools — Figma. The agent reads the component spec directly instead of you describing it in prose.
- Browser automation — Playwright. The agent navigates a staging site, fills a form, screenshots the result.
The test: if the answer to “why did you do it that way?” is “I had to guess because I couldn’t see the source,” there’s probably an MCP server that closes the gap. The integration moves from “you, by hand” to “the agent, in-flow.”
For the per-tool setup (where servers are configured, scopes, transport options) see MCP servers.