Connect OrbitPage through MCP without losing review control
Understand OrbitPage's OAuth-protected remote MCP tools, the preview-only WebMCP tools in compatible browsers and their boundaries.
Last reviewed 17 September 2026OrbitPage has two distinct MCP surfaces. The remote server connects a client to one selected hosted workspace through OAuth and exposes focused page actions. Browser WebMCP, when supported, works only inside the signed-in dashboard and can read or preview without applying a change. Neither surface is the wider personal-token Automation API.
Connect a compatible client to one workspace with OAuth.
The production Streamable HTTP endpoint is https://orbitpage.com/mcp. A compatible MCP client discovers OrbitPage's OAuth authorization flow, signs you in on OrbitPage and asks you to select and approve one eligible workspace. Do not paste passwords, Firebase credentials or personal API tokens into the client.
The grant is tied to that workspace and its approved scopes. OrbitPage rechecks role, plan, permission and revision on every call; switching the active workspace in a browser tab does not retarget the connection. You can revoke it from Dashboard > Team > Connected apps.
Read, preview, apply, publish and recover a page.
The remote server exposes get_workspace, get_page and get_page_capabilities for current state; preview_page_changes and apply_page_changes for reviewed edits; publish_page and get_publication_status for publication; and list_page_versions and restore_page_version for retained history.
A preview does not modify the draft. Applying the approved preview publishes by default, unless you explicitly ask to keep a private draft. Publishing that draft later requires its exact revision. Restore creates a new private draft and never publishes automatically.
- Read the current page and capabilities before proposing a change.
- Inspect the short-lived preview and confirm the exact result.
- Verify draft and published revisions after every write.
The signed-in dashboard offers a narrower, preview-only browser surface.
When a compatible top-level browser exposes site tools, the open OrbitPage dashboard can register three namespaced WebMCP tools: orbitpage_web_read_current_page, orbitpage_web_get_page_capabilities and orbitpage_web_preview_page_changes. They use the existing dashboard session and App Check, not a remote MCP OAuth token.
The browser preview consumes the normal AI allowance but withholds the commit capability. WebMCP cannot apply, publish or restore a page; those actions remain in the dashboard. Browser support and production availability may vary, and the normal editor works without WebMCP.
The ChatGPT plugin uses remote MCP; broader automation uses the REST API.
The public ChatGPT plugin packages the remote MCP server with instructions for a reviewed page workflow. It is the simplest path when you want to work with one connected OrbitPage page from ChatGPT. A compatible standalone MCP client can use the same remote endpoint and OAuth boundary.
For media, menus, additional pages, analytics, Shop, newsletters, domains or team operations, use the dashboard or the scoped personal-token Automation REST API. The public support chatbot is separate and cannot read your workspace.
