YOUR WORKSPACE, IN YOUR ASSISTANT

One growth engine.
Wherever you ask.

Bring your Organiq plan into a compatible assistant. Connect your workspace, ask it to read the evidence, and have your coding agent prepare changes for review. You keep control of research charges and publication.

Your MCP endpoint

Connect from Claude

1. Open Claude Settings → Connectors → Add custom connector, where available on your account.
2. Enter the Organiq MCP URL above.
3. Follow the authorization link, sign in to Organiq, choose your workspace, and explicitly approve the connection.
4. Ask Claude to retrieve your websites or prepare a research quote.

Custom connector availability depends on your Claude plan and client. See Claude’s official connection guide.

Connect from ChatGPT

1. Use ChatGPT’s supported custom app or developer-mode settings, where enabled for your account or workspace.
2. Create a remote MCP connection using the endpoint above and OAuth authentication.
3. Authorize the Organiq workspace in the browser.
4. Enable Organiq in your conversation and request a price quote.

Plan availability and workspace administrator controls can differ. This development server is not listed in an app directory. See OpenAI’s official developer-mode guide.

Your journey, from plan to progress

1. Connect your workspace. Add the endpoint in a compatible MCP client, sign in to Organiq and approve workspace access.
2. Read the plan and its evidence. Ask: “Read my latest Organiq plan. Explain the supporting data and prepare every recommended website change.” Reading saved results does not start paid research.
3. Prepare changes. Your coding agent retrieves the complete implementation prompt, evidence and acceptance checks. It also needs access to your website repository.
4. Review the returned work. The agent returns a preview or pull request to Organiq. You review it and authorize deployment separately.
5. Record what went live. Return the live URL and deployment time. Organiq checks public page evidence, Google indexing when connected, and received customer completions when measurement is installed.
6. Review what changed. Ask for the latest review and weekly history. Repeated assistant questions keep their model, date and collection method. New paid research still needs an approved quote or existing recurring allowance.

MCP carries context between Organiq and your assistant. It does not itself grant access to your website hosting or authorize a deployment. A passed page check does not prove indexing, traffic growth or business impact.

Prefer to copy one prompt?

Open Actions and choose “Read the prompt” or copy the complete plan. Paste it into your coding agent, review its changes, then report the returned work in Organiq. This path works without MCP.

Try these prompts

• “Show my latest findings and the data behind them.”
• “Prepare all pending website recommendations as a pull request.”
• “Return this preview to Organiq for owner review.”
• “What changed since the last review, and what should we do next?”
• “Quote a refreshed assessment, then wait for my approval.”

Spending stays in your control

Paid tools return a price quote. They do not start research until you approve the maximum charge. One dollar equals one dollar of credit. Existing reports can be retrieved without new research charges. MCP tools never purchase credits silently.

Available tools

Website intelligence: analyze_website, get_website_profile, update_website_profile, list_websites.

Research: discover_keywords, discover_ai_questions, run_ai_visibility_audit, get_ai_search_queries, get_ai_citations, analyze_competitors.

Execution: get_plan_execution_brief, get_growth_brief, get_execution_brief, record_action_delivery, verify_action_delivery, update_growth_task, set_growth_monitoring.

Planning: generate_opportunity_report, get_growth_forecast, generate_content_strategy, list_content_opportunities.

Evidence and monitoring: get_evidence_lineage, get_growth_review, get_weekly_history, run_weekly_check.

Measurement and account: get_organic_performance, get_ai_visibility, compare_visibility, get_growth_recommendations, get_usage, get_wallet, get_subscription.

Jobs: approve_paid_operation, get_job_status, get_job_result.

Security and verification status

OAuth uses PKCE, scoped tokens, resource audience validation, rotating refresh tokens, and revocation. Every tool is tenant-scoped. Publishing requires recorded web-app approval and owner permission.

This development deployment uses an existing Clerk development instance. Interactive account authorization and the official MCP SDK connection have been tested. Direct consumer ChatGPT and Claude client connections remain unverified until client access is available. A dedicated branded production identity instance is a launch requirement.