Connect tools and capabilities to Managed Deep Agents

Managed Deep Agents discovers connector modules under connectors/. Each file directly under that folder is a connector; you do not register connectors in the agent entry. Every connector module exports a named connector created from the connectors namespace (for example connectors.mcp(...)); a TypeScript export default fails the build.

​

Connector types

For the full project layout, see the CLI project file reference. The current mda CLI does not include workspace MCP server management commands. Do not use older deepagents mcp-servers ... examples for Managed Deep Agents projects.

​

Choose the right integration

For example, the GitHub connector prepares repositories in a sandbox, while the GitHub channel receives App webhooks.

​

Combine connectors with authored tools

Use custom tools for business logic, private APIs, database access, and other project-owned code. Use custom middleware for cross-cutting behavior around model calls, tool calls, lifecycle hooks, retries, limits, and data handling. MCP connector tools are appended to the tools you define in the agent file. LangSmith capabilities are exposed on separate HTTP routes scoped by identity.

​

Test and deploy

Test the project locally with mda dev, then deploy it with mda deploy. Open deployment traces in LangSmith to inspect model calls, tool calls, errors, and latency. Connector misconfiguration usually surfaces during local startup or first tool load. LangSmith capability calls return 401 without a resolved identity and 403 when ownership checks fail.

​

Next steps

---