Skip to main content

Custom Packs Management API

Build custom tool collections by combining MCP servers into reusable packs.

Overview

Custom Packs let you:
  • Combine servers - Group multiple MCP servers together
  • Share collections - Use the same pack across projects
  • Organize tools - Logical grouping for team workflows
  • Enforce limits - Control max packs per plan
  • Version control - Track and update pack configurations

What Are Packs?

A Pack is a curated collection of MCP servers that work together:

Plan Limits


POST /custom-packs/mcp-servers

Create a custom MCP server definition

Authentication

Required

Request Body

Request Example

Response Format

Error Cases

Plan limit exceeded (400):

GET /custom-packs/mcp-servers

List all custom servers for user

Authentication

Required

Request Example

Response Format


POST /custom-packs/packs

Create a custom pack

Authentication

Required

Request Body

Request Example

Response Format


GET /custom-packs/packs

List all custom packs

Authentication

Required

Query Parameters

Request Example

Response Format


GET /custom-packs/packs/

Get specific pack details

Authentication

Required

Path Parameters

Request Example

Response Format


PATCH /custom-packs/packs/

Update pack details

Authentication

Required

Request Body

Request Example

Response Format


DELETE /custom-packs/packs/

Delete a pack

Authentication

Required

Request Example

Response Format


POST /custom-packs/packs//servers

Add server to pack

Authentication

Required

Request Body

Request Example

Response Format


DELETE /custom-packs/packs//servers/

Remove server from pack

Authentication

Required

Path Parameters

Request Example

Response Format


PUT /custom-packs/packs//servers

Replace all servers in pack

Authentication

Required

Request Body

Request Example

Response Format


GET /custom-packs/packs//install

Get install command for pack

Authentication

Required

Request Example

Response Format


Use Cases

Use Case 1: Team Workflow Pack

Goal: Create a pack for frontend development team

Use Case 2: Multi-Service API Pack

Goal: Manage multiple internal services

Best Practices

1. Logical Grouping


2. Naming Convention


3. Version Server Configurations


4. Document Pack Usage


Management Workflow

Create and Configure


Update and Migrate


Archive and Cleanup


Error Handling

Plan Limit Exceeded


Server Not Found


Integration with Tools

Once pack is enabled, use tools:

See Also