Connect your assistant to FounderOmni

Use one MCP connection to work with selected SEO websites, Analytics websites and Social channels in a Workspace. Read-only is the default; saving notes, reports or drafts needs your explicit approval.

Start with Agent Setup

Open AI Agents → Agent Setup. Copy the universal setup prompt and paste it into an assistant that supports remote MCP. It should use its own supported setup flow and preserve your existing integrations.

Server: https://founderomni.com/mcp
Transport: Streamable HTTP
Authentication: OAuth with authorization code, S256 PKCE and resource binding.

1. Add the server in your assistant and begin OAuth sign-in.
2. Sign in with your FounderOmni account, review the requesting app and return address, and choose a Workspace.
3. Choose products and explicitly check the websites and channels you want to share. Optional write permissions start unchecked. Select an access expiry.
4. Return to the assistant and ask it to call get_workspace_context and list_workspace_resources. Confirm the Workspace and actual resources before starting work.

Available in this release

• SEO & GEO: saved evidence, website context, research notes and private reports. Each website call needs the selected SEO projectId.
• Web Analytics: existing traffic metrics, daily trends, top pages and sources for selected websites. Compare up to ten sites per call, using each site’s timezone. Unique visitor counts are distinct browsers per website and period; never add them across websites or days.
• Social: selected channel identities and unscheduled drafts. With draft-write permission, create and edit text-and-link drafts for review in FounderOmni. These tools cannot schedule or publish.

Workspace IDs, SEO project IDs, Analytics site IDs and Social account IDs are different. Always use the IDs returned by the resource-list tool.

ChatGPT

In your current ChatGPT Settings, find the controls for custom remote MCP apps or connectors. Developer mode or Workspace administrator approval may be required. Add FounderOmni with the full server URL above and choose OAuth. Use automatic client registration when offered; this server does not ask you to paste a client secret.

Complete FounderOmni’s approval page, then return to ChatGPT and select the connection in a new chat. Ask it to perform the two verification calls above. A setup explanation alone does not verify access. A local Codex connection is separate from a ChatGPT web connection.

See OpenAI’s authentication documentation. Client controls and account availability can differ.

Claude and other clients

Use the client’s remote MCP connector or native MCP configuration. Add the same server address, complete OAuth and verify a real read. Follow Claude’s remote connector instructions or your client’s official documentation. Do not paste passwords, access tokens or authorization codes into a chat.

Context and workflows

Workspace Context holds shared business background. Owners and admins edit it; authorized assistants can read it. Website-specific business facts and versioned notes remain in SEO → Website Context. Reports remain in SEO → Reports.

Ask your assistant to use the workspace_growth_review prompt to review evidence across products. SEO workflows remain available through get_seo_workflow; choose an authorized website before following them. Existing public SEO skills can still be installed in clients that support local skills. MCP tool refresh does not update local skill files.

Permissions, costs and revocation

Connections follow your current Workspace membership and product permissions. The approved resource list is fixed: new websites or channels need new consent. Product quotas continue to apply. Saved reads do not start paid research or model checks; normal backend costs and your external assistant’s usage still apply.

Review or revoke access in Connected Apps. Revocation stops access and refresh immediately. Access tokens last up to an hour, refresh tokens rotate, and neither outlives the approved 7/30/90-day grant.

Existing website-only SEO connections keep their original website and permissions. Reconnect to approve broader Workspace access. Clients without OAuth can keep using the advanced website-only SEO token connection; it does not provide cross-product access.

Connection help

Opening the server URL in a browser shows instructions. An unauthenticated protocol request receives a 401 OAuth challenge. Both are expected before authorization. Check server proves reachability; an authenticated tool call verifies access.

If approval expired, access was revoked, or your membership changed, restart sign-in from your assistant. If you need more products, resources or write permissions, reconnect and review a new approval. An active grant in Connected Apps does not prove a separate assistant has completed its setup.