Skip to Content

Publishing MCP Servers

Developers can submit MCP servers to the MCP Market by publishing a JSON snippet. The platform discovers metadata and tools, then sends the submission to admin review.

Public Market Submission

Use the MCP publish page in the product, or call the publish API directly:

POST /api/v1/mcp/publish-snippet Content-Type: application/json Authorization: Bearer <Privy JWT>

The request body contains display metadata and exactly one mcpServers entry:

{ "name": "OKX CEX Market Data", "slug": "okx-cex-market-dev", "description": "Read-only OKX market data tools for AI Chat.", "category": "market-data", "icon_url": "https://www.okx.com/favicon.ico", "mcp_server": { "mcpServers": { "okx-cex-market-dev": { "command": "npx", "args": ["-y", "@okx_ai/okx-trade-mcp", "--modules", "market"] } } } }

Submissions enter pending status until an admin approves them.

Personal Install

Personal installs are for testing or private use. They do not publish a server to the public market:

POST /api/v1/mcp/personal-install Content-Type: application/json Authorization: Bearer <Privy JWT>

Use personal install before submitting a public listing when you need to validate discovery, tool names, and runtime behavior.

Admin Review

Admins can review submitted servers in MCP Manager. A reviewer can:

  • approve the server
  • reject the server
  • request more information
  • suspend or unsuspend an existing listing
  • inspect discovered tools and runtime configuration

Naming Test Listings

When testing multiple listing paths, use different slugs, such as:

  • okx-cex-market-quickadd
  • okx-cex-market-seed
  • okx-cex-market-dev

After testing, suspend or delete duplicate listings and keep the intended production slug.

Review Checklist

Before submitting:

  • keep tool descriptions concise
  • avoid hardcoded secrets
  • prefer read-only modules for public market listings
  • return bounded, structured responses
  • document required user configuration
  • test the server locally before submission