> ## Documentation Index > Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt > Use this file to discover all available pages before exploring further. # List curated MCP adapters > Returns the curated MCP integrations Ankra knows how to connect: each adapter's transport, default or example URL, the credential headers it needs, and the tools it recommends. The list is built into Ankra and the same for every organisation. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /api/v1/org/mcp-servers/catalog openapi: 3.1.0 info: title: FastAPI version: 0.1.0 servers: - url: https://platform.ankra.app security: [] tags: - name: Organisation IAM description: >- Custom organisation roles and scoped role assignments for member and service-account identities. - name: Clusters description: Create, inspect and manage clusters, and the stacks deployed on them. - name: Managed Clusters description: Provider-managed control planes, driven through one common surface. - name: Imported Clusters description: Clusters that already existed and were connected to Ankra. - name: Cluster Access description: Kubeconfigs, service-account tokens and per-cluster access grants. - name: Kubernetes description: Read and act on the Kubernetes objects inside a cluster. - name: AWS Clusters description: >- Provision and manage self-managed k3s / kubeadm clusters on AWS EC2 in your own VPC. - name: Ankra Cloud Clusters description: >- Provision and manage self-managed kubeadm / k3s clusters on Ankra Cloud servers: a private network, a NAT router and a bastion per cluster. - name: DigitalOcean Clusters description: Provision and manage DigitalOcean Kubernetes clusters. - name: Hetzner Clusters description: Provision and manage Hetzner Kubernetes clusters. - name: OVH Clusters description: Provision and manage OVH Kubernetes clusters. - name: Scaleway Clusters description: Provision and manage Scaleway Kapsule clusters. - name: UpCloud Clusters description: Provision and manage UpCloud Kubernetes clusters. - name: Applications description: Deploy, configure and observe applications across the fleet. - name: Pipelines description: >- Pipeline definitions, the approval of the authority they declare, and the caches pipelines keep between runs. - name: Workspaces description: >- Personal workspaces on the organisation's CI pool where a repository's heavy commands run, and the repository profiles they are built from. - name: Deploy Targets description: >- Environments, the hosts registered to receive deployments, and the releases deployed to them. - name: Backups description: >- Backup vaults, restore points, protection posture and captures for stacks and application deployments; a completed capture is not a verified restore. - name: Stack Profiles description: Reusable stack definitions, their versions and sharing. - name: Services description: >- Versioned service packages and explicit sharing. Runtime admission is separate from publication. - name: Charts description: Browse the chart catalogue behind stacks and addons. - name: Helm description: Helm registries, credentials and the charts they expose. - name: Executions description: Long-running platform executions and their jobs. - name: Operations description: Cancel in-flight cluster operations and their jobs. - name: Chat description: Conversational sessions, plans and confirmable actions. - name: AI Management description: >- Customer agent lifecycle, authenticated identity and organisation automation controls. - name: AI Agent Runs description: Autonomous agent runs and their outcomes. - name: AI Tickets description: The AI ticket board, its sync connections and settings. - name: AI Playbooks description: Reusable playbooks the AI lanes execute. - name: AI Conditions description: Conditions that gate AI autonomy. - name: AI Remediation description: >- The organisation's auto-remediation policy: what the AI lanes may fix by themselves, and who approves the rest. - name: AI Engineering Handoffs description: Work the AI lanes escalate to a human engineer. - name: AI Environment description: The environment and base stacks AI demos deploy into. - name: MCP Servers description: >- Register the MCP servers the organisation's AI agents can call, choose their tools and grant them to roles. - name: Security description: Findings, advisories, SBOMs, compliance and posture. - name: Cost description: Cluster and fleet cost, rate cards and cost settings. - name: Decisions description: >- The decision ledger behind the Security and Cost queues: proposals a surface computed, the approve and set-aside decisions people took on them, and the receipts of running them. - name: Usage description: >- What your organisation used of Ankra - vCPU-hours, playgrounds, managed services, hosted logs and metrics, and AI - per meter and period, with how completely it was measured and whether a published rate applies. - name: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - name: Account description: >- Your own account: the contact email Ankra mails when it differs from your sign-in address. - name: Account Tokens description: Personal access tokens for the API and CLI. - name: Credentials description: The shared credential store. - name: AWS Credentials description: >- AWS credentials: access keys or CloudFormation-onboarded STS roles for cost, EKS and self-managed provisioning. - name: Ankra Cloud Credentials description: >- Ankra Cloud API tokens, shared by the self-managed and managed Ankra Cloud lanes. - name: Azure Credentials description: Azure credentials and SSH keys. - name: DigitalOcean Credentials description: DigitalOcean credentials and SSH keys. - name: Hetzner Credentials description: Hetzner credentials and SSH keys. - name: OVH Credentials description: OVH credentials and SSH keys. - name: Scaleway Credentials description: Scaleway credentials. - name: UpCloud Credentials description: UpCloud credentials and SSH keys. - name: Data Source Credentials description: Credentials for metrics and log sources. - name: DNS Credentials description: Credentials for DNS providers. - name: Object Storage Buckets description: >- Buckets Ankra creates and manages on an organisation's own provider credentials. - name: DNS description: DNS zones and records, including custom organisation zones. - name: Cloudflare description: Cloudflare domains and the credentials behind them. - name: Avura description: >- The linked Avura organization, the domains it shares with Ankra Platform, and their DNS records. - name: Variables description: Organisation- and cluster-scoped variables. - name: Secret Slots description: >- Store secrets in Vault and reference them by ${SECRET_SLOT:} sentinel instead of by value. - name: SOPS description: Encrypt and decrypt values with the organisation SOPS config. - name: Alerts description: Alert integrations and ingest credentials. - name: Notifications description: Notification routes and their delivery targets. - name: Support description: Support tickets. - name: AI Settings description: Organisation AI provider, model catalog and per-function model settings paths: /api/v1/org/mcp-servers/catalog: get: tags: - MCP Servers summary: List curated MCP adapters description: >- Returns the curated MCP integrations Ankra knows how to connect: each adapter's transport, default or example URL, the credential headers it needs, and the tools it recommends. The list is built into Ankra and the same for every organisation. operationId: list_mcp_adapters_api_v1_org_mcp_servers_catalog_get parameters: - in: header name: authorization required: false schema: anyOf: - type: string - type: 'null' title: Authorization - in: header name: x-ankra-organisation-id required: false schema: anyOf: - type: string - type: 'null' title: X-Ankra-Organisation-Id responses: '200': description: The curated adapters content: application/json: schema: $ref: '#/components/schemas/MCPAdapterCatalog' '400': description: >- Missing or malformed Authorization header, or an organisation header the token cannot use content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' '401': description: Unknown, expired or revoked token content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' '403': description: >- The organisation header names an organisation the token cannot act in content: application/json: schema: $ref: '#/components/schemas/ContractDetailError' security: - BearerAuth: [] components: schemas: MCPAdapterCatalog: title: MCPAdapterCatalog type: object properties: adapters: type: array items: $ref: '#/components/schemas/MCPAdapter' required: - adapters ContractDetailError: example: detail: Cluster not found properties: detail: oneOf: - type: string - additionalProperties: true properties: {} type: object required: - detail type: object MCPAdapter: title: MCPAdapter type: object properties: key: type: string description: The adapter_key to register a server with. display_name: type: string description: type: string docs_url: type: string description: The vendor's documentation for its MCP server. transport: type: string enum: - stdio - http - sse url_placeholder: type: string description: An example URL to show in a form. It is not a real endpoint. url_default: type: string description: >- The vendor's hosted endpoint, or an empty string when the server is self-hosted. credentials: type: array items: $ref: '#/components/schemas/MCPAdapterCredential' read_tool_patterns: type: array items: type: string description: Tool name patterns Ankra treats as read-only for this adapter. recommended_tools: type: array items: type: string description: Tools suggested for allowed_tools. required: - key - display_name - description - docs_url - transport - url_placeholder - url_default - credentials - read_tool_patterns - recommended_tools MCPAdapterCredential: title: MCPAdapterCredential type: object properties: header: type: string description: The HTTP header the adapter sends the credential in. label: type: string description: A short name for the credential. secret: type: boolean description: >- Whether the credential is a secret. A secret one must be stored as a secret slot and passed by sentinel. value_prefix: type: string description: >- The scheme Ankra adds in front of a stored value that lacks it, for example "Bearer ". Present only for adapters that need one. description: type: string description: What the credential is and where to find it. required: - header - label - secret - description securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.