Otto configuration

Configure Otto agents to access MCP servers and define their capabilities within your Ascend Project.

Organization

The otto.yaml configuration must be located within a dedicated otto directory in your Ascend Project:

Screenshot

File tree

├── otto
│   ├── agents
│   │   ├── custom_agent.md
│   ├── mcp.yaml
│   ├── otto.yaml
│   └── rules
│       └── demo_welcome.yaml
│       └── git_commits.yaml

Basic agent setup

Configure Otto agents in your otto.yaml file:

otto/otto.yaml

otto:
  agents:
    "Otto Chat":
      mcp_servers:
        - slack

Agent access control

Grant agents access to specific MCP servers configured in mcp.yaml (see MCP guide):

otto/otto.yaml

otto:
  agents:
    "Otto Chat":
      mcp_servers:
        - slack

    "Pipeline Monitor":
      mcp_servers:
        - slack

Access patterns:

• Specific agents: Only listed agents can access the MCP servers
• Granular control: Different agents can have different server access levels
• Multiple servers: In theory, agents can access multiple MCP servers simultaneously

note

Currently, Ascend natively supports the Slack messaging integration via @zencoderai/slack-mcp-server.

See the MCP guide for more information.

Next steps

After configuring Otto agents:

• Set up MCP servers following the MCP Setup Guide
• Configure Otto Automations
• Test agent functionality by triggering Otto actions