Connectors

Register a connector

Fetches the source, parses it, dispatches to the plugin that owns it, and syncs the tool catalog — one call. Passing a presetId from the catalog resolves the source for you. GraphQL catalog registration preserves credential headers; an explicit API-key method on a custom GraphQL source uses Authorization: Bearer. An MCP endpoint is asked how it authenticates, so a server that wants OAuth gets an OAuth connector; authMethods overrides what it answers.

post/v1/connectors

Request

  • Base URL: https://api.spacefast.com
  • URL: https://api.spacefast.com/v1/connectors
  • Auth: one of:
    • HTTP bearer
    • OAuth 2 (authorization code, authorization URL https://api.spacefast.com/v1/auth/oauth2/authorize, token URL https://api.spacefast.com/v1/auth/oauth2/token; client credentials, token URL https://api.spacefast.com/v1/auth/oauth2/token, scopes: connectors:write)

Query parameters

teamstring

Team id or slug to act for. Required only when the credential could act for more than one team.

Request body

slugstring required

Team-unique slug. Also the namespace its tools hang off, so keep it short.

titlestring required

Display name. Defaults to whatever the source calls itself.

descriptionstring

What this connector reaches, in one line. Agent-visible.

presetIdstring

Catalog row supplying the source and authentication recipe. An explicit source overrides its endpoint and must use the same kind.

specOverridesobject[]

RFC 6902 JSON Patch operations applied to the fetched spec before tools are built.

Response

Response for status 201

$schemastring uri

Canonical JSON Schema URL for this response body. The server also sends it in the Link: rel="describedby" response header.

Changes

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