Connections Custom Connectors API

The Custom Connectors API from Connections — 3 operation(s) for custom connectors.

GitHub OpenAPI

Operations 4

GET /v1/custom-connectors List this workspace's custom connectors (remote MCP servers a member added by… #
POST /v1/custom-connectors Add a custom connector: a remote MCP server by its link. #
POST /v1/custom-connectors/{id}/sign-in Sign a custom connector in again (a token that expired, a server that changed… #
DELETE /v1/custom-connectors/{id} Remove a custom connector and its stored sign-in; its tools leave the AI's… #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/connections-icu:connections-icu-custom-connectors-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

connections-icu-custom-connectors-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Connections Icu Custom Connectors API
  version: 1.0.0
  description: 'Operations tagged Custom Connectors across 2 of this provider''s published API definitions: connections-icu-studio-openapi-original.json, connections-icu-studio-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://studio.connectionsapi.com
tags:
- name: Custom Connectors
paths:
  /v1/custom-connectors:
    get:
      summary: List this workspace's custom connectors (remote MCP servers a member added by…
      security:
      - aegisBearer: []
      - apiKey: []
      tags:
      - Custom Connectors
      operationId: getV1CustomConnectors
      x-operation-id-source: derived
    post:
      summary: 'Add a custom connector: a remote MCP server by its link.'
      security:
      - aegisBearer: []
      - apiKey: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - name
              - url
              properties:
                name:
                  type: string
                  description: REQUIRED. What the connector is called in this workspace (1-60 characters, unique per workspace).
                url:
                  type: string
                  description: REQUIRED. The remote MCP server's link. https only; no user or password in it; private and loopback hosts are refused.
                oauth_client_id:
                  type: string
                  description: 'For a server that does not register clients itself: the OAuth client id its owner gave you.'
                oauth_client_secret:
                  type: string
                  description: The OAuth client secret that goes with oauth_client_id, if the owner gave one. Never returned.
                listing:
                  type: string
                  description: The slug of the listed connector this was added from, when one started it.
                return_to:
                  type: string
                  description: Where the browser lands after the server's own sign-in. Honoured only for a first-party Connections https page.
      tags:
      - Custom Connectors
      operationId: postV1CustomConnectors
      x-operation-id-source: derived
    servers:
    - url: https://studio.connectionsapi.com
  /v1/custom-connectors/{id}/sign-in:
    post:
      summary: Sign a custom connector in again (a token that expired, a server that changed…
      security:
      - aegisBearer: []
      - apiKey: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties: {}
              description: No fields. The path id and your session are the entire input.
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      tags:
      - Custom Connectors
      operationId: postV1CustomConnectorsByIdSignIn
      x-operation-id-source: derived
    servers:
    - url: https://studio.connectionsapi.com
  /v1/custom-connectors/{id}:
    delete:
      summary: Remove a custom connector and its stored sign-in; its tools leave the AI's…
      security:
      - aegisBearer: []
      - apiKey: []
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      tags:
      - Custom Connectors
      operationId: deleteV1CustomConnectorsById
      x-operation-id-source: derived
    servers:
    - url: https://studio.connectionsapi.com
components:
  securitySchemes:
    aegisBearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: The AEGIS SSO access token (Cognito JWT from the shared sign-in) presented as a Bearer on every /v1 call.
    apiKey:
      type: http
      scheme: bearer
      bearerFormat: cnx_live_* | cnx_pub_*
      description: 'A key minted in the console, sent as a bearer token. `cnx_live_` carries cross-plane data scopes AND (when granted) Studio management scopes (apps:*, keys:*, projects:*, webhooks:*) that authorize the console-management operations below. `cnx_pub_` is the publishable, browser-safe tier (Stripe''s pk_ model): mint-time capped to :read scopes, requires a non-empty allowed-origins allowlist, refused on any non-GET/HEAD route, and rate-limited - safe to embed in client-side code.'
    oauthUserToken:
      type: http
      scheme: bearer
      description: EITHER (a) a Sign-in-with-Connections USER access token issued by accounts.connectionsapi.com to a registered OAuth app - the app acts on behalf of its signed-in user, rows are keyed by the token's own sub + client_id; OR (b) an app-bound publishable key (cnx_pub_, minted with an appId) presented on X-Connections-Api-Key ALONGSIDE the signed-in user's own plain AEGIS bearer on Authorization - the server derives (app_id, sub) from the two verified credentials. The publishable key alone authorizes nothing; both credentials are required. This second form is for a developer who wants the locker without standing up a full OAuth client - mint one publishable key bound to a registered app instead.
x-refined-from:
- connections-icu-studio-openapi-original.json
- connections-icu-studio-openapi.yml