> ## Documentation Index > Fetch the complete documentation index at: https://portkey-docs-add-third-party-integration-issues-fixes.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Create MCP Integration > Create a new MCP Integration. Requires either organisation_id (with admin API key) or workspace_id in body. ## OpenAPI ````yaml post /mcp-integrations openapi: 3.0.0 info: title: Portkey API description: >- The Portkey REST API. Please see https://portkey.ai/docs/api-reference for more details. version: 2.0.0 termsOfService: https://portkey.ai/terms contact: name: Portkey Developer Forum url: https://portkey.wiki/community license: name: MIT url: https://github.com/Portkey-AI/portkey-openapi/blob/master/LICENSE servers: - url: https://api.portkey.ai/v1 description: Portkey API Public Endpoint security: - Portkey-Key: [] tags: - name: Assistants description: Build Assistants that can call models and use tools. - name: Audio description: Turn audio into text or text into audio. - name: Chat description: >- Given a list of messages comprising a conversation, the model will return a response. - name: Realtime description: WebSocket proxy for provider Realtime APIs - name: Collections description: Create, List, Retrieve, Update, and Delete collections of prompts. - name: Labels description: Create, List, Retrieve, Update, and Delete labels. - name: Prompt Collections description: Create, List, Retrieve, Update, and Delete prompt collections. - name: PromptPartials description: Create, List, Retrieve, Update, and Delete prompt partials. - name: Prompts description: >- Given a prompt template ID and variables, will run the saved prompt template and return a response. - name: Guardrails description: Create, List, Retrieve, Update, and Delete prompt Guardrails. - name: Completions description: >- Given a prompt, the model will return one or more predicted completions, and can also return the probabilities of alternative tokens at each position. - name: Embeddings description: >- Get a vector representation of a given input that can be easily consumed by machine learning models and algorithms. - name: Rerank description: >- Rerank a list of documents based on their relevance to a query. Supported providers include Cohere, Voyage, Jina, Pinecone, Bedrock, and Azure AI. - name: Fine-tuning description: Manage fine-tuning jobs to tailor a model to your specific training data. - name: Batch description: Create large batches of API requests to run asynchronously. - name: Files description: >- Files are used to upload documents that can be used with features like Assistants and Fine-tuning. - name: Images description: Given a prompt and/or an input image, the model will generate a new image. - name: Models description: List and describe the various models available in the API. - name: Moderations description: >- Given a input text, outputs if the model classifies it as potentially harmful. - name: Configs description: Create, List, Retrieve, and Update your Portkey Configs. - name: Feedback description: Send and Update any feedback. - name: Logs description: Custom Logger to add external logs to Portkey. - name: Integrations description: Create, List, Retrieve, Update, and Delete your Portkey Integrations. - name: Integrations > Workspaces description: Manage workspace access for your Portkey Integrations. - name: Integrations > Models description: Manage model access for your Portkey Integrations. - name: Providers description: Create, List, Retrieve, Update, and Delete your Portkey Providers. - name: Virtual-keys description: Create, List, Retrieve, Update, and Delete your Portkey Virtual keys. - name: Users description: Create and manage users. - name: User-invites description: Create and manage user invites. - name: Workspaces description: Create and manage workspaces. - name: Workspaces > Members description: Create and manage workspace members. - name: MCP Integrations description: Create, List, Retrieve, Update, and Delete MCP Integrations. - name: MCP Integrations > Workspaces description: Manage workspace access for MCP Integrations. - name: MCP Integrations > Capabilities description: List and manage capabilities for MCP Integrations. - name: MCP Integrations > Metadata description: Get MCP Integration metadata and sync info. - name: MCP Servers description: >- Create, List, Retrieve, Update, and Delete MCP Servers (workspace instances of MCP Integrations). - name: MCP Servers > Capabilities description: List and manage capabilities for MCP Servers. - name: MCP Servers > User Access description: List and manage user access for MCP Servers. - name: MCP Servers > Connections description: List and manage user connections for MCP Servers. - name: Api-Keys description: Create, List, Retrieve, Update, and Delete your Portkey API keys. - name: Logs Export description: Exports logs service. - name: Audit Logs description: Get audit logs for your Portkey account. - name: Analytics description: >- Get analytics over different data points like requests, costs, tokens, etc. - name: Analytics > Graphs description: Get data points for graphical representation. - name: Analytics > Summary description: Get overall summary for the selected time bucket. - name: Analytics > Groups description: Get grouped metrics for the selected time bucket. - name: Usage Limits Policies description: Manage usage limits policies to control total usage over time - name: Rate Limits Policies description: Manage rate limits policies to control request or token rates - name: Model Pricing description: Model pricing configurations for 2300+ LLMs across 40+ providers - name: Secret-References description: >- Create, List, Retrieve, Update, and Delete secret references to external secret managers. paths: /mcp-integrations: servers: - url: https://api.portkey.ai/v1 description: Portkey API Public Endpoint - url: SELF_HOSTED_CONTROL_PLANE_URL description: Self-Hosted Control Plane URL post: tags: - MCP Integrations summary: Create MCP Integration description: >- Create a new MCP Integration. Requires either organisation_id (with admin API key) or workspace_id in body. operationId: McpIntegrations_create requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/CreateMcpIntegration' examples: default: summary: Minimal (required fields only) value: name: My MCP Server url: https://mcp.example.com/mcp auth_type: none transport: http responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/McpIntegrationCreateResponse' components: schemas: CreateMcpIntegration: type: object description: >- Only include optional fields (slug, description, configurations) when you have values for them. The example and code samples show required fields plus workspace_id and organisation_id when scoping. required: - name - url - auth_type - transport properties: organisation_id: type: string format: uuid description: >- Organisation ID (optional; required when using org admin API key without workspace_id) workspace_id: type: string format: uuid description: Workspace ID (optional; to create at workspace level) slug: type: string pattern: ^[a-zA-Z0-9_-]+$ description: Optional slug; must be unique within organisation name: type: string description: Display name of the MCP integration description: type: string nullable: true configurations: type: object description: Auth/config key-value pairs (e.g. headers, client credentials) properties: custom_headers: type: object additionalProperties: true description: Custom headers to send to the MCP server. example: Authorization: Bearer some-token x-foo: bar passthrough_header: type: object additionalProperties: true description: >- Headers to pass through from the incoming request to the MCP server. example: x-user-id: type: string example: abc123 x-request-id: type: string example: req-0001 additionalProperties: true url: type: string format: uri description: MCP server URL auth_type: type: string enum: - oauth_auto - headers - none transport: type: string enum: - http - sse secret_mappings: type: array items: $ref: '#/components/schemas/SecretMapping' description: >- Dynamically resolve secrets from secret references at runtime. Valid target_field values are "configurations." (e.g. "configurations.oauth_metadata"). Each target_field must be unique. McpIntegrationCreateResponse: type: object properties: id: type: string format: uuid slug: type: string SecretMapping: type: object required: - target_field - secret_reference_id properties: target_field: type: string description: > The field on the entity to populate from the secret reference. Must be unique within the array. - **Integrations**: `key` or `configurations.` (e.g. `configurations.aws_secret_access_key`) - **Virtual Keys**: `key` or `model_config.` (e.g. `model_config.awsSecretAccessKey`) - **MCP Integrations**: `configurations.` (e.g. `configurations.oauth_metadata`) example: key secret_reference_id: type: string description: >- UUID or slug of the secret reference. Must belong to the same organisation and be accessible by the workspace. example: my-aws-secret secret_key: type: string nullable: true description: >- Override the secret_key defined on the secret reference. Use to pick a specific key from a multi-value secret. value_format: type: string nullable: true enum: - json - string description: > Format of the secret value. - `string`: The secret value is treated as a plain string. - `json`: The secret value is parsed as JSON before being applied to the target field. Use this when the target field expects a structured object (e.g. `configurations.oauth_metadata`). example: json securitySchemes: Portkey-Key: type: apiKey in: header name: x-portkey-api-key ````