Binance Square Post MCP
Menu

Docs

Connect Binance Square Post MCP

Add the fixed Server URL in clients that support remote MCP, finish OAuth, then publish to Binance Square safely.

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).
  3. Keys are stored with AES-256-GCM; the UI only shows a fingerprint.

Subscribe Open dashboard

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