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).

POST

integrations

connections

{connection_id}

test-mcp-call

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

curl --request POST \
  --url https://api-sandbox.featherhq.com/v1/integrations/connections/{connection_id}/test-mcp-call \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "slug": "<string>",
  "input": {}
}
'

{
  "result": {}
}

Authorizations

x-api-key

string

header

required

Path Parameters

connection_id

string<uuid>

required

Body

application/json

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.

slug

string

required

input

Input · object

Response

Successful Response

Raw MCP tools/call result echoed back to the dashboard test surface.

result

Result · object

required

Dashboard test surface: lease a provider token (FEATHER_API)Lease a provider token via ``FEATHER_API`` and prove it works. Opens ``lease_provider_token`` for the connection and, for Slack, calls ``auth.test`` with the leased token to echo the workspace name. The token is never returned — only the provider's identity response. Emits a ``feather_api_token_lease`` Tinybird row.

⌘I

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

curl --request POST \
  --url https://api-sandbox.featherhq.com/v1/integrations/connections/{connection_id}/test-mcp-call \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "slug": "<string>",
  "input": {}
}
'

{
  "result": {}
}