This legacy concepts overview remains available by URL. For the canonical concepts docs, use Agent Architecture, Tool System, MCP, and A2A Protocol.
The Mental Model
| Component | What it does | When you need it |
|---|---|---|
| Agent | LLM-powered reasoning engine that can take actions | Always - this is your starting point |
| Tools | Functions the agent can call to interact with the world | When your agent needs to do more than chat |
| MCP Server | Standardized protocol for exposing tools to any agent | When you want reusable, shareable tool packages |
| Deployment | Run your agent as an API endpoint | When you’re ready to integrate with your app |
Agents
An Agent is an LLM with instructions and capabilities. At minimum, it needs:- A name for identification
- A model (e.g.,
gpt-4o,claude-sonnet) - Instructions defining its behavior
Tools
Tools are functions your agent can call. They bridge the gap between “knowing” and “doing.”- Built-in - Celesto provides common tools like weather, web search, and more
- Custom - Define your own Python functions as tools
- MCP Servers - Connect to standardized tool servers
MCP (Model Context Protocol)
MCP is a standard for packaging and sharing tools. Think of it like an API specification for agent capabilities. Why MCP matters:- Reusability - Build once, use with any MCP-compatible agent
- Isolation - Tools run in their own server process
- Ecosystem - Access tools built by the community
Deployment
Once your agent works locally, deploy it to make it accessible as an API.- Local API
- Celesto Cloud
- Self-Hosted
Putting It Together
Here’s the typical progression:Next Steps
Build an Agent
Deep dive into the Agent API
Add Tools
Learn how to connect tools
Build MCP Server
Create reusable tool packages
Deploy
Ship your agent to production