An MCP client registers itself with POST /oauth/register, sends the person through the sign-in and approval page, and exchanges the code with PKCE at POST /oauth/token. The person chooses the workspace. Tokens refresh, and the person can see and disconnect every connected app in settings.
Register the client. Discovery documents are served at the standard well-known addresses.
Send the person to the authorization page. They pick a workspace and approve.
Exchange the code, with PKCE, for an access token and a refresh token.
Call /v1/mcp/oauth with the token. Revocation is supported at POST /oauth/revoke.
The connection acts with the person's role in the workspace they chose. Disconnecting an app in settings ends it at once.
7-day trial for $1. Connect your accounts and schedule a week of posts in one sitting.
Start a trialCount characters the way each network does, split threads and preview posts. No account needed.
Open the toolsPost to every network from your own code or assistant with one key, signed webhooks and idempotent requests.
See the APIDynamic client registration, protected resource and authorization server metadata, authorization code with PKCE, refresh tokens and token revocation.
Plan the week in one sitting, keep your team in the loop, and let 1Post publish on time while you get on with the rest of your day.