Skip to content

Ecosystem capability and skill fleet

Generated by scripts/generate_ecosystem_capability_catalog.py; do not edit by hand.

The repository-manager workspace manifest is the package authority. Each provider repository contributes one comprehensive canonical skill; former specialist skills are retained as WORKFLOW.md references inside that skill rather than separately advertised capabilities. This keeps discovery compact while preserving deep procedures.

Every governed connector also owns a capability bundle: signed manifest, ontology, SHACL shapes, mappings, fixtures, migrations, exact live tool-schema fingerprints, and certification metadata. Agent Utilities carries pinned manifest fallbacks for standalone GraphOS deployments, but the connector-owned bundle remains authoritative.

Current package coverage: 65/65 complete packages; 64/65 expose governed source-sync presets.

Package Manifest Bundle Source sync Tool schema Canonical skills OpenAI metadata MkDocs
ansible-tower-mcp yes yes yes yes one yes yes
archimate-mcp yes yes yes yes one yes yes
archivebox-api yes yes yes yes one yes yes
arr-mcp yes yes yes yes one yes yes
atlassian-agent yes yes yes yes one yes yes
audio-transcriber yes yes yes yes one yes yes
audiobookshelf-mcp yes yes yes yes one yes yes
caddy-mcp yes yes yes yes one yes yes
camunda-mcp yes yes yes yes one yes yes
ciso-assistant-api yes yes yes yes one yes yes
clarity-api yes yes yes yes one yes yes
container-manager-mcp yes yes yes yes one yes yes
data-science-mcp yes yes yes yes one yes yes
dockerhub-api yes yes yes yes one yes yes
documentdb-mcp yes yes yes yes one yes yes
egeria-mcp yes yes yes yes one yes yes
emerald-exchange yes yes yes yes one yes yes
erpnext-agent yes yes yes yes one yes yes
fan-manager yes yes yes yes one yes yes
firefly-iii-mcp yes yes yes yes one yes yes
genius-agent yes yes yes yes one yes yes
github-agent yes yes yes yes one yes yes
gitlab-api yes yes yes yes one yes yes
gramps-mcp yes yes yes yes one yes yes
home-assistant-agent yes yes yes yes one yes yes
jellyfin-mcp yes yes yes yes one yes yes
jena-mcp yes yes yes yes one yes yes
kafka-mcp yes yes yes yes one yes yes
keycloak-agent yes yes yes yes one yes yes
langfuse-agent yes yes yes yes one yes yes
leanix-agent yes yes yes yes one yes yes
legal-peripherals-mcp yes yes yes yes one yes yes
lgtm-mcp yes yes yes yes one yes yes
listmonk-api yes yes yes yes one yes yes
mattermost-mcp yes yes yes yes one yes yes
mealie-mcp yes yes yes yes one yes yes
media-downloader yes yes n/a n/a one yes yes
microsoft-agent yes yes yes yes one yes yes
nextcloud-agent yes yes yes yes one yes yes
objectstore-mcp yes yes yes yes one yes yes
okta-agent yes yes yes yes one yes yes
onetrust-api yes yes yes yes one yes yes
openbao-mcp yes yes yes yes one yes yes
owncast-agent yes yes yes yes one yes yes
paperless-ngx-mcp yes yes yes yes one yes yes
plane-agent yes yes yes yes one yes yes
portainer-agent yes yes yes yes one yes yes
postiz-agent yes yes yes yes one yes yes
pulselink-mcp yes yes yes yes one yes yes
qbittorrent-agent yes yes yes yes one yes yes
repository-manager yes yes yes yes one yes yes
rom-manager yes yes yes yes one yes yes
salesforce-agent yes yes yes yes one yes yes
scholarx yes yes yes yes one yes yes
searxng-mcp yes yes yes yes one yes yes
servicenow-api yes yes yes yes one yes yes
sql-mcp yes yes yes yes one yes yes
stirlingpdf-agent yes yes yes yes one yes yes
systems-manager yes yes yes yes one yes yes
technitium-dns-mcp yes yes yes yes one yes yes
tunnel-manager yes yes yes yes one yes yes
twenty-mcp yes yes yes yes one yes yes
uptime-kuma-agent yes yes yes yes one yes yes
vector-mcp yes yes yes yes one yes yes
wger-agent yes yes yes yes one yes yes

Validation contract

A release fails when a package is absent, advertises more than one canonical skill, has invalid skill metadata, lacks a signed bundle, or its live MCP tool schema differs from the connector-owned fingerprint. Direct skill execution and GraphOS-delegated execution are certified separately in the release validation matrix; this catalog describes packaged coverage, not a fabricated live result.

Runtime configuration stores only neutral aliases and secret references. Endpoints, credentials, raw identities, workstation names, and filesystem locations must never enter this generated page, capability manifests, trace attributes, or certification summaries.