SIsignalshq
MCP CONNECTOR

Connection details and setup steps for the MCP connector.

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.

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)
  • Auth
    OAuth 2
    Password
    Token URL: /auth/login

Response

Successful Response

mcp_enabledboolean required

Whether this organization may use the connector.

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

transportstring
auth_headerstring

Header carrying the credential.

auth_schemestring

Sent as Authorization: Bearer <api key>.

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

notesstring[]

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.

Changes

No recorded changes to this operation across all 1 revision of this API.