Custom MCP Server APIs
Version: aju17f20mq
Use the reference below for request and response fields and operation-specific requirements.
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.
Authentication
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.
Scoping
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.
Credentials
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.
Servers
Register, read, update, and delete custom MCP servers.
- Register a custom MCP server
- Get a custom MCP server
- List custom MCP servers
- Update a custom MCP server
- Delete a custom MCP server
Diagnostics
Test a registered server’s connection and tool discovery.
Server 1
Travila API
X-API-Key
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.
Authentication credentials
- API Key: apiKeyAuth
- API Key: onBehalfOf
- HTTP: bearerAuth
| Setting | Value |
|---|---|
| Security scheme type | apiKey |
| header parameter name | X-API-Key |
| Setting | Value |
|---|---|
| Security scheme type | apiKey |
| header parameter name | X-On-Behalf-Of |
| Setting | Value |
|---|---|
| Security scheme type | http |
| Scheme | bearer |
Operations
- Register a custom MCP server —
POST /api/v1/mcp-servers/create - Get a custom MCP server —
POST /api/v1/mcp-servers/get - List custom MCP servers —
POST /api/v1/mcp-servers/list - Update a custom MCP server —
POST /api/v1/mcp-servers/update - Delete a custom MCP server —
POST /api/v1/mcp-servers/delete - Test a custom MCP server connection —
POST /api/v1/mcp-servers/test-connection
Document ID: DOC-API-mcp-servers-overview. Section identities and revisions.
| Section | Stable reference |
|---|---|
| Overview | DOC-API-mcp-servers-overview#overview |
| Authentication | DOC-API-mcp-servers-overview#authentication |
| Scoping | DOC-API-mcp-servers-overview#scoping |
| Credentials | DOC-API-mcp-servers-overview#credentials |
| JSON conventions | DOC-API-mcp-servers-overview#json-conventions |
| Servers | DOC-API-mcp-servers-overview#reference-group-1 |
| Diagnostics | DOC-API-mcp-servers-overview#reference-group-2 |
| Server 1 | DOC-API-mcp-servers-overview#reference-server-1 |
| X-API-Key | DOC-API-mcp-servers-overview#authentication-apiKeyAuth |