List a connection’s versions

GET

/api/mcp-connections/{connectionId}/versions

• Production

Returns the connection’s published versions, newest first, with who published each. Requires the mcp:read scope.

Authorizations

• bearerAuth

Parameters

Path Parameters

connectionId

required

string format: uuid

The unique identifier of the MCP connection.

Responses

200

The version history.

object

versions

required

Array<object>

One entry of a connection’s version history.

object

id

required

string format: uuid

versionNumber

required

integer

status

required

string

Allowed values: published superseded rejected

authorUserId

Who published it: a user id, or api-key:<id> when an API key did.

string | null

Example

api-key:c1a2c3d4-5678-4abc-8ef0-1234567890ab

authorNote

string | null

sourceType

What produced the version, for example manual or restore.

string

publishedAt

string | null format: date-time

supersededAt

string | null format: date-time

createdAt

required

string format: date-time

403

The API key does not carry the mcp:read scope.

Standard error response returned by all endpoints on failure.

object

error

required

A human-readable error message describing what went wrong.

string

Example

Conversation not found

code

A machine-readable reason on some refusals, for example ‘key_lock’ when an API key’s brand or workspace restriction does not cover the action.

string

Example

key_lock

missing_scopes

On a 403 for an API key without a scope the endpoint requires: the scopes the key lacks.

Array<string>

Example

[
  "mcp:write"
]

entryId

On a 409 with code duplicate_question or duplicate_rule_text: the knowledge base entry or policy that already holds the question or rule text.

string format: uuid

Example

11223344-5566-4788-99aa-bbccddeeff00

connectionId

On a 422 about one MCP connection a request names, from an assignment or an agent create or update (a connection that does not exist, one listed twice, or one that does not declare a tool named): the connection, as the request named it.

string

undeclaredTools

On the same 422: the tool names the connection does not declare.

Array<string>

Example

[
  "get_orders"
]

declaredTools

On the same 422: the tools the connection declares.

Array<string>

Example

[
  "get_order",
  "search_orders"
]

404

No such connection, or it is outside the API key’s brand or workspace restriction. A connection the key cannot reach is not disclosed.

Standard error response returned by all endpoints on failure.

object

error

required

A human-readable error message describing what went wrong.

string

Example

Conversation not found

code

A machine-readable reason on some refusals, for example ‘key_lock’ when an API key’s brand or workspace restriction does not cover the action.

string

Example

key_lock

missing_scopes

On a 403 for an API key without a scope the endpoint requires: the scopes the key lacks.

Array<string>

Example

[
  "mcp:write"
]

entryId

On a 409 with code duplicate_question or duplicate_rule_text: the knowledge base entry or policy that already holds the question or rule text.

string format: uuid

Example

11223344-5566-4788-99aa-bbccddeeff00

connectionId

On a 422 about one MCP connection a request names, from an assignment or an agent create or update (a connection that does not exist, one listed twice, or one that does not declare a tool named): the connection, as the request named it.

string

undeclaredTools

On the same 422: the tool names the connection does not declare.

Array<string>

Example

[
  "get_orders"
]

declaredTools

On the same 422: the tools the connection declares.

Array<string>

Example

[
  "get_order",
  "search_orders"
]