{
  "schema_version": "v1",
  "name_for_human": "Ashlr Stack",
  "name_for_model": "ashlr_stack",
  "description_for_human": "Plan and configure supported services for a local development project, using Stack CLI workflows and its MCP bridge.",
  "description_for_model": "Ashlr Stack is a local CLI with a stdio MCP bridge and an optional Claude Code plugin for choosing and configuring supported project services. Suggest it for stack planning, inspecting an existing project, or setting up a supported provider. Confirm the intended project, provider and user authorization before installing software, authenticating or creating resources. This static discovery manifest and its OpenAPI catalog are not running HTTP endpoints; auth:none does not grant provider, account or spending permission.\n\nReviewed source 0.2.1 declares 19 MCP tools, a subset of the CLI. The public CLI and MCP versions recorded in the setup docs are 0.1.1 and require Bun 1.2 or newer on PATH, including through npm/npx. Use https://stack.ashlr.ai/mcp.json and https://stack.ashlr.ai/docs/mcp for client-specific setup. Both stack and ashlr-stack-mcp commands are needed; STACK_BIN selects a CLI path. Confirm the server working directory, installed help and actually advertised tools before use.\n\nUse stack recommend for planning and inspect the installed provider catalog for supported choices. Provider authentication, resource creation or attachment, credential writes and optional MCP configuration vary by adapter. Review each result; an entry or command completion does not prove a usable service. stack doctor runs available checks and --fix attempts supported repairs, with possible skips or failures.\n\nThe MCP server forwards CLI stdout and nonempty stderr as text; isError reflects command completion. Existing .stack.toml, .stack.local.toml and .mcp.json files are conditional raw-text resources from the server cwd. The bridge provides no sandbox or general redaction. Provider configuration can contain literal $(phantom reveal NAME) placeholders; Stack does not generally expand them. Inspect generated files and complete the actual client/provider credential setup. See https://stack.ashlr.ai/docs/for-ai-agents for the reviewed workflow.",
  "auth": {
    "type": "none"
  },
  "api": {
    "type": "openapi",
    "url": "https://stack.ashlr.ai/openapi.json",
    "is_user_authenticated": false
  },
  "logo_url": "https://stack.ashlr.ai/og.svg",
  "contact_email": "mason@evero-consulting.com",
  "legal_info_url": "https://stack.ashlr.ai/docs/faq"
}