> ## Documentation Index
> Fetch the complete documentation index at: https://docs.profy.cn/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish a connector

> Publish an API-key remote MCP through the existing plugin flow and declare how users get a key

A connector reuses the plugin draft, review, and release flow. There is no separate product or review API. The first release supports remote HTTPS only, over HTTP or SSE, with API key authentication.

## Create

Open Connectors in creator works and add one. The existing plugin editor asks for the shared fields plus:

* One `mcpServers` JSON document. Write `{{param}}` where the user must fill a value
* What the key is for
* An external HTTPS page where the user gets a key, and the link label

A query credential is `?key={{key}}`. A header is `"Authorization": "Bearer {{token}}"` or `"X-API-Key": "{{apiKey}}"`. A placeholder must occupy a whole query value, path segment, or header value. The host cannot be a variable. Users fill only those values, and the platform substitutes them back into the JSON.

## Test and publish

The key you type for Test connection exists only for that request. It is not written to the draft, the pending submission, or the release, and it does not create a personal installation. The test discovers tools and prompts only.

A draft may omit business fields, but it cannot store a real key. Submit requires the full declaration and the same publish gate as a plugin. While a new version is in review, the market keeps serving the last approved release. A connector with no approved release cannot be installed.

Stdio MCP stays on the existing plugin import path and is not part of this public catalog. OAuth is out of scope.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.