bootstrap.example.yaml

# ============================================================================
# AI Registry — bootstrap file example
# ============================================================================
# Pass this file to the server with --bootstrap-file to load initial data.
# The server will upsert all entries on startup and then continue serving.
# Running it multiple times is safe — existing entries are skipped.
#
# Usage:
#   /server --bootstrap-file /etc/ai-registry/bootstrap.yaml
#
# Or via docker-compose (mount the file and set the flag via command/entrypoint):
#   command: ["/server", "--bootstrap-file", "/etc/ai-registry/bootstrap.yaml"]
#
# Supported formats: .yaml / .yml / .json
#
# This example also showcases the v0.2 fields:
#   • featured   — flag an entry for the home page carousel
#   • verified   — officially vetted badge
#   • tags       — free-form labels surfaced in listing filters
#   • readme     — long-form markdown rendered on the detail page
#   • capabilities (MCP versions) — free-form MCP capabilities JSON
#
# Authorization: MCP servers and agents are scoped directly to
# their owning publisher. Roles (Viewer/Editor/Reviewer/Admin) are granted to
# users and groups — either via the admin API or seeded here in `groups` +
# `grants` (idempotent, source = config). The group slugs below match the
# group-membership claim the dev Keycloak realm emits, so a federated user
# resolves to these grants on login.
# ============================================================================

publishers:
  - slug: "anthropic"
    name: "Anthropic"
    verified: true

  - slug: "openai"
    name: "OpenAI"
    verified: true

  - slug: "community"
    name: "Community"
    verified: false

  - slug: "genai-test"
    name: "GenAI Test"
    verified: false

# ── Groups ───────────────────────────────────────────────────────
# Slugs MUST match the group names the IdP emits in the group-membership claim
# (the dev Keycloak realm puts author@example.com in anthropic-core +
# anthropic-labs, and reviewer@example.com in registry-reviewers). The
# registry-reviewers group + its global Reviewer grant are seeded automatically
# from AUTH_REVIEWER_GROUP, so they are not repeated here.
groups:
  - slug: "anthropic-core"
    name: "Anthropic Core"
  - slug: "anthropic-labs"
    name: "Anthropic Labs"
  - slug: "openai-platform"
    name: "OpenAI Platform"
  # genai-test sandbox: separate author (Editor) and reviewer (Reviewer) groups
  # on the genai-test publisher, so the change-approval flow can be exercised
  # end-to-end. The dev Keycloak realm puts genai-author@example.com in
  # genai-test-authors and genai-reviewer@example.com in genai-test-reviewers.
  - slug: "genai-test-authors"
    name: "GenAI Test Authors"
  - slug: "genai-test-reviewers"
    name: "GenAI Test Reviewers"

# ── Grants ───────────────────────────────────────────────────────
# Give the seeded groups roles on their publishers. author@example.com is in
# anthropic-core + anthropic-labs, so they become a publisher Admin on
# anthropic (Admin via core, Editor via labs).
grants:
  - group: "anthropic-core"
    role: "admin"
    publisher: "anthropic"
  - group: "anthropic-labs"
    role: "editor"
    publisher: "anthropic"
  - group: "openai-platform"
    role: "editor"
    publisher: "openai"
  # genai-author@example.com authors on genai-test; genai-reviewer@example.com
  # approves. Separate groups keep the duties split (Reviewer is the sole approver).
  - group: "genai-test-authors"
    role: "editor"
    publisher: "genai-test"
  - group: "genai-test-reviewers"
    role: "reviewer"
    publisher: "genai-test"

# ── MCP Servers ───────────────────────────────────────────────────────────────
mcp_servers:
  # anthropic/filesystem — npm, stdio, two versions (v1 published, v2 draft)
  - publisher: "anthropic"
    slug: "filesystem"
    name: "Filesystem MCP Server"
    description: "Gives Claude read/write access to the local file system."
    repository_url: "https://github.com/anthropics/mcp-filesystem"
    public: true
    featured: true
    verified: true
    tags: ["filesystem", "storage", "official", "stdio"]
    readme: |
      # Filesystem MCP Server

      Gives an MCP host (Claude Desktop, Cursor, etc.) **scoped** read/write
      access to a directory on the local machine.

      ## Features

      - Read, write and list files in an allow-listed root
      - Glob-style search across the tree
      - Atomic writes with backup
      - Path traversal protection

      ## Quick start

      ```bash
      npx -y @anthropic/mcp-filesystem /path/to/workspace
      ```

      Then point your MCP host at the command above. The server is stdio-only
      — there is no network surface to harden.
    versions:
      - version: "1.0.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
          resources:
            subscribe: true
            listChanged: true
          logging: {}
        tools:
          - name: "read_file"
            description: "Read the contents of a file by absolute path."
            input_schema:
              type: "object"
              properties:
                path:
                  type: "string"
                  description: "Absolute path to the file"
              required: ["path"]
          - name: "write_file"
            description: "Write text to a file, creating it if necessary."
            input_schema:
              type: "object"
              properties:
                path:
                  type: "string"
                content:
                  type: "string"
              required: ["path", "content"]
            annotations:
              destructive: true
          - name: "list_directory"
            description: "List the entries of a directory."
            input_schema:
              type: "object"
              properties:
                path:
                  type: "string"
              required: ["path"]
        packages:
          - registry_type: "npm"
            identifier: "@anthropic/mcp-filesystem"
            version: "1.0.0"
            transport:
              type: "stdio"
      - version: "2.0.0"
        status: "draft"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
          resources:
            subscribe: true
            listChanged: true
          prompts:
            listChanged: true
          logging: {}
        tools:
          - name: "read_file"
            description: "Read the contents of a file by absolute path."
          - name: "write_file"
            description: "Write text to a file, creating it if necessary."
            annotations:
              destructive: true
          - name: "delete_file"
            description: "Delete a file. Rejected for paths outside the workspace."
            annotations:
              destructive: true
          - name: "list_directory"
            description: "List the entries of a directory."
          - name: "watch_path"
            description: "Subscribe to changes under a given path."
        packages:
          - registry_type: "npm"
            identifier: "@anthropic/mcp-filesystem"
            version: "2.0.0"
            transport:
              type: "stdio"

  # anthropic/computer-use — npm, SSE transport
  - publisher: "anthropic"
    slug: "computer-use"
    name: "Computer Use MCP Server"
    description: "Streams real-time desktop screenshots and control events over Server-Sent Events."
    repository_url: "https://github.com/anthropics/mcp-computer-use"
    public: true
    featured: true
    verified: true
    tags: ["desktop", "automation", "sse", "remote"]
    readme: |
      # Computer Use MCP Server

      Exposes the local desktop as an MCP resource. The host can ask the
      server to take a screenshot, move the mouse, type text, or click — and
      screen updates stream back over SSE in real time.

      > **Warning**
      > Computer Use gives an agent full control of the machine it runs on.
      > Run it inside a sandbox or VM unless you trust every tool call.

      ## Auth

      Per the MCP authorization spec this server is OAuth 2.1 with PKCE;
      discover metadata at `/.well-known/oauth-protected-resource`.
    versions:
      - version: "1.2.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
          resources:
            subscribe: true
        tools:
          - name: "screenshot"
            description: "Capture the current desktop as a PNG image."
          - name: "mouse_click"
            description: "Left-click at a screen coordinate."
            input_schema:
              type: "object"
              properties:
                x:
                  type: "integer"
                y:
                  type: "integer"
              required: ["x", "y"]
            annotations:
              destructive: true
          - name: "type_text"
            description: "Type a string as if from the keyboard."
            annotations:
              destructive: true
          - name: "key"
            description: "Press a named key (e.g. enter, tab, escape)."
        packages:
          - registry_type: "npm"
            identifier: "@anthropic/mcp-computer-use"
            version: "1.2.0"
            transport:
              type: "sse"
              url: "https://mcp.anthropic.com/computer-use/sse"
        # Hosted deployment of the same server — clients connect straight to
        # the URL, no package install. A version may carry packages, remotes,
        # or both; a remotes-only version is valid (hosted-only server).
        remotes:
          - type: "sse"
            url: "https://mcp.anthropic.com/computer-use/sse"

  # anthropic/memory — npm, HTTP transport, deprecated
  - publisher: "anthropic"
    slug: "memory"
    name: "Memory MCP Server"
    description: "Provides long-term memory storage for conversations. Deprecated: use anthropic/knowledge-base."
    repository_url: "https://github.com/anthropics/mcp-memory"
    public: true
    verified: true
    status: "deprecated"
    tags: ["memory", "deprecated"]
    readme: |
      # Memory MCP Server (deprecated)

      This server has been **replaced** by `anthropic/knowledge-base`, which
      ships a richer semantic store and supports streaming updates.

      Existing clients will keep working for the 1.x line, but no new
      features will land here.
    versions:
      - version: "1.0.0"
        status: "deprecated"
        status_message: "Replaced by anthropic/knowledge-base"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: false
        packages:
          - registry_type: "npm"
            identifier: "@anthropic/mcp-memory"
            version: "1.0.0"
            transport:
              type: "http"
              url: "https://mcp.anthropic.com/memory"

  # anthropic/github — npm, stdio, two published versions
  - publisher: "anthropic"
    slug: "github"
    name: "GitHub MCP Server"
    description: "Interact with GitHub repositories, issues, and pull requests."
    repository_url: "https://github.com/anthropics/mcp-github"
    public: true
    featured: true
    verified: true
    tags: ["github", "git", "devtools", "stdio"]
    readme: |
      # GitHub MCP Server

      A thin wrapper around the GitHub REST + GraphQL APIs exposed as MCP
      tools. Works with both personal access tokens and GitHub App
      installations.

      ## Tools

      | Tool | Description |
      |------|-------------|
      | `list_issues` | List issues in a repo |
      | `create_pr` | Open a new pull request |
      | `review_pr` | Post inline review comments |
      | `merge_pr` | Merge a PR (respects branch protections) |

      ## Auth

      Set `GITHUB_TOKEN` in the environment or supply an installation ID for
      GitHub App auth.
    versions:
      - version: "0.5.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
        packages:
          - registry_type: "npm"
            identifier: "@anthropic/mcp-github"
            version: "0.5.0"
            transport:
              type: "stdio"
      - version: "1.0.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
          resources:
            listChanged: true
          prompts: {}
        tools:
          - name: "list_issues"
            description: "List issues in a repository."
          - name: "get_issue"
            description: "Fetch a single issue with its comments."
          - name: "create_pr"
            description: "Open a new pull request."
            annotations:
              destructive: true
          - name: "review_pr"
            description: "Post inline review comments on a PR."
          - name: "merge_pr"
            description: "Merge a pull request (respects branch protections)."
            annotations:
              destructive: true
          - name: "search_code"
            description: "Search code across a repository using GitHub code search."
        packages:
          - registry_type: "npm"
            identifier: "@anthropic/mcp-github"
            version: "1.0.0"
            transport:
              type: "stdio"

  # openai/web-search — npm, streamable-http
  - publisher: "openai"
    slug: "web-search"
    name: "Web Search MCP Server"
    description: "Provides real-time web search capabilities via a streaming HTTP transport."
    repository_url: "https://github.com/openai/mcp-web-search"
    public: true
    featured: true
    verified: true
    tags: ["search", "web", "streamable-http", "remote"]
    readme: |
      # Web Search MCP Server

      Streams search results as they come in using MCP's streamable-HTTP
      transport. No polling, no artificial chunking — the host sees a new
      result the moment the upstream index returns it.

      ## Example

      ```json
      {
        "tool": "search",
        "args": { "query": "latest mcp spec changes", "limit": 10 }
      }
      ```
    versions:
      - version: "2.1.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
          logging: {}
        tools:
          - name: "search"
            description: "Search the web and stream results as they come in."
            input_schema:
              type: "object"
              properties:
                query:
                  type: "string"
                limit:
                  type: "integer"
                  default: 10
              required: ["query"]
          - name: "fetch_url"
            description: "Fetch a URL and return its extracted text content."
        packages:
          - registry_type: "npm"
            identifier: "@openai/mcp-web-search"
            version: "2.1.0"
            transport:
              type: "streamable-http"
              url: "https://mcp.openai.com/search"

  # openai/image-gen — OCI container + HTTP transport
  - publisher: "openai"
    slug: "image-gen"
    name: "Image Generation MCP Server"
    description: "Generate images from text prompts via a containerised HTTP endpoint."
    repository_url: "https://github.com/openai/mcp-image-gen"
    public: true
    verified: true
    tags: ["image", "multimodal", "oci", "http"]
    readme: |
      # Image Generation MCP Server

      Ships as an OCI image so you can run it anywhere a container runs —
      locally with `docker run`, on Kubernetes, or as a serverless job.

      ```bash
      docker run --rm -p 7060:7060 \
          -e OPENAI_API_KEY=sk-... \
          ghcr.io/openai/mcp-image-gen:1.0.0
      ```

      Images are returned inline as base64-encoded PNG via the MCP
      `generate_image` tool.
    versions:
      - version: "1.0.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: false
        packages:
          - registry_type: "oci"
            identifier: "ghcr.io/openai/mcp-image-gen"
            version: "1.0.0"
            transport:
              type: "http"
              url: "https://mcp.openai.com/image-gen"

  # openai/code-interpreter — streamable-http, draft (never published)
  - publisher: "openai"
    slug: "code-interpreter"
    name: "Code Interpreter MCP Server"
    description: "Execute Python code in a sandboxed environment and return results."
    repository_url: "https://github.com/openai/mcp-code-interpreter"
    public: true
    tags: ["python", "sandbox", "experimental"]
    readme: |
      # Code Interpreter MCP Server (draft)

      Runs arbitrary Python in a gVisor sandbox and streams stdout, stderr,
      and any generated files back to the host.

      This version is still **draft** — the tool signatures will change before
      the 1.0 release.
    versions:
      - version: "0.3.0"
        status: "draft"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
          resources:
            subscribe: true
        packages:
          - registry_type: "npm"
            identifier: "@openai/mcp-code-interpreter"
            version: "0.3.0"
            transport:
              type: "streamable-http"
              url: "https://mcp.openai.com/code-interpreter"

  # community/postgres — pypi, stdio
  - publisher: "community"
    slug: "postgres"
    name: "PostgreSQL MCP Server"
    description: "Community-maintained server for querying and managing PostgreSQL databases."
    repository_url: "https://github.com/community/mcp-postgres"
    public: true
    tags: ["database", "postgres", "sql", "stdio"]
    readme: |
      # PostgreSQL MCP Server

      Exposes a read-only (by default) PostgreSQL connection as MCP tools:

      - `query` — run a SQL SELECT and return rows
      - `describe_table` — list columns, types, indexes
      - `explain` — return a query plan

      Write tools (`insert`, `update`, `delete`) are gated behind the
      `--allow-writes` flag.
    versions:
      - version: "0.3.1"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
        tools:
          - name: "query"
            description: "Run a SQL SELECT and return rows."
            input_schema:
              type: "object"
              properties:
                sql:
                  type: "string"
              required: ["sql"]
          - name: "describe_table"
            description: "List columns, types, and indexes for a table."
          - name: "explain"
            description: "Return a query plan for a given SQL statement."
        packages:
          - registry_type: "pypi"
            identifier: "mcp-postgres"
            version: "0.3.1"
            transport:
              type: "stdio"

  # community/sqlite — pypi, stdio
  - publisher: "community"
    slug: "sqlite"
    name: "SQLite MCP Server"
    description: "Read and write SQLite databases using natural language."
    repository_url: "https://github.com/community/mcp-sqlite"
    public: true
    tags: ["database", "sqlite", "sql", "stdio"]
    readme: |
      # SQLite MCP Server

      Drop-in MCP server for working with local `.sqlite` / `.db` files.
      Perfect for poking at application databases, exports, or small
      datasets without spinning up a full Postgres instance.
    versions:
      - version: "1.2.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
          resources: {}
        packages:
          - registry_type: "pypi"
            identifier: "mcp-sqlite"
            version: "1.2.0"
            transport:
              type: "stdio"

  # community/kubernetes — OCI container, HTTP
  - publisher: "community"
    slug: "kubernetes"
    name: "Kubernetes MCP Server"
    description: "Manage Kubernetes clusters and workloads from your AI assistant."
    repository_url: "https://github.com/community/mcp-kubernetes"
    public: true
    tags: ["kubernetes", "cloud", "oci", "http"]
    readme: |
      # Kubernetes MCP Server

      Wraps `kubectl` + the Kubernetes API as MCP tools. Reads kubeconfig
      from the environment and honours the current context — **be careful
      which cluster you're pointing at.**

      Ships as an OCI image that can run as a sidecar next to your MCP host.
    versions:
      - version: "0.5.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
          resources:
            subscribe: true
            listChanged: true
          logging: {}
        tools:
          - name: "get_pods"
            description: "List pods in a namespace."
          - name: "logs"
            description: "Tail the logs of a pod/container."
          - name: "apply"
            description: "Apply a YAML manifest to the cluster."
            annotations:
              destructive: true
          - name: "delete"
            description: "Delete a resource by namespace, kind, and name."
            annotations:
              destructive: true
          - name: "describe"
            description: "Human-readable description of a resource."
        packages:
          - registry_type: "oci"
            identifier: "ghcr.io/community/mcp-kubernetes"
            version: "0.5.0"
            transport:
              type: "http"
              url: "http://localhost:8080"

  # community/dotnet-tools — nuget, stdio, private
  - publisher: "community"
    slug: "dotnet-tools"
    name: ".NET Tools MCP Server"
    description: "Wraps common .NET CLI tools (build, test, publish) as MCP primitives."
    repository_url: "https://github.com/community/mcp-dotnet-tools"
    public: false
    tags: ["dotnet", "nuget", "devtools"]
    readme: |
      # .NET Tools MCP Server (internal)

      Private to teams with a .NET-heavy stack. Exposes `dotnet build`,
      `dotnet test`, and `dotnet publish` as MCP tools so an agent can drive
      the full CI loop without shelling out.
    versions:
      - version: "1.0.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
        packages:
          - registry_type: "nuget"
            identifier: "MCP.DotNetTools"
            version: "1.0.0"
            transport:
              type: "stdio"

  # community/mcp-bridge — mcpb registry type, stdio
  - publisher: "community"
    slug: "mcp-bridge"
    name: "MCP Bridge Server"
    description: "Bridges legacy tool APIs into the MCP ecosystem using the mcpb packaging format."
    repository_url: "https://github.com/community/mcp-bridge"
    public: true
    tags: ["bridge", "mcpb", "interop"]
    readme: |
      # MCP Bridge

      Adapter for legacy function-calling tool APIs — point it at an OpenAPI
      spec or a Swagger file and it generates MCP tools on the fly. Ships as
      an `mcpb` bundle (Model Context Protocol Bundle format).
    versions:
      - version: "0.9.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
        packages:
          - registry_type: "mcpb"
            identifier: "mcp-bridge"
            version: "0.9.0"
            transport:
              type: "stdio"

  # community/multi-transport — multiple packages (npm + oci), two transports
  - publisher: "community"
    slug: "multi-transport"
    name: "Multi-Transport MCP Server"
    description: "Ships as both an npm package (stdio) and an OCI image (HTTP) — pick the deployment model you need."
    repository_url: "https://github.com/community/mcp-multi-transport"
    public: true
    tags: ["multi-transport", "stdio", "http", "example"]
    readme: |
      # Multi-Transport MCP Server

      A reference implementation showing how to ship the same logical server
      as **two** packages: an `npm` bundle for local stdio use, and an `oci`
      image for remote HTTP deployments. Clients pick whichever one suits
      their host.
    versions:
      - version: "1.0.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: true
          resources: {}
        packages:
          - registry_type: "npm"
            identifier: "@community/multi-transport"
            version: "1.0.0"
            transport:
              type: "stdio"
          - registry_type: "oci"
            identifier: "ghcr.io/community/mcp-multi-transport"
            version: "1.0.0"
            transport:
              type: "http"
              url: "http://localhost:3000"

  # genai-test/echo — published + public, so it shows under the genai-test
  # publisher in the read-only browse UI.
  - publisher: "genai-test"
    slug: "echo"
    name: "Echo MCP Server"
    description: "Minimal sandbox server that echoes its input back — seed entry for the genai-test publisher."
    repository_url: "https://github.com/genai-test/mcp-echo"
    public: true
    tags: ["sandbox", "example", "stdio"]
    readme: |
      # Echo MCP Server

      A throwaway server living under the **genai-test** publisher so the
      sandbox publisher has something to browse. Exposes a single `echo` tool.
    versions:
      - version: "1.0.0"
        status: "published"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: false
        tools:
          - name: "echo"
            description: "Return the input string unchanged."
            input_schema:
              type: "object"
              properties:
                text:
                  type: "string"
              required: ["text"]
        packages:
          - registry_type: "npm"
            identifier: "@genai-test/mcp-echo"
            version: "1.0.0"
            transport:
              type: "stdio"

  # genai-test/scratch — draft, so genai-author can edit it and genai-reviewer
  # can approve the first publish (exercises the change-approval flow).
  - publisher: "genai-test"
    slug: "scratch"
    name: "Scratch MCP Server"
    description: "Unpublished draft under genai-test — author edits it, reviewer approves the publish."
    repository_url: "https://github.com/genai-test/mcp-scratch"
    public: false
    tags: ["sandbox", "draft"]
    readme: |
      # Scratch MCP Server (draft)

      Sits in `draft` so a genai-test Editor can submit it and a genai-test
      Reviewer can approve the first published version.
    versions:
      - version: "0.1.0"
        status: "draft"
        protocol_version: "2025-03-26"
        capabilities:
          tools:
            listChanged: false
        packages:
          - registry_type: "npm"
            identifier: "@genai-test/mcp-scratch"
            version: "0.1.0"
            transport:
              type: "stdio"

# ── Agents ────────────────────────────────────────────────────────────────────
agents:
  # anthropic/code-review — published, public
  - publisher: "anthropic"
    slug: "code-review"
    name: "Code Review Agent"
    description: "Automatically reviews pull requests and suggests improvements."
    public: true
    featured: true
    verified: true
    tags: ["code-review", "git", "devtools", "official"]
    readme: |
      # Code Review Agent

      Reads a pull request diff and posts inline comments that flag bugs,
      style issues, and missing tests.

      ## What it's good at

      - Spotting copy/paste bugs
      - Catching missing null / error checks
      - Suggesting test cases for new branches

      ## What it's not

      It is **not** a replacement for human review on anything security- or
      architecture-sensitive. Use it as a first pass, not the final word.
    versions:
      - version: "1.0.0"
        status: "published"
        endpoint_url: "https://agents.anthropic.com/code-review"
        default_input_modes: ["text/plain"]
        default_output_modes: ["text/plain"]
        skills:
          - id: "review-pr"
            name: "Review Pull Request"
            description: "Analyse a PR diff and post inline comments"
            tags: ["git", "code-quality"]
          - id: "suggest-fix"
            name: "Suggest Fix"
            description: "Generate a code fix for a flagged issue"
            tags: ["code-quality"]
        authentication:
          - scheme: "Bearer"

  # anthropic/browser-agent — published, public, text + image I/O
  - publisher: "anthropic"
    slug: "browser-agent"
    name: "Browser Automation Agent"
    description: "Controls a real browser to fill forms, click buttons, and extract information from any website."
    public: true
    featured: true
    verified: true
    tags: ["browser", "automation", "multimodal", "official"]
    readme: |
      # Browser Automation Agent

      A headful browser agent. Give it a goal in plain English ("book me a
      table for two at 8pm") and it will navigate, click, type and screenshot
      its way to the result.

      ## I/O modes

      - **Input:** `text/plain`, `application/json`
      - **Output:** `text/plain`, `image/png` (screenshots)

      Screenshots are returned alongside text so your host can show the user
      what the agent actually did.
    versions:
      - version: "1.2.0"
        status: "published"
        endpoint_url: "https://agents.anthropic.com/browser"
        default_input_modes: ["text/plain", "application/json"]
        default_output_modes: ["text/plain", "image/png"]
        skills:
          - id: "navigate"
            name: "Navigate"
            description: "Open a URL in the browser"
            tags: ["browser", "automation"]
          - id: "click"
            name: "Click Element"
            description: "Click on a CSS selector"
            tags: ["browser", "automation"]
          - id: "screenshot"
            name: "Screenshot"
            description: "Capture the current viewport as a PNG"
            tags: ["browser", "visual"]
          - id: "extract"
            name: "Extract Data"
            description: "Pull structured data from a page using a schema"
            tags: ["browser", "data"]
        authentication:
          - scheme: "Bearer"

  # openai/data-analyst — published, public
  - publisher: "openai"
    slug: "data-analyst"
    name: "Data Analyst Agent"
    description: "Analyses structured datasets and produces charts and summaries."
    public: true
    featured: true
    verified: true
    tags: ["data", "analytics", "charts", "csv"]
    readme: |
      # Data Analyst Agent

      Accepts CSV, JSON, or plain-text datasets and returns a written
      analysis alongside any charts it decided to draw.

      ## Typical flow

      1. Host uploads a CSV via `text/csv` input
      2. Agent runs exploratory stats and picks an appropriate chart
      3. Agent replies with a written summary (`text/plain`), the generated
         chart (`image/png`), and the raw numbers (`application/json`)
    versions:
      - version: "0.9.0"
        status: "published"
        endpoint_url: "https://agents.openai.com/data-analyst"
        default_input_modes: ["text/plain", "application/json", "text/csv"]
        default_output_modes: ["text/plain", "image/png", "application/json"]
        skills:
          - id: "analyse-csv"
            name: "Analyse CSV"
            description: "Parse and summarise a CSV file"
            tags: ["data", "csv"]
          - id: "plot-chart"
            name: "Plot Chart"
            description: "Generate a chart from tabular data"
            tags: ["data", "visualisation"]
          - id: "sql-query"
            name: "SQL Query"
            description: "Run a SQL query against an uploaded file"
            tags: ["data", "sql"]
        authentication:
          - scheme: "ApiKey"

  # openai/research-agent — deprecated
  - publisher: "openai"
    slug: "research-agent"
    name: "Research Agent"
    description: "Searches the web and academic databases to answer deep research questions."
    public: true
    verified: true
    status: "deprecated"
    tags: ["research", "search", "deprecated"]
    readme: |
      # Research Agent (deprecated)

      Replaced by the newer `openai/deep-research` agent, which uses a
      long-horizon planner and can run for minutes without losing track of
      its sub-goals.

      The 0.5.x line will continue to respond but receives no new features.
    versions:
      - version: "0.5.0"
        status: "published"
        endpoint_url: "https://agents.openai.com/research"
        default_input_modes: ["text/plain"]
        default_output_modes: ["text/plain"]
        skills:
          - id: "web-search"
            name: "Web Search"
            description: "Search the public web"
            tags: ["search", "research"]
          - id: "paper-search"
            name: "Paper Search"
            description: "Query arXiv and Semantic Scholar"
            tags: ["research", "academic"]
        authentication:
          - scheme: "Bearer"

  # community/docs-writer — published, public
  - publisher: "community"
    slug: "docs-writer"
    name: "Documentation Writer"
    description: "Generates and maintains API documentation from source code."
    public: true
    tags: ["docs", "openapi", "devtools"]
    readme: |
      # Documentation Writer

      Reads a codebase and emits Markdown / OpenAPI documentation for public
      interfaces. Plug it into CI to keep your docs in sync with the code on
      every merge.
    versions:
      - version: "0.2.0"
        status: "published"
        endpoint_url: "https://community.example.com/agents/docs-writer"
        default_input_modes: ["text/plain"]
        default_output_modes: ["text/plain"]
        skills:
          - id: "generate-docs"
            name: "Generate Docs"
            description: "Extract and write API documentation from code"
            tags: ["docs", "openapi"]
        authentication:
          - scheme: "Bearer"

  # community/devops-agent — draft (never published)
  - publisher: "community"
    slug: "devops-agent"
    name: "DevOps Agent"
    description: "Provisions cloud infrastructure, manages CI/CD pipelines, and monitors deployments."
    public: true
    tags: ["devops", "cloud", "ci-cd", "experimental"]
    readme: |
      # DevOps Agent (draft)

      Experimental agent for driving cloud infrastructure. Currently
      targets AWS and GCP; Azure support is on the roadmap.

      > This version is **draft** — breaking changes will land before 1.0.
    versions:
      - version: "0.1.0"
        status: "draft"
        endpoint_url: "https://community.example.com/agents/devops"
        default_input_modes: ["text/plain", "application/json"]
        default_output_modes: ["text/plain", "application/json"]
        skills:
          - id: "deploy"
            name: "Deploy"
            description: "Deploy an application to a cloud provider"
            tags: ["cloud", "deploy"]
          - id: "monitor"
            name: "Monitor"
            description: "Check deployment health and logs"
            tags: ["cloud", "observability"]
          - id: "rollback"
            name: "Rollback"
            description: "Roll back to a previous release"
            tags: ["cloud", "deploy"]
        authentication:
          - scheme: "Bearer"
          - scheme: "ApiKey"

  # community/security-scanner — published, private
  - publisher: "community"
    slug: "security-scanner"
    name: "Security Scanner Agent"
    description: "Scans codebases and infrastructure configs for common vulnerabilities."
    public: false
    tags: ["security", "sast", "iac"]
    readme: |
      # Security Scanner Agent (internal)

      Runs static analysis across code and IaC (Terraform, Helm, k8s
      manifests) and returns a structured finding report.

      Kept **private** so that the list of known-vulnerable patterns isn't
      visible to unauthenticated users.
    versions:
      - version: "1.0.0"
        status: "published"
        endpoint_url: "https://community.example.com/agents/security-scanner"
        default_input_modes: ["text/plain", "application/json"]
        default_output_modes: ["text/plain", "application/json"]
        skills:
          - id: "scan-code"
            name: "Scan Code"
            description: "Static analysis for common CVEs"
            tags: ["security", "sast"]
          - id: "scan-infra"
            name: "Scan Infra"
            description: "Check IaC files for misconfigurations"
            tags: ["security", "iac"]
        authentication:
          - scheme: "ApiKey"