Connect Binance Square Post MCP

1. Fixed MCP Server URL

Use this address when adding a Custom Connector or Remote MCP in Grok / Claude / ChatGPT. Keys never go in the URL.

2. Subscribe and bind a Key

1. Log in and complete plan activation (WeChat confirmation).
2. In the dashboard API Key tab, paste your Binance Square OpenAPI Key and save (one active key per tenant). How to get this API Key
3. Keys are stored with AES-256-GCM; the UI only shows a fingerprint.

Subscribe Open dashboard

How to get a Binance Square API Key

The key is issued inside Binance Square’s Creator Center (创作者学院), not from the general Binance OpenAPI console.

1. Open the Binance Square Creator Center and sign in.
2. In the left sidebar, open Creator Academy (创作者学院).
3. In the upper-right of that page, click View API (查看 API).
4. In the API management dialog, copy the API key (API 密钥).
5. Paste it into this product’s dashboard (or the OAuth consent form) and save.

Open Creator Center ↗ Open dashboard to paste the key

Never put the key in the MCP URL. Store it only in the dashboard or consent form; it is encrypted at rest.

3. Client OAuth

1. Paste the fixed Server URL above into the client.
2. The client opens the consent page; log in and approve (scope: square:publish).
3. After consent, tokens travel only in the Authorization header — never in links.

A legacy access-code path may still exist during migration; the default product path is account login + plan entitlement.

4. Publish and idempotency

Agents call publish_* tools; each publish needs a stable idempotency_key. The server never auto-retries /content/add. For read-only checks use preview_square_post.

FAQ Pricing