OrbitPage AI and the OpenAI MCP integration

The same safe page workflow is available through three different entry points.

Use the dashboard AI assistant when you are already editing in OrbitPage. Use the personal-token Automation REST API for scripts, n8n, CI or a trusted backend. Use the remote MCP server when you want a compatible OpenAI client to read, preview, apply, publish or restore one connected workspace.

The public-site support chatbot is separate. It cannot edit a workspace and does not share the MCP OAuth grant or the personal Automation API token.

• Dashboard AI: Firebase session, App Check and an explicit preview confirmation.
• Automation REST API: a revocable personal token bound to one workspace and selected scopes.
• Remote MCP: OAuth access bound to one selected workspace and tool-specific scopes.

A request becomes a proposal before it becomes page content.

OrbitPage sends bounded page context to the configured model and asks for structured operations. The server validates the result against the page schema, role, plan, moderation and current revision before it creates a short-lived preview.

Nothing changes when a preview is rejected or left unused. Applying an approved preview rechecks the revision and permissions, creates normal version history and can publish the exact result. If someone edited the page in the meantime, OrbitPage returns a conflict instead of overwriting the newer work.

The OpenAI MCP connection is intentionally narrower than the complete API.

The production Streamable HTTP endpoint is https://orbitpage.com/mcp. Its tools identify the connected workspace, read page content and capabilities, prepare and apply reviewed changes, publish an exact revision, inspect publication status, list retained versions and restore a selected version into a private draft.

It edits only the profile, social, block and theme fields returned by the capability tool for the current plan and role. It can read subpages and settings as context, but media uploads, subpage and menu management, analytics, collaborators, newsletters, Shop, billing, domains and internal operator actions remain in the OrbitPage dashboard.

Create a custom OpenAI MCP connection to the live OrbitPage endpoint.

In ChatGPT on the web, enable Developer Mode for your account, then add a custom MCP connection from Settings > Apps > Create or the equivalent workspace-admin screen. OpenAI currently places custom MCP connections under Apps; this does not make OrbitPage a public directory app. Enter https://orbitpage.com/mcp as the remote MCP endpoint, select OAuth, scan the available tools and create the connection. OrbitPage supports dynamic client registration, so you do not enter a client secret.

Start sign-in, authenticate with your normal OrbitPage account and choose one eligible workspace on the consent screen. Review every requested permission before approving. OpenAI currently provides full MCP, including write and modify actions, to Business and Enterprise/Edu workspaces in beta; Pro developer mode is limited to read and fetch actions. Availability, menus and administrator controls can change, so verify the current OpenAI guide before setup.

• Use the production HTTPS endpoint, not a Preview deployment or local URL.
• Do not paste a Firebase password, personal API token or OpenAI API key into the connector settings.
• Confirm or revoke the grant later under OrbitPage Dashboard > Account > Connected apps.

The OpenAI client receives a revocable grant, not your OrbitPage credentials.

The client discovers OrbitPage's protected-resource and authorization-server metadata, registers as a public OAuth client and uses authorization code with PKCE S256. The browser login remains protected by Firebase Authentication and App Check. The consent step binds the resulting grant to the selected user, tenant, page and scopes.

Access tokens are short-lived and refresh tokens rotate. OrbitPage stores credential hashes, verifies the exact MCP resource and scopes on every tool call, and rechecks current workspace membership. Changing the active dashboard workspace does not retarget an existing grant; disconnect the integration and connect again when you need a different workspace.

• workspace:read reads workspace identity, page content, theme and capabilities.
• publication:read reads publication state and the public URL.
• ai:write prepares and applies reviewed AI page changes.
• publication:write publishes an approved page revision.
• backup:read lists retained published versions; backup:write restores one into a private draft.

Keep proposal, private draft and public page as separate states.

Ask the connected client to read the affected section and preview a specific change. Review the returned summary, then approve only that proposal. A normal apply publishes the approved revision and reports success only after managed publication is complete.

If you explicitly want a private draft, ask the client to apply without publishing. Review the saved revision separately, then approve publication of that exact revision. Restoring history also stays private until a separate publish instruction is confirmed.

• Safe prompt: Preview a clearer profile description, keep my links and theme unchanged, and do not apply it yet.
• Status prompt: Show my connected workspace and tell me whether it has unpublished changes. Do not modify anything.
• Publish prompt: Show the current private revision, then publish that exact revision only after I confirm.

This is a custom MCP integration, not a public OrbitPage app.

OrbitPage currently supports a manual connection to its remote MCP server at https://orbitpage.com/mcp. The product site does not present this connection as an OrbitPage app in the public ChatGPT app directory.

OpenAI controls eligibility for custom MCP connections by plan, workspace role and administrator settings. The connection runs on ChatGPT web and may expose fewer actions when the selected OpenAI plan supports only read and fetch tools.

Diagnose discovery, login, scope and publication as different layers.

An OAuth configuration error usually means the OpenAI client could not read a well-known metadata document as public JSON. A successful login followed by a reconnect request usually means the grant lacks a tool scope. A tool-scan failure should be diagnosed separately from OAuth and workspace access.

After a write, ask for publication status and compare the draft and published revision before judging the public page. If the connection targets the wrong workspace, revoke it from Dashboard Account and reconnect; never try to supply tenant or page IDs in a prompt.

Grant only the workspace and capabilities you intend to use.

The connected OpenAI service receives only the data returned by the tools you authorize and processes it under its own terms. OrbitPage does not send your Firebase password or personal API tokens to the MCP client, and tool responses should never contain credentials or unrelated customer data.

You can revoke the entire connection from Dashboard Account. Use a dedicated, fictional workspace for demonstrations and review material, and verify the current OrbitPage privacy policy before connecting production content.