> ## Documentation Index
> Fetch the complete documentation index at: https://doc.featherhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard test surface: invoke an MCP tool by slug (FEATHER_MCP_CLIENT)

> Fire a real ``FEATHER_MCP_CLIENT`` invocation from the Integrations dashboard.

Verifies the parent connection is owned by the caller's org (404
otherwise), resolves the slug to ``(connection, tool)`` via
``ToolService.resolve_by_slug``, then dispatches through our MCP client →
the customer's MCP server (decrypt creds → open session → ``call_tool``).
This is the only non-agent way to exercise ``FEATHER_MCP_CLIENT``, so a
green result here is strong evidence the whole custom-MCP invoke path works
end-to-end. Returns the raw MCP result and emits an ``integration_tool_call``
Tinybird row with ``mode=feather_mcp_client`` / ``reason="ui_mcp_test_call"``.
An unresolved/disabled slug surfaces as ``ToolUnavailableError`` (400).



## OpenAPI

````yaml /api-reference/openapi.json post /v1/integrations/connections/{connection_id}/test-mcp-call
openapi: 3.1.0
info:
  title: Feather API
  description: >-
    Unified customer experience platform API. Manages identity, conversations,
    memory, agents, procedures, policies, model routing, knowledge bases,
    integrations, and runtime execution.
  version: 1.21.0
servers:
  - url: https://api-sandbox.featherhq.com
    description: Sandbox
  - url: http://localhost:8000
    description: Local dev
security: []
paths:
  /v1/integrations/connections/{connection_id}/test-mcp-call:
    post:
      tags:
        - integrations
      summary: 'Dashboard test surface: invoke an MCP tool by slug (FEATHER_MCP_CLIENT)'
      description: >-
        Fire a real ``FEATHER_MCP_CLIENT`` invocation from the Integrations
        dashboard.


        Verifies the parent connection is owned by the caller's org (404

        otherwise), resolves the slug to ``(connection, tool)`` via

        ``ToolService.resolve_by_slug``, then dispatches through our MCP client
        →

        the customer's MCP server (decrypt creds → open session →
        ``call_tool``).

        This is the only non-agent way to exercise ``FEATHER_MCP_CLIENT``, so a

        green result here is strong evidence the whole custom-MCP invoke path
        works

        end-to-end. Returns the raw MCP result and emits an
        ``integration_tool_call``

        Tinybird row with ``mode=feather_mcp_client`` /
        ``reason="ui_mcp_test_call"``.

        An unresolved/disabled slug surfaces as ``ToolUnavailableError`` (400).
      operationId: testMcpCallConnection
      parameters:
        - name: connection_id
          in: path
          required: true
          schema:
            type: string
            format: uuid
            title: Connection Id
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ConnectionTestMcpCallRequest'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConnectionTestMcpCallResponse'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Authentication required
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Resource not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - APIKeyHeader: []
components:
  schemas:
    ConnectionTestMcpCallRequest:
      properties:
        slug:
          type: string
          title: Slug
        input:
          additionalProperties: true
          type: object
          title: Input
      additionalProperties: false
      type: object
      required:
        - slug
      title: ConnectionTestMcpCallRequest
      description: >-
        Body for the dashboard ``FEATHER_MCP_CLIENT`` test surface (Step 8).


        Lets an operator fire a real ``custom_mcp`` MCP ``tools/call`` from the

        Integrations page to confirm the customer-MCP invoke path end-to-end

        (decrypt creds → open MCP session → ``call_tool``). It's the only
        non-agent

        way to exercise ``FEATHER_MCP_CLIENT``. ``input`` matches the resolved

        tool's ``input_schema``.
    ConnectionTestMcpCallResponse:
      properties:
        result:
          additionalProperties: true
          type: object
          title: Result
      type: object
      required:
        - result
      title: ConnectionTestMcpCallResponse
      description: Raw MCP ``tools/call`` result echoed back to the dashboard test surface.
    ErrorResponse:
      properties:
        error:
          type: string
          title: Error
        message:
          type: string
          title: Message
      type: object
      required:
        - error
        - message
      title: ErrorResponse
      description: Standard error response returned by all API error handlers.
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: x-api-key

````