ReferenceArchestra MCP Server

Archestra MCP Server

Ask an agent to create another agent, install an MCP server, or build an app through Archestra's built-in MCP tools. Tool calls use the access of the account authenticated to Archestra. Tool names start with archestra__; the reference uses their short names.

Give an Agent These Tools

New agents start with some built-in tools already assigned; the initial selection depends on enabled features. You can add or remove tools later on the agent's Tools, Skills & Knowledge tab.

Use Manual to assign tools explicitly, or All with exclusions. See Choose What the Agent Can Use for how these modes work. For gateways, change Tools & Knowledge under Settings; see Choose Its Tools.

Permissions

Assigning a tool does not grant access to the resources it manages. Each tool entry lists the RBAC permission and any additional access requirements checked for the authenticated account.

  • RBAC permission: links to the Permissions reference. None means no additional RBAC permission; the tool still enforces its own access checks.
  • Granted per item: requires access to the specific agent, app, or other resource. See Granular Access Control.
  • Additional requirements: notes in the tool entry cover restrictions such as ownership or an acting user. Guardrails policies also apply to tool calls.

Tools Reference

Find tool inputs, output fields, and access requirements by topic.

Find a tool by name

Identity

Chat

Tool Discovery

Skills

Files

Code Sandbox

Apps

Projects

Agent Runtime

Agents

Knowledge Management

MCP Servers

MCP Gateways

Tool Assignment

Guardrails

Limits

Logs

Teams

Plugins