> ## Documentation Index > Fetch the complete documentation index at: https://docs.cloudhumans.com/llms.txt > Use this file to discover all available pages before exploring further. # List MCP servers > Every MCP server registered for this tenant, including the ones CloudHumans provides to everyone. Start here: the ids returned are what the update, delete and probe operations take. Credentials are never part of the answer — `credentialsStored` only says whether one is on file. ## OpenAPI ````yaml /api-reference/specs/claudia/v1.json get /v1/tenants/{tenant}/mcp-servers openapi: 3.0.1 info: title: Claudia API version: 1.0.0 servers: - url: https://api.cloudhumans.com/claudia description: Production - url: https://api.cloudhumans.com/claudia/staging description: Staging security: - bearerAuth: [] tags: - name: MCP Servers description: >- The MCP servers your agents can call tools on. Registering one here is what makes its tools selectable in an agent; the credentials it needs are stored encrypted and never read back. - name: Knowledge Base Content description: Read, search and edit the content that answers your customers. - name: Content Quality description: Rewrites proposed for content that is answering your customers badly. - name: Playground description: >- Talk to one of your agents as if you were a customer, without touching a real conversation. - name: Project Settings description: >- Read and change how a ClaudIA project behaves — the settings screens of the ClaudIA app, as an API. - name: Content Improvements description: Answers Claudia proposes for questions your content does not cover yet. - name: Knowledge Bases description: The knowledge bases your account can manage. - name: Content Sources description: The sites Claudia crawls to keep a knowledge base in sync. paths: /v1/tenants/{tenant}/mcp-servers: get: tags: - MCP Servers summary: List MCP servers description: >- Every MCP server registered for this tenant, including the ones CloudHumans provides to everyone. Start here: the ids returned are what the update, delete and probe operations take. Credentials are never part of the answer — `credentialsStored` only says whether one is on file. operationId: listMcpServers parameters: - name: tenant in: path description: >- Tenant whose MCP servers you are managing. Get it from the backoffice `GET /auth/v1/me/claudia-projects`, which answers with the tenant your credentials cover. A tenant your credentials do not cover is indistinguishable from one that does not exist. required: true schema: type: string responses: '200': description: The MCP servers this tenant can use. content: application/json: schema: type: array items: $ref: '#/components/schemas/McpServer' '400': description: The request could not be answered as written. content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Missing, expired or invalid credentials. '403': description: The credentials hold no account allowed to manage this content. content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: >- No such resource, or none these credentials can reach — the two are deliberately indistinguishable. content: application/json: schema: $ref: '#/components/schemas/Error' '429': description: Rate limit applied by the API gateway. Back off and retry. components: schemas: McpServer: required: - authType - credentialsStored - customHeaders - id - name - platformOwned - slug - url - verified type: object properties: id: type: string description: Use this id to update, delete or re-probe this server. example: 6683f1c2a4b19e0012ab34cd name: type: string description: Display name, as shown in the Tools screen. example: Acme Orders slug: type: string description: >- Stable key derived from the name: lowercased, with every run of non-alphanumeric characters collapsed into `_`. Agent configurations reference a server by this key, so renaming a server changes it and is not a cosmetic edit. Unique within the tenant. example: acme_orders url: type: string description: >- The MCP endpoint agents call. Used exactly as stored once `verified` is true. example: https://mcp.acme.com/mcp authType: type: string description: >- How Claudia authenticates to this server. `none` sends no credential; `bearer` sends the stored secret as `Authorization: Bearer `; `apiKey` sends it as `x-api-key`; `forwarded_user` stores no secret and forwards the end user's own token at call time; `oauth` stores no secret either and lets the CloudHumans MCP gateway resolve the contact's custodied session. example: bearer enum: - none - bearer - apiKey - forwarded_user - oauth credentialsStored: type: boolean description: >- Whether a secret is stored for this server. The secret itself is never returned by this API — to change it, send the new value in full. Always false for `none`, `forwarded_user` and `oauth`, which store no secret by design, and for platform-owned servers, whose credential is held by the platform. example: true customHeaders: type: object additionalProperties: type: string description: >- Extra headers sent on every call to this server. Header names are lowercased on save, and the ones owned by the auth and tenant pipeline (`authorization`, `x-api-key`, `x-tenant`, `x-authorization`, `x-account`, `x-tenant-name`) are dropped — send credentials through `credentials`, not here. example: '{"x-acme-region":"br"}' description: >- Extra headers sent on every call to this server. Header names are lowercased on save, and the ones owned by the auth and tenant pipeline (`authorization`, `x-api-key`, `x-tenant`, `x-authorization`, `x-account`, `x-tenant-name`) are dropped — send credentials through `credentials`, not here. example: x-acme-region: br verified: type: boolean description: >- Whether this url was probed successfully and is used as stored. False keeps the legacy behaviour of appending `/mcp` to the url at call time, so a server whose url already ends in the MCP path answers 404 until it is verified. example: true platformOwned: type: boolean description: >- Whether CloudHumans owns this server. Platform-owned servers are provided to every tenant and are listed so agents can reference them, but they cannot be changed or deleted — those attempts answer 422. example: false createdAt: type: string description: >- When the server was registered (ISO-8601). Absent on platform-owned servers, which are not stored per tenant. example: '2026-08-10T14:32:05Z' nullable: true updatedAt: type: string description: When it last changed (ISO-8601). Absent until the first change. example: '2026-08-10T18:20:41Z' nullable: true description: An MCP server your agents can call tools on. Error: required: - error type: object properties: error: type: string description: What went wrong. example: 'Forbidden: token holds no claim for the requested account' description: Something the caller needs to fix. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ````