Skip to main content
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.
Managed Deep Agents is in private beta, available on LangSmith Cloud in the US region only. Join the waitlist to request access.

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.

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

MCP connector

Load tools from remote MCP servers.

LangSmith connector

Expose constrained LangSmith capabilities to untrusted callers.

Identity

Authenticate callers required by the LangSmith connector.

CLI reference

Look up connector project file rules.