nextcloud-agent

Nextcloud Agent

CLI or API | MCP | Agent

!PyPI - Version !MCP Server !PyPI - Downloads !GitHub Repo stars !GitHub forks !GitHub contributors !PyPI - License !GitHub !GitHub last commit (by committer) !GitHub pull requests !GitHub closed pull requests !GitHub issues !GitHub top language !GitHub language count !GitHub repo size !GitHub repo file count (file type) !PyPI - Wheel !PyPI - Implementation

Version: 2.0.0

Documentation — Installation, deployment, usage across the API, CLI, and MCP interfaces, and guidance for provisioning the backing Nextcloud instance are maintained in the official documentation.

---

Overview

Nextcloud Agent is a production-grade Agent and Model Context Protocol (MCP) server designed to interface directly with Nextcloud MCP Server for Agentic AI!.

---

Key Features

• Consolidated Action-Routed MCP Tools: Minimizes token overhead and eliminates tool bloat in LLM contexts by grouping methods into optimized, togglable tool modules.
• Enterprise-Grade Security: Comprehensive support for Eunomia policies, OIDC token delegation, and granular execution context tracking.
• Integrated Graph Agent: Built-in Pydantic AI agent supporting the Agent Control Protocol (ACP) and standard Web interfaces (AG-UI).
• Native Telemetry & Tracing: Out-of-the-box OpenTelemetry exports and native Langfuse tracing.

---

CLI or API

This agent wraps the Nextcloud MCP Server for Agentic AI! API. You can interact with it programmatically or via its integrated execution entrypoints.

Detailed instructions on how to use the underlying API wrappers, extended schema bindings, and developer SDK references are maintained in docs/index.md.

---

MCP

This server utilizes dynamic Action-Routed tools to optimize token overhead and maximize IDE compatibility.

Available MCP Tools

<!-- This table is auto-generated by python -m agent_utilities.mcp.readme_tools — do not edit by hand. -->

<!-- MCP-TOOLS-TABLE:START -->

Condensed action-routed tools (MCP_TOOL_MODE=condensed)

| MCP Tool | Toggle Env Var | Description | |----------|----------------|-------------| | nextcloud_calendar | CALENDARTOOL | Manage nextcloud calendar operations. | | nextcloud_contacts | CONTACTSTOOL | Manage nextcloud contacts operations. | | nextcloud_files | FILESTOOL | Manage nextcloud files operations. | | nextcloud_ingest_file | INGESTTOOL | Fetch a Nextcloud file over WebDAV and natively store it in the knowledge | | nextcloud_sharing | SHARINGTOOL | Manage nextcloud sharing operations. | | nextcloud_user | USERTOOL | Manage nextcloud user operations. |

Verbose 1:1 API-mapped tools (MCP_TOOL_MODE=verbose or both)

<details> <summary>26 per-operation tools — one per public API method (click to expand)</summary>

| MCP Tool | Toggle Env Var | Description | |----------|----------------|-------------| | nextcloud_copy_item | APITOOL | Alias for copy_resource to support MCP server action. | | nextcloud_copy_resource | APITOOL | Copy a file or directory. | | nextcloud_create_calendar_event | APITOOL | Alias for create_event to support MCP server action. | | nextcloud_create_contact | APITOOL | Invoke the create_contact operation. | | nextcloud_create_directory | APITOOL | Create a directory (MKCOL). | | nextcloud_create_event | APITOOL | Create an event with ICS data. | | nextcloud_create_folder | APITOOL | Alias for create_directory to support MCP server action. | | nextcloud_create_share | APITOOL | Create a share. | | nextcloud_delete_item | APITOOL | Alias for delete_resource to support MCP server action. | | nextcloud_delete_resource | APITOOL | Delete a file or directory. | | nextcloud_delete_share | APITOOL | Delete a share. | | nextcloud_get_properties | APITOOL | Helper to get properties of a path by listing its contents. | | nextcloud_get_user_info | APITOOL | Get current user info. | | nextcloud_get_user_quota | APITOOL | Get storage quota information. | | nextcloud_list_address_books | APITOOL | List address books. | | nextcloud_list_calendar_events | APITOOL | Alias for list_events to support MCP server action. | | nextcloud_list_calendars | APITOOL | List available calendars. | | nextcloud_list_contacts | APITOOL | List contacts in address book. | | nextcloud_list_contents | APITOOL | List files and folders in a directory using PROPFIND. | | nextcloud_list_events | APITOOL | List events in a calendar (returns basic info). | | nextcloud_list_files | APITOOL | Alias for list_contents to support MCP server action. | | nextcloud_list_shares | APITOOL | List all shares. | | nextcloud_move_item | APITOOL | Alias for move_resource to support MCP server action. | | nextcloud_move_resource | APITOOL | Move a file or directory. | | nextcloud_read_file | APITOOL | Download a file. | | nextcloud_write_file | APITOOL | Upload a file. |

</details>

_6 action-routed tool(s) · 26 verbose 1:1 tool(s). Each is enabled unless its <DOMAIN>TOOL toggle is set false; MCP_TOOL_MODE selects the surface (intent default — the six verb-tools, granular set loaded on demand · condensed action-routed · verbose 1:1 · both). Auto-generated — do not edit._ <!-- MCP-TOOLS-TABLE:END -->

Detailed tool schemas, parameter shapes, and validation constraints are preserved in docs/usage.md.

Dynamic Tool Selection & Visibility

This MCP server supports dynamic toolset selection and visibility filtering at runtime. This allows you to restrict the set of exposed tools in order to prevent blowing up the LLM's context window.

You can configure tool filtering via multiple input channels:

• CLI Arguments: Pass --tools or --toolsets (or their disabled counterparts --disabled-tools and --disabled-toolsets) during startup.
• Environment Variables: Define standard environment variables:
• MCP_ENABLED_TOOLS / MCP_DISABLED_TOOLS
• MCP_ENABLED_TAGS / MCP_DISABLED_TAGS
• HTTP SSE Request Headers: Pass custom headers during transport initialization:
• x-mcp-enabled-tools / x-mcp-disabled-tools
• x-mcp-enabled-tags / x-mcp-disabled-tags
• HTTP SSE Request Query Parameters: Append query parameters directly to your transport connection URL:
• ?tools=tool1,tool2
• ?tags=tag1

When query strings or parameters are supplied, an LLM-free Knowledge Graph resolution layer (using DynamicToolOrchestrator) matches query intents against known tool tags, names, or descriptions, with safe fallback and automated 24-hour background cache refreshing.

---

MCP Configuration Examples

<!-- MCP-CONFIG-EXAMPLES:START -->

Install the connector-focused [mcp] extra. Examples use nextcloud-agent[mcp] to add FastMCP / FastAPI through agent-utilities[mcp]; the required Agent Utilities core still carries epistemic-graph[full]. The [agent-runtime] extra additionally enables model orchestration.

stdio Transport (local IDEs — Cursor, Claude Desktop, VS Code)

{
  "mcpServers": {
    "nextcloud-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "nextcloud-agent[mcp]",
        "nextcloud-mcp"
      ],
      "env": {
        "MCP_TOOL_MODE": "intent",
        "CALENDARTOOL": "True",
        "CONTACTSTOOL": "True",
        "FILESTOOL": "True",
        "INGESTTOOL": "True",
        "NEXTCLOUD_PASSWORD": "your_password",
        "NEXTCLOUD_URL": "https://nextcloud.example.com",
        "NEXTCLOUD_USERNAME": "your_username",
        "SHARINGTOOL": "True",
        "USERTOOL": "True"
      }
    }
  }
}

Runtime references require an alias-aware launcher such as GraphOS. Other launchers must omit those entries and inject the resolved values through their own runtime secret boundary.

Streamable-HTTP Transport (networked / production)

{
  "mcpServers": {
    "nextcloud-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "nextcloud-agent[mcp]",
        "nextcloud-mcp",
        "--transport",
        "streamable-http",
        "--port",
        "8000"
      ],
      "env": {
        "TRANSPORT": "streamable-http",
        "HOST": "127.0.0.1",
        "PORT": "8000",
        "MCP_TOOL_MODE": "intent",
        "CALENDARTOOL": "True",
        "CONTACTSTOOL": "True",
        "FILESTOOL": "True",
        "INGESTTOOL": "True",
        "NEXTCLOUD_PASSWORD": "your_password",
        "NEXTCLOUD_URL": "https://nextcloud.example.com",
        "NEXTCLOUD_USERNAME": "your_username",
        "SHARINGTOOL": "True",
        "USERTOOL": "True"
      }
    }
  }
}

Alternatively, connect to a pre-deployed Streamable-HTTP instance by url:

{
  "mcpServers": {
    "nextcloud-mcp": {
      "url": "http://localhost:8000/nextcloud-mcp/mcp"
    }
  }
}

Run a reviewed container image as a least-privilege stdio child (no listener or published port):

docker run -i --rm \
  --read-only \
  --cap-drop=ALL \
  --security-opt=no-new-privileges \
  --pids-limit=256 \
  --tmpfs /tmp:rw,noexec,nosuid,nodev,size=64m \
  -e TRANSPORT=stdio \
  -e MCP_TOOL_MODE=intent \
  -e CALENDARTOOL=True \
  -e CONTACTSTOOL=True \
  -e FILESTOOL=True \
  -e INGESTTOOL=True \
  -e NEXTCLOUD_PASSWORD=your_password \
  -e NEXTCLOUD_URL=https://nextcloud.example.com \
  -e NEXTCLOUD_USERNAME=your_username \
  -e SHARINGTOOL=True \
  -e USERTOOL=True \
  registry.example.invalid/nextcloud-agent@sha256:<digest> nextcloud-mcp

For containerized network HTTP, supply an authenticated TLS ingress (or direct server TLS), exact MCP_ALLOWED_HOSTS, and an exact trusted-proxy CIDR policy through the operator-owned deployment profile. The generator does not emit an unauthenticated non-loopback listener.

_Auto-generated from the code-read env surface (MCP_TOOL_MODE + package vars) — do not edit._ <!-- MCP-CONFIG-EXAMPLES:END -->

<!-- BEGIN GENERATED: additional-deployment-options -->

Additional Deployment Options

nextcloud-agent can also run as a local container (Docker / Podman / uv) or be consumed from a remote deployment. The Deployment guide has full, copy-paste mcp_config.json for all four transports — stdio, streamable-http, local container / uv, and remote URL:

• Local container / uv — launch the server from mcp_config.json via uvx,

docker run, or podman run, or point at a local streamable-http container by url. The published container runs as a reviewed, least-privilege stdio child with no listener or published port by default (see the hardened docker run example above).

• Remote URL — connect to a server deployed behind Caddy at

http://nextcloud-mcp.arpa/mcp using the "url" key, or through any operator-supplied authenticated HTTPS ingress. Keep its URL, outbound identity references, trust profile, and exact MCP_ALLOWED_HOSTS in AgentConfig. <!-- END GENERATED: additional-deployment-options -->

Agent

This repository features a fully integrated Pydantic AI Graph Agent. It communicates over the Agent Control Protocol (ACP) and interacts seamlessly with the Agent Web UI (AG-UI) and Terminal interface.

Running the Agent CLI

To start the interactive command-line agent:

# Set credentials
export NEXTCLOUD_URL="your_value"
export NEXTCLOUD_USERNAME="your_value"
export NEXTCLOUD_PASSWORD="your_value"

# Run the agent server
nextcloud-agent --provider openai --model-id gpt-4o

Docker Compose Orchestration

The following docker/agent.compose.yml configures the Agent, Web UI, and Terminal Interface together:

version: '3.8'

services:
  nextcloud-agent-mcp:
    image: knucklessg1/nextcloud-agent:mcp
    container_name: nextcloud-agent-mcp
    hostname: nextcloud-agent-mcp
    restart: always
    env_file:
      - ../.env
    environment:
      - PYTHONUNBUFFERED=1
      - HOST=0.0.0.0
      - PORT=8000
      - TRANSPORT=streamable-http
    ports:
      - "8000:8000"
    healthcheck:
      test: ["CMD", "python3", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:8000/health')"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 10s
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"

  nextcloud-agent-agent:
    image: knucklessg1/nextcloud-agent:latest
    container_name: nextcloud-agent-agent
    hostname: nextcloud-agent-agent
    restart: always
    depends_on:
      - nextcloud-agent-mcp
    env_file:
      - ../.env
    command: [ "nextcloud-agent" ]
    environment:
      - PYTHONUNBUFFERED=1
      - HOST=0.0.0.0
      - PORT=9016
      - MCP_URL=http://nextcloud-agent-mcp:8000/mcp
      - PROVIDER=${PROVIDER:-openai}
      - MODEL_ID=${MODEL_ID:-gpt-4o}
      - ENABLE_WEB_UI=True
      - ENABLE_OTEL=True
    ports:
      - "9016:9016"
    healthcheck:
      test: ["CMD", "python3", "-c", "import urllib.request; urllib.request.urlopen('http://localhost:9016/health')"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 10s
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"

Detailed graph node architecture explanations, custom skill configurations, and agentic trace guides are available in docs/deployment.md.

---

Security & Governance

Built directly upon the enterprise-ready agent-utilities core, standard security parameters are fully supported:

Access Control & Policy Enforcement

• Eunomia Policies: Fine-grained, policy-driven tool authorization. Supports none, local embedded (mcp_policies.json), or centralized remote modes.
• OIDC Token Delegation: Compliant with RFC 8693 token exchange for flowing authenticating user credentials from Web UI / ACP → Agent → MCP.
• Scoped Credentials: Execution context runs restricted to the specific caller identity.

Runtime Security Grid

| Feature | Functionality | Enablement | |---------|---------------|------------| | Tool Guard | Sensitivity inspection with human-in-the-loop validation | Enabled by default | | Prompt Injection Defense | Input scanning, repetition monitoring, and recursive loop blocks | Enabled by default | | Context Safety Guard | Stuck-loop detectors and contextual overflow preemptive alerts | Enabled by default |

---

Environment Variables

<!-- ENV-VARS-TABLE:START -->

Package environment variables

| Variable | Example | Description | |----------|---------|-------------| | HOST | 0.0.0.0 | | | PORT | 8000 | | | TRANSPORT | stdio | options: stdio, streamable-http, sse | | ENABLE_OTEL | True | | | OTEL_EXPORTER_OTLP_ENDPOINT | http://localhost:8080/api/public/otel | | | OTEL_EXPORTER_OTLP_PUBLIC_KEY | secret-injected | | | OTEL_EXPORTER_OTLP_SECRET_KEY | secret-injected | | | OTEL_EXPORTER_OTLP_PROTOCOL | http/protobuf | | | EUNOMIA_TYPE | none | options: none, embedded, remote | | EUNOMIA_POLICY_FILE | mcp_policies.json | | | EUNOMIA_REMOTE_URL | http://eunomia-server:8000 | | | NEXTCLOUD_URL | https://nextcloud.example.com | | | NEXTCLOUD_USERNAME | your_username | | | NEXTCLOUD_PASSWORD | secret-injected | | | TLS_PROFILE | private-ca | AgentConfig named transport profile | | TLS_PROFILE_REF | secret://transport/provider | Direct runtime profile reference | | TLS_PROFILES_REF | secret://transport/catalog | Named runtime profile catalog | | FILESTOOL | True | | | USERTOOL | True | | | SHARINGTOOL | True | | | CALENDARTOOL | True | | | CONTACTSTOOL | True | | | INGESTTOOL | True | |

Inherited agent-utilities variables (apply to every connector)

| Variable | Example | Description | |----------|---------|-------------| | MCP_TOOL_MODE | intent | Tool surface: intent \| condensed \| verbose \| both | | MCP_ENABLED_TOOLS | — | Comma-separated tool allow-list | | MCP_DISABLED_TOOLS | — | Comma-separated tool deny-list | | MCP_ENABLED_TAGS | — | Comma-separated tag allow-list | | MCP_DISABLED_TAGS | — | Comma-separated tag deny-list | | MCP_CLIENT_AUTH | — | Outbound MCP child auth: oidc-client-credentials \| basic \| none | | OIDC_CLIENT_ID | — | OIDC client id (service-account auth) | | OIDC_CLIENT_SECRET_REF | secret://identity/oidc-client-secret | Runtime secret reference for the OIDC service account | | MCP_BASIC_AUTH_USERNAME | — | HTTP Basic username (MCP_CLIENT_AUTH=basic) | | MCP_BASIC_AUTH_PASSWORD_REF | secret://identity/mcp-basic-password | Runtime secret reference for HTTP Basic auth (MCP_CLIENT_AUTH=basic) | | DEBUG | False | Verbose logging | | PYTHONUNBUFFERED | 1 | Unbuffered stdout (recommended in containers) | | MCP_URL | http://localhost:8000/mcp | URL of the MCP server the agent connects to | | PROVIDER | openai | LLM provider for the agent | | MODEL_ID | gpt-4o | Model id for the agent | | ENABLE_WEB_UI | True | Serve the AG-UI web interface |

_23 package + 16 inherited variable(s). Auto-generated from .env.example + the shared agent-utilities set — do not edit._ <!-- ENV-VARS-TABLE:END -->

Every variable the server reads, grouped by purpose. See .env.example for a copy-paste starting point.

Connection & Credentials

| Variable | Description | Default | |----------|-------------|---------| | NEXTCLOUD_URL | Base URL of the Nextcloud instance | https://nextcloud.example.com | | NEXTCLOUD_USERNAME | Username (basic auth) | — | | NEXTCLOUD_PASSWORD | Password / app password (basic auth) | — | | TLS_PROFILE / TLS_PROFILE_REF | AgentConfig transport profile selector; peer verification is mandatory | — |

MCP server / transport

| Variable | Description | Default | |----------|-------------|---------| | TRANSPORT | stdio, streamable-http, or sse | stdio | | HOST | Bind host (HTTP transports) | 0.0.0.0 | | PORT | Bind port (HTTP transports) | 8000 | | MCP_TOOL_MODE | Tool surface: intent, condensed, verbose, or both | intent | | MCP_ENABLED_TOOLS / MCP_DISABLED_TOOLS | Comma-separated tool allow/deny list | — | | MCP_ENABLED_TAGS / MCP_DISABLED_TAGS | Comma-separated tag allow/deny list | — |

Tool toggles

Each action-routed tool can be disabled individually via its toggle env var (set to false): FILESTOOL, USERTOOL, SHARINGTOOL, CALENDARTOOL, CONTACTSTOOL. See the Available MCP Tools table above.

Telemetry & governance

| Variable | Description | Default | |----------|-------------|---------| | ENABLE_OTEL | Enable OpenTelemetry export | True | | OTEL_EXPORTER_OTLP_ENDPOINT | OTLP collector endpoint | — | | OTEL_EXPORTER_OTLP_PUBLIC_KEY / OTEL_EXPORTER_OTLP_SECRET_KEY | OTLP auth keys | — | | OTEL_EXPORTER_OTLP_PROTOCOL | OTLP protocol (e.g. http/protobuf) | — | | EUNOMIA_TYPE | Authorization mode: none, embedded, remote | none | | EUNOMIA_POLICY_FILE | Embedded policy file | mcp_policies.json | | EUNOMIA_REMOTE_URL | Remote Eunomia server URL | — |

---

Installation

Pick the extra that matches what you want to run:

| Extra | Installs | Use when | |-------|----------|----------| | nextcloud-agent[mcp] | Connector-focused MCP server (agent-utilities[mcp] — FastMCP/FastAPI + epistemic-graph[full]) | You only run the MCP server (smallest install / image) | | nextcloud-agent[agent] | Agent runtime (agent-utilities[agent-runtime,logfire] — model orchestration + epistemic-graph[full]) | You run the integrated agent | | nextcloud-agent[all] | Everything (mcp + agent + logfire) | Development / both surfaces |

# Connector-focused MCP server (includes the shared graph engine)
uv pip install "nextcloud-agent[mcp]"

# Agent runtime (adds model orchestration to the shared graph engine)
uv pip install "nextcloud-agent[agent]"

# Everything (development)
uv pip install "nextcloud-agent[all]"      # or: python -m pip install "nextcloud-agent[all]"

Container images (:mcp vs :agent)

One multi-stage docker/Dockerfile builds two right-sized images, selected by --target:

| Image tag | Build target | Contents | Entrypoint | |-----------|--------------|----------|------------| | knucklessg1/nextcloud-agent:mcp | --target mcp | nextcloud-agent[mcp] — connector-focused, includes epistemic-graph[full]; no model-orchestration stack | nextcloud-mcp | | knucklessg1/nextcloud-agent:latest | --target agent (default) | nextcloud-agent[agent] — agent runtime, model orchestration + epistemic-graph[full] | nextcloud-agent |

docker build --target mcp   -t knucklessg1/nextcloud-agent:mcp    docker/   # connector-focused MCP server
docker build --target agent -t knucklessg1/nextcloud-agent:latest docker/   # agent runtime

docker/mcp.compose.yml runs the connector-focused :mcp server; docker/agent.compose.yml runs the agent (:latest) with a co-located :mcp sidecar.

Knowledge-graph database (epistemic-graph)

Both [mcp] and [agent] carry the epistemic-graph engine through the required Agent Utilities core dependency (epistemic-graph[full]). The [mcp] extra keeps the server connector-focused; [agent] additionally enables model orchestration. Local deployments can use the bundled engine. For production — or to share one knowledge graph across multiple agents — run epistemic-graph as its own database container and point the agent at it instead of embedding it. Deployment recipes (single-node + Raft HA), connection config, and the full database architecture (with diagrams) are documented in the epistemic-graph deployment guide.

---

Documentation

The complete documentation is published as the official documentation site and is the recommended reference for installation, deployment, and day-to-day operation.

| Page | Contents | |---|---| | Installation | pip, source, uv, prebuilt Docker image | | Deployment | run the MCP server and the agent, Compose, Caddy + Technitium, env config | | Usage | the MCP tools, the NextcloudAPI client, the agent CLI | | Backing Platform | deploy Nextcloud with Docker | | Overview | the action-routed tool surface and ecosystem role | | Concepts | concept registry (CONCEPT:NC-*) |

---

Repository Owners

<img width="100%" height="180em" src="https://github-readme-stats.vercel.app/api?username=example&show_icons=true&hide_border=true&&count_private=true&include_all_commits=true" />

!GitHub followers !GitHub User's stars

---

Contribute

Contributions are welcome! Please ensure code quality by executing local checks before submitting pull requests:

• Format code using ruff format .
• Lint code using ruff check .
• Validate type-safety with mypy .
• Execute test suites using pytest

<!-- BEGIN agent-os-genesis-deploy (generated; do not edit between markers) -->

Deploy with agent-os-genesis

This package can be provisioned for you — skill-guided — by the agent-os-genesis universal skill (its single-package deploy mode): it picks your install method, seeds secrets to OpenBao/Vault (or .env), trusts your enterprise CA, registers the MCP server, and verifies it — the same machinery that stands up the whole Agent OS, narrowed to just this package. Ask your agent to "deploy nextcloud-agent with agent-os-genesis".

| Install mode | Command | |------|---------| | Bare-metal, prod (PyPI) | uvx nextcloud-mcp · or uv tool install nextcloud-agent | | Bare-metal, dev (editable) | uv pip install -e ".[all]" · or pip install -e ".[all]" | | Container, prod | deploy knucklessg1/nextcloud-agent:latest via docker-compose / swarm / podman / podman-compose / kubernetes | | Container, dev (editable) | deploy docker/compose.dev.yml (source-mounted at /src; edits live on restart) |

Secrets are read-existing + seeded via vault_sync — you are only prompted for what's missing.

<!-- END agent-os-genesis-deploy -->

<!-- BEGIN agent-utilities-deployment (generated; do not edit between markers) -->

Deploy with agent-utilities-deployment

Provision this package with the consolidated agent-utilities-deployment workflow. It selects an installed-package, editable-source, or immutable-container path; records only runtime secret and TLS-profile references in AgentConfig; and runs doctor, registration, policy, observability, and rollback gates. Ask your agent to "deploy nextcloud-agent with agent-utilities-deployment".

| Install mode | Command | |------|---------| | Installed package | uv tool install "nextcloud-agent[mcp]", then run nextcloud-mcp | | Editable source | uv pip install -e ".[agent]", then run nextcloud-mcp | | Immutable container | deploy knucklessg1/nextcloud-agent:latest (or a pinned @sha256:<digest>) through the operator-selected orchestrator |

The repository embeds no deployment profile, credential value, certificate path, or environment-specific endpoint. Supply those at runtime through AgentConfig and the configured secret provider.

<!-- END agent-utilities-deployment -->

<!-- GOVERNED-CAPABILITY:START -->

Governed capability contract

This package ships a compact canonical skill surface with specialist procedures kept as referenced workflows. The current MCP tools, skill metadata, connector_manifest.yml, ontology, mappings, shapes, fixtures, migrations, tool-schema fingerprints, and certification metadata form one versioned capability contract. Validate them together; do not rely on stale tool names or historical per-task skill wrappers.

Runtime endpoints, credentials, certificate trust, tenant identity, retention, and observability policy are deployment inputs and are never packaged values. See Configuration, trust, and privacy before enabling a network transport, connector ingestion, GraphOS delegation, or trace export. <!-- GOVERNED-CAPABILITY:END -->