Custom MCP Server APIs
Register custom MCP servers, update their configuration and test discovery. Configuration and discovery do not grant permission to perform a tool action or imply automatic insertion into every agent.
Use an authorized backend sk_… key in X-API-Key; these configuration operations do not need an end-user identity. A console JWT belongs to the separate console surface. See Authentication.
Tenant context comes from the authenticated request. Client-supplied X-Tenant-Id, X-User-Id or X-Project-Id are not an authorization mechanism. The current public integration uses the default project. Do not rely on project headers for separate project, test/live or customer isolation on this API.
Server endpoints, query parameters and secret bindings are sensitive connection configuration. Use approved network destinations and the secret store; never place credentials in shared examples.
Related guide: Custom MCP servers
JSON conventions
Requests accept snake_case or camelCase field names; responses use camelCase. Ordinary default-valued scalars and empty repeated fields can be omitted. Explicitly present optional scalars, map values and well-known JSON types follow their own presence rules: an explicit false, 0 or empty value is not universally equivalent to absence. Decode each field according to its schema. 64-bit integers use JSON strings; preserve their precision. Unknown request fields are generally discarded before validation, so a typo can silently change behavior. This is not a guarantee that arbitrary fields or future client contracts are supported. See API conventions.
Authentication
- API Key: apiKeyAuth
Authorized tenant backend secret key (sk_…). No end-user identity is needed for these tenant/project configuration operations. Keep the key out of client apps; authorization and provisioning still apply.
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-API-Key |
📄️ Connected accounts overview
Connect end-user accounts through the optional hosted Pipedream integration. This API requires Pipedream Connect to be enabled for your account.
📄️ Custom MCP servers overview
Register custom MCP servers, update their configuration and test discovery. Configuration and discovery do not grant permission to perform a tool action or imply automatic insertion into every agent.
📄️ Connected account selection
overview}
📄️ MCP server selection
overview}
🗃️ Endpoints
22 items
🗃️ Models
9 items
Document ID: DOC-IN-tools-connections-servers-api-overview. Section identities and revisions.
| Section | Stable reference |
|---|---|
| Overview | DOC-IN-tools-connections-servers-api-overview#overview |
| JSON conventions | DOC-IN-tools-connections-servers-api-overview#json-conventions |
| Authentication | DOC-IN-tools-connections-servers-api-overview#authentication |
| Scoping | DOC-IN-tools-connections-servers-api-overview#scoping |
| Credentials | DOC-IN-tools-connections-servers-api-overview#credentials |