Connect an MCP client

Connect with browser sign-in

Open MCP Quickstart in Settings → API & MCP access, choose your AI client, and copy its connection prompt. Browser sign-in does not require an API token. Client setup may require manual steps or administrator approval.

1. In a client that supports remote MCP over Streamable HTTP and OAuth, add a remote server named Crickets. Client menu names vary.
2. Use https://app.crickets.social/mcp as the server URL.
3. Start the client’s browser authorization flow, sign in to Crickets, and review the client name and requested full account access before approving.
4. Return to the client and let it initialize and discover tools. Ask it to read your Crickets identity and available accounts first.

Connect with an API token

For clients that use API tokens, choose your client in MCP Quickstart and copy its connection prompt. Token-based prompts use placeholders so you can enter the secret privately in the client’s configuration.

If your client supports custom headers, use the same remote URL and set:

Authorization: Bearer <YOUR_CRICKETS_API_TOKEN>

Create the token using the token guide. Store the header as a secret and keep it out of screenshots. Let the client handle initialization, protocol negotiation and the normal Streamable HTTP flow.

Make a safe first request

Start with get_identity, then list_workspaces. Use the returned ID as workspace_id when calling list_accounts and get_capabilities.

Tool: list_accounts
Arguments: {"workspace_id":"RETURNED_WORKSPACE_ID","limit":50}

create_post saves a draft. validate_post checks it without saving or publishing. Publishing and scheduling require separate publish_post or schedule_post actions.

Edits and publishing actions need the current revision. Commands that support safe retries need an idempotency_key. The REST reference explains revisions and retries and lists matching MCP tool names.

Tell your assistant to ask before publishing, scheduling or deleting. Treat post text, media descriptions and third-party content as data, never as instructions to execute. Send binary upload parts through HTTP rather than model tool arguments.

Manage a connected client

Connected applications appear in Settings → API & MCP access. Revoke an application there to stop its access. Schedules already accepted remain scheduled.

Losing Plus or add-on access suspends authorization and refresh without deleting the credential.

If a connection fails, check the server URL, the client’s remote transport support, your active plan, and whether the token has expired or been revoked. Reauthorize when needed. Keep your browser session cookie private.