Skip to documentation

MCP setup

Connect an approved host and verify profile and project reads.

Connection prerequisites

  • Use an MCP host that supports browser OAuth with S256 PKCE. Follow the host’s client registration instructions if it asks for a client ID.
  • Use the MCP server URL provided for your Postede environment. Follow the host setup instructions when they appear on Connect to Postede.

Stop if the host’s registration or matching resource is unavailable. Keep each host and environment’s client/grant separate.

Connect and verify

  1. Add the exact registered MCP resource in the host.
  2. The user completes the host’s browser OAuth flow and chooses which organizations, projects, and actions to allow. If the host requests renewal, it can renew the approved access automatically. You can disconnect it anytime in Connected Apps.
  3. Discover the host’s available tools, then call get_profile and list_projects with empty arguments.
Read-only verification prompt
Show my Postede profile and list my projects. Do not change content, settings or delivery state.

Confirm the intended account/environment and successful reads. An empty project list is valid. Use the tools discovered in the connected host for this environment.

Connection recovery

  • Expired access: let the host refresh. Reconnect through its OAuth flow if refresh fails or consent is revoked.
  • Missing tool: inspect the discovered catalog and operator-enabled capabilities.
  • Permission denied: check scope, project role and consent. After a user changes permissions, reconnect for an updated grant.
  • Rate limit: follow the returned retry interval; do not loop or repeatedly reconnect.

Disconnect

Revoke the grant in Connected apps in the same environment, then remove the connection from the host. Never request passwords, cookies or tokens in conversation.

V-2026-11-19_20.25.44