A server registry
Organize hosted and private MCP servers around the work your agents perform.
Everything connected. Nothing accidental.
Give each agent a focused profile. See which tools are connected, which permissions are active, and where a request goes.
Start building⠿ 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
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.
A 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