# Reference

> Look up environment variables, permissions, API endpoints, built-in MCP tools, and the Apps SDK

Look up an exact value here: an environment variable, a permission, an endpoint, or a built-in tool.

You can manage Archestra in three ways, and all three check the same [permissions](https://archestra.ai/docs/reference/permissions):

- **Web app:** for people.
- **[Platform API](https://archestra.ai/docs/reference/api):** for scripts and CI, with an API key.
- **[Archestra MCP Server](https://archestra.ai/docs/reference/archestra-mcp-server):** for agents. Its built-in tools create agents, install MCP servers, and query knowledge, as the person using the agent.

Deployment-wide settings that the web app does not show are [environment variables](https://archestra.ai/docs/admin/deployment/configuration). An [MCP App](https://archestra.ai/docs/chat/apps) calls platform tools through the [Apps SDK](https://archestra.ai/docs/reference/apps-sdk), as the person viewing it.

## Explore

- [Permissions](https://archestra.ai/docs/reference/permissions.md): What each built-in role can do, and every permission a custom role can hold
- [API Reference](https://archestra.ai/docs/reference/api.md): Find Archestra API endpoints by task, with request and response fields alongside each operation
- [Archestra MCP Server](https://archestra.ai/docs/reference/archestra-mcp-server.md): Every built-in tool an agent uses to manage Archestra, with its inputs and required permission
- [Apps SDK Reference](https://archestra.ai/docs/reference/apps-sdk.md): The window.archestra SDK, styling, security model, and authoring tools for MCP Apps
- [Archestra CLI](https://archestra.ai/docs/reference/archestra-cli.md): The archestra program on your device, with the commands that start, stop, update, and remove the MCP bridge
