What "Agents Having Tools" Means
Through 2023, LLMs were essentially text-in, text-out functions.
In 2024, function calling let LLMs call external tools. But each vendor (OpenAI, Anthropic, Google) used a different API spec, so a tool you wrote ran on one model only.
To unify the fragmentation, Anthropic released MCP (Model Context Protocol) in late 2024. It is an open standard that lets any model access tools and context the same way.
Analogy: USB-C standardized device cables. MCP is doing the same for AI agent tools.
The Three Core Ideas in MCP
1. Client-Server Architecture
MCP is a protocol between MCP servers (tool providers) and MCP clients (AI models).
- MCP Server: exposes a set of tools (e.g., filesystem MCP, GitHub MCP, Postgres MCP)
- MCP Client: any LLM (Claude, GPT, Gemini, Marblo…) connects the same way
Build one MCP server, and every MCP-compatible client can use it.
2. Three Standard Interfaces
- Resources: read-only data (files, DB query results, API responses)
- Tools: callable functions (file writes, query execution, notifications)
- Prompts: reusable prompt templates
Most practical scenarios fit into these three abstractions.
3. Standard Message Format
JSON-RPC 2.0–based standard messages. Models discover what an MCP server exposes and call it without prior training.
Why MCP Changed the Agent Industry
Tool Ecosystem Growth
The standard started a community MCP server ecosystem. By 2026:
- Official MCP servers: filesystem, Git, GitHub, Slack, Postgres, SQLite, Brave Search, Puppeteer, etc.
- Community MCPs: Notion, Linear, Figma, Jira, AWS, GCP, and many internal-system adapters
Write a tool once as MCP-compatible, and every MCP-compatible LLM can use it.
Standardized Internal System Integration
In enterprise environments, the hardest part has usually been integrating with internal systems (ERP, CRM, internal DBs, intranets). With MCP:
- Wrap your internal ERP API in an MCP server once
- Agents call it identically regardless of which LLM
- Security policies (auth, ACLs) consolidate in the MCP server layer
You can switch model vendors without rewriting integrations, and internal assets stay behind the MCP server layer.
MCP's Security Model
A common question: "Isn't giving AI agents access to internal DBs risky?"
MCP is explicit about security:
- Explicit permission delegation: users decide which MCP servers to trust
- Sandboxing: each MCP server can run in an isolated process
- Audit logs: every tool call is recorded
In particular, local execution environments keep data on-machine. Marblo (local desktop agent) + internal MCP server combinations give agents tool access without ever sending code to the cloud.
MCP in Marblo
Marblo is designed MCP-native. In the workspace:
- Add/manage MCP servers via GUI
- Scope per-agent MCP server permissions
- View MCP call logs alongside the kanban board in real time
Multi-tool pipelines like Slack notification → Linear ticket → GitHub PR are possible without writing extra code.
What to Consider for In-house Adoption
- Which systems should you expose via MCP? Decide priorities first.
- How to design the permission model? Least privilege per agent role.
- Who maintains internal MCP servers? Assign clear ownership.
These three are exactly what we work through in the diagnostic stage of In-house Adoption Consulting.
Wrap-up
MCP is the infrastructure that lets AI agents use real tools in a standard way. Once it settles, we expect the next standard to cover agent-to-agent collaboration.
In our view, teams that build their internal tool integrations on MCP now will have an easier time adopting agents later. Marblo is built on this standard.
Wrapping up
The Hypemarc Builder Community will keep sharing what we learn while building and operating AI agents, along with resources worth exploring. We'll continue gathering useful resources to share with fellow builders.
- Open chat: AI Builders
- Adoption advice and inquiries: Contact form
- Get the next post: Blog RSS · AI resource library