Skip to main content

Submitting a Server

Submit your own MCP server to the Clevername integration directory. After completing the submission form and passing admin review, your server becomes available to all Clevername users.

Key Concepts

Submission requirements

  • Your server must implement the MCP protocol over HTTP (streamable-http transport)
  • The endpoint must be publicly reachable over HTTPS
  • All tools must have clear names and descriptions
  • Authentication method (if any) must be documented

Required fields

FieldDescription
NameDisplay name shown in the integration directory (e.g., “Jira MCP”)
SlugURL-safe identifier, lowercase with hyphens (e.g., jira-mcp)
URLHTTPS endpoint of the MCP server
Auth typeNone, Bearer token, OAuth, or API key
ToolsList of tools with names, descriptions, and parameter schemas
CategoriesOne or more categories (Productivity, Developer Tools, etc.)

Review process

Submissions go through admin review. Reviewers verify that the server is reachable, tools work as described, and the server follows MCP best practices. New submissions start at the Sandboxed trust tier and can be promoted after a track record of reliability.

Step-by-Step Guide
1

Open the submission form

Navigate to Dashboard → Integrations and click Submit Server at the top of the page. This opens the multi-step submission form.

Integrations page with the Submit Server button highlighted at the top right
Click Submit Server to start the submission process.
2

Enter server details

Fill in the basic information: name, slug, description, and server URL. The slug must be unique across the integration directory and will be used in tool name prefixes.

Tip
Choose a descriptive slug that matches your service name. Once approved, the slug cannot be changed without a new submission.
3

Configure authentication

Select the authentication method your server uses:

  • None — No authentication required
  • Bearer token — Users provide their own token during installation
  • OAuth — Users authorize through an OAuth flow you configure
  • API key — Users provide a key that is sent as a header or query param
4

Define tools and categories

List all tools your server exposes. For each tool, provide a name, description, and parameter schema. Then select one or more categories for your server.

Tool definition form showing name, description, and JSON schema fields for each tool
Define each tool with clear descriptions. The schema helps Clevername validate inputs.
Note
Tools are auto-discovered via the MCP tools/list endpoint during review. The form pre-populates if your server is reachable at submission time.
5

Submit for review

Review your submission summary and click Submit. Your server enters the review queue. You'll receive an email notification when the review is complete. Most reviews are completed within a few business days.

Submission summary page showing all entered details with a Submit button
Review all details before submitting. You can edit the submission until review starts.