Skip to main content
GET
Get registry connector details and configuration schema

Authorizations

Authorization
string
header
required

OAuth 2.0 / OIDC bearer token.

Tenant-Name
string
header
required

The tenant the request operates within.

Path Parameters

connectorId
string
required

Registry connector identifier (e.g. @dedalus/coding-expert).

Response

The registry connector.

A discoverable, pre-built connector offered by the platform registry. Only id, type, name, title, description, and configSchema are populated by the server today. version, provider, capabilities, tags, and documentationUrl are declared for forward compatibility but are not yet returned.

id
string
required

Stable, namespaced registry identifier; use as a registry connector's name.

Example:

"@dedalus/coding-expert"

type
enum<string>
required

The connector kind this entry provisions when attached to an agent.

Available options:
registry,
mcp,
agent,
a2a,
schema
name
string
required

Programmatic name (MCP convention).

Example:

"coding-expert"

title
string

Human-readable display name (MCP convention).

Example:

"ICD-10 Coding Expert"

description
string

Description for list and detail views. May contain CommonMark.

version
string

Latest published version (SemVer recommended).

Example:

"1.4.2"

icons
object[]

Display icons (MCP convention).

provider
string

Name of the publishing organisation.

Example:

"Dedalus"

websiteUrl
string<uri>

Connector homepage (MCP convention).

documentationUrl
string<uri>

Documentation URL for the connector.

capabilities
object

What the connector can do once attached.

tags
string[]

Keywords for search and filtering.

configSchema
object

JSON Schema (draft 2020-12) describing the connector's accepted config.