A server registry
Organize hosted and private MCP servers around the work your agents perform.
The MCP operating layer
DOJO / TOOL SYSTEMSAgentDojoConnect with intention.
A home for the tools your agents use. Organize MCP servers, connect private systems, and make access deliberate, visible, and reviewable.
Hosted tools. Private connections. Clear boundaries.MCP-native workflowsPrivate connectorsScoped permissionsExecution visibility
A place for every capability
Small tools. A connected system.
Give each agent a focused profile. See which tools are connected, which permissions are active, and where a request goes.
⠿ TOOL REGISTRYProfile / Research assistant
DocumentsSearch & retrieveRead only
CRMCustomer contextRead only
CalendarAvailabilityScoped
Internal APIProject recordsPrivate
profile: research-assistant tools: - documents.search - crm.contacts.read - internal.projects.read policy: read-only environment: sandbox
Illustrative workspace · Sample data
The toolkit
Explore all featuresEverything connected. Nothing accidental.
Precise access
Describe which capabilities belong to each agent and keep credentials outside its prompt.
Reusable profiles
Build a focused tool profile once and use it across your agent workflows.
Developer-friendly setup
Keep connection details and tool contracts inspectable alongside your implementation.
Private systems, included
Connect internal services while keeping their access boundaries explicit.
A visible execution trail
Trace tool calls, errors, and execution context when diagnosing agent behavior.
Connect a server
Bring a hosted MCP service or your own internal tool.
Define the profile
Choose the capabilities the agent needs for its task.
Inspect the work
Review tool usage and refine access as the workflow evolves.
The manual
All resources Good systems start with good contracts.
⠿Tool design
Tool design · 1 min read
Design a tool profile around a task.
Start with what the agent needs to accomplish, then choose its capabilities.
Read the guide⠿Connections
Connections · 1 min read
Bring private tools into the loop.
Give internal systems an explicit place in your agent architecture.
Read the guide⠿Operations
Operations · 1 min read
A useful log tells you what happened.
Make agent execution understandable to the next person investigating it.
Read the guide⠿MCP engineering
MCP engineering · 9 min read
What Is an MCP Gateway? Architecture, Security and Deployment
An MCP gateway is the policy and routing layer between AI agents and the MCP servers they use. It keeps tool access observable, authenticated, and constrained while teams connect more servers.
Read the guide⠿MCP engineering
MCP engineering · 10 min read
How to Host a Remote MCP Server in Production
A remote MCP server needs more than a public URL. Production hosting requires deployment discipline, OAuth, secret isolation, scaling, monitoring, and a clean example your agents can actually call.
Read the guide⠿MCP engineering
MCP engineering · 11 min read
How to Build an MCP Server: Complete Developer Guide
To build an MCP server, start with one useful tool, define the input schema, add authentication, test the call path, and deploy it behind a platform that can govern production usage.
Read the guideA few things to knowGood questions.
Good questions.
Clear answers.
Is AgentDojo an agent framework?
AgentDojo focuses on the tools and access layer around an agent. Your existing application or agent framework remains responsible for its own workflow.
Can we connect internal systems?
Private connectors are part of the product direction. Tell us which systems and access boundaries your team needs during onboarding.
What happens when I sign up?
You create an AgentDojo account. Hosted resources, paid plans, and private deployments require separate activation.
Build the right tool environment.
Start with one agent, one useful task, and a clear set of capabilities.
Start building