---
title: "Get connector detail"
method: GET
path: "/connector/{slug}"
tags: ["Connectors"]
---

# Get connector detail

`GET /connector/{slug}`

## Request

- Base URL: `https://api.elaichi.ai`
- URL: `https://api.elaichi.ai/connector/{slug}`
- Auth: HTTP bearer

Returns a connector's catalog detail plus `restricted`, which says whether the caller's restrictions block it; a restricted connector still resolves here but cannot be connected or executed. Platform catalog connectors need only `connector:view`. For an org-owned connector the response also carries its config, `owner_user_id` and `owner_member`, the capability fields `can_use`, `can_manage`, `can_share`, `can_transfer`, `can_delete`, `can_revoke_share`, `can_assign_owner` and `can_claim`, a short `access_summary` (counts plus a few names; page `GET /connector/{slug}/share` for the full list), and `shares`, present only when the caller is the owner or has an `edit` grant of their own. A custom connector the caller cannot see is `404`, never `403`.

## Path parameters

- `slug` string, required

## Headers

- `X-Organization-Id` string

## Response `200`

OK

- object
  - `restricted` boolean
  - `kind` 'catalog' | 'remote_mcp': `remote_mcp` for an organization's own remote MCP connector (`POST /connector` with `remote_mcp`, whose detail also carries `remote_mcp` and `auth`), `catalog` for every other connector. Read it instead of guessing from the slug.
  - `single_redirect_auth` boolean: Hint: exactly one auth method, it can redirect (OAuth), and it has no form fields and no `permissions_text`. `direct_connect_url` on the connect response stays authoritative.
  - `tool_count` integer: The provider's total. For a remote MCP connector that Elaichi publishes, the organization's switched-on tools once anyone in it has connected, and until then the length of the tool list Elaichi published for it (never 0 for a server that publishes tools).
  - `connect_notes` string, nullable: Remote MCP connectors only: markdown a person should read BEFORE connecting (an admin setting to turn on first, the plan it bills, which region or site to pick). The same text the sign-in page shows above its Connect button (the OAuth config's `permissions_text`). Render it as sanitized markdown. Null when there is none, and for every catalog connector. Detail only.
  - `connect_notes_link` string, uri, nullable: An https guide to that setup (the OAuth config's `documentation_link`). Null when unset.
  - `connect_blocked` object, nullable: Why a connection cannot be started on this connector right now, or null when it can. `oauth_app_required`: `byoa` is true, this organization has not added its own OAuth app, and the connector has no API-key option; `POST /connection` answers 409 `oauth_app_required` for it. Always null for a remote MCP connector. Detail only — the check reads the organization's app, which a list row does not.
    - `reason` 'oauth_app_required', required
    - `custom` boolean, required: True for an org-owned connector, whose OAuth app is part of its own definition (its Edit screen) rather than an organization override added on the connector page.
    - `can_fix` boolean, required: Whether THIS caller may add the OAuth app (the same answer as `can_configure_oauth_app`). False means point them at an admin, not at the connector page.
  - `oauth_app` object, nullable: Whether signing in with OAuth needs an app this organization has not added, and which other ways in exist. Null means unknown (the lookup failed) — never "not needed". Detail only, from the same single read of the organization's app as `connect_blocked`.
    - `needed_for_oauth` boolean, required: True when OAuth sign-in on this connector needs an OAuth app this organization has NOT added. False when no app is needed (`byoa` false) or the organization already added its own: `byoa` stays true after that, so it cannot say this.
    - `app_free_methods` string[], required: The auth formats this connector offers that connect without the app. Non-empty with `needed_for_oauth: true` is the mixed case: connectable by these now, and OAuth would first need an admin to add the app. Empty with `needed_for_oauth: true` is `connect_blocked`.

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not found
- `429`: Rate limited

---

[API](https://skmtc.dev/elaichi/apis/elaichi-api.md) · [All operations](https://skmtc.dev/elaichi/apis/elaichi-api/llms.txt) · [OpenAPI document](https://skmtc.dev/elaichi/apis/elaichi-api/revisions/b22cfb7b6d15?raw)