Can AI agents automate Unleash?

Unleash is automatable today through its Admin API. This record is the Unleash feature-flag product, hosted or self-hosted. The Admin API base path is the instance URL plus /api/admin. It manages flags, projects, environments, users, roles, and integrations. Requests send Authorization with a personal access token or a service account token. Service accounts are created under Admin settings, Service accounts. Personal tokens are created under Profile, Personal API tokens. OpenAPI is at /docs/openapi/ on the instance in v5.2 and later. The GitHub repository Unleash/unleash describes the project as open source and uses the GNU Affero General Public License v3.0. Unleash also documents backend and frontend SDKs for flag evaluation. The first-party MCP server calls the Admin API. The local server runs as npx @unleash/mcp and needs a personal access token that can create flags. Tools include create_flag, which creates a flag disabled by default. A remote MCP mode is hosted by the Unleash instance. An admin enables it under Admin settings, Remote MCP server. Remote mode uses OAuth 2.0 dynamic client registration and exchanges the login session for a personal access token valid for 24 hours. https://docs.getunleash.io/llms.txt is a first-party docs index. Connector catalogs were not opened. SDK language names were not copied into this record. Computer-use viability is unassessed. API scores 8. MCP scores 7. API is the best path because a service account token calls the Admin API without running a local MCP process or enabling dynamic client registration.

Best path today: api · Overall automatability: 8/10