---
title: "Connection details and setup steps for the MCP connector."
method: GET
path: "/internal/api/mcp/connection"
tags: ["MCP CONNECTOR"]
---

# Connection details and setup steps for the MCP connector.

`GET /internal/api/mcp/connection`

## Request

- Base URL: `https://api.signalshq.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.signalshq.io/internal/api/mcp/connection`
- Auth: OAuth 2
  - Password
  - Token URL: `/auth/login`

Everything the Settings page shows a firm wiring Elan into their AI stack.

Carries NO credential — ``<YOUR_API_KEY>`` is a placeholder in every
snippet. That keeps this response safe to render, screenshot and paste
into a support ticket, which is what people do with setup instructions
whatever the warning says.

## Response `200`

Successful Response

- McpConnectionResponse: Everything the Settings page needs to render connection details. Deliberately one call. The page has to answer "is this on, where do I point it, do I have a key, and how do I wire it up" together — split across four endpoints it renders half-configured states that read as bugs.
  - `mcp_enabled` boolean, required: Whether this organization may use the connector.
  - `server_url` string, required: The MCP endpoint. Must be entered EXACTLY as given — OAuth discovery compares this string rather than normalizing it. Empty when the server has no ELAN_MCP_RESOURCE_URL set, which means the deployment is not ready to accept connectors.
  - `transport` string
  - `auth_header` string: Header carrying the credential.
  - `auth_scheme` string: Sent as ``Authorization: Bearer <api key>``.
  - `active_key_count` integer, required: Live keys for this organization. Zero means the connector cannot be used yet however it is configured — the setup screen should lead with 'create a key' in that state.
  - `tools` McpConnectionTool[]
    - `name` string, required
    - `summary` string, required
  - `setup` McpSetupStep[]
    - `client` string, required: Which AI tool this snippet is for.
    - `instructions` string, required
    - `snippet` string: Copy-paste command or config. ``<YOUR_API_KEY>`` is a placeholder — the real key is NEVER interpolated here, so this response stays safe to render, screenshot and paste into a support ticket.
  - `notes` string[]: Caveats worth showing next to the steps rather than burying in docs — read-only scope, and that access follows the credential rather than the person holding it.

---

[API](https://skmtc.dev/signalshq/apis/signals-api.md) - [All operations](https://skmtc.dev/signalshq/apis/signals-api/llms.txt) - [OpenAPI document](https://skmtc.dev/signalshq/apis/signals-api/revisions/2c22af3b5576?raw)