AI tool permissions

Know what an AI tool can do before you connect it

SEO Dispatch MCP gives an authorized AI coding tool bounded access to saved implementation Guides. Reading is the default. Starting Guide work is a separate permission you choose.

Availability depends on workspace rollout. Client versions are not described as tested until release evidence is recorded.

Permissions stay narrow and visible

New connections start with Read SEO Guides. The optional Start Guide work permission is the only action that changes SEO Dispatch state.

This AI tool can

View the workspace or workspaces you select.
Read properties, open SEO fixes, saved implementation Guides, and bounded fix context.
If you explicitly allow Start Guide work, mark a Guide or selected fixes as used and move new fixes to In progress.

It cannot

Edit your website or local code, publish content, or deploy changes.
Run scans or live verification, dismiss fixes, or mark work Applied or Done.
Access billing details, Google tokens, CMS credentials, provider keys, or unselected workspaces.

Connect safely

Choose a client only when its exact version and verification date appear in the connection instructions.
Add https://seodispatch.app/api/mcp as the remote MCP server URL in that client.
Check the client identity and redirect origin shown by SEO Dispatch. Deny an unfamiliar request.
Select only the workspaces the client needs.
Keep Start Guide work off unless you want the client to move selected fixes to In progress.
Approve the connection, then ask the client to list available Guides before acting on one.

Never paste an access token into chat or a configuration file. A successful Start Guide work response should say that fixes are In progress, nothing was marked Done, and no website changes were made.

Give your AI assistant a safe setup brief

If a compatible AI tool can configure a remote MCP server for you, give it the brief below. Complete sign-in and consent yourself in the SEO Dispatch browser window.

Set up SEO Dispatch as a remote MCP server using the URL shown above. Do not ask me to share my SEO Dispatch password, MFA code, browser cookies, access token, refresh token, or OAuth code. Start the standard sign-in and consent flow, then pause while I complete sign-in and approval directly in SEO Dispatch. I will verify the client identity and redirect host, choose the minimum required workspaces, and keep Start Guide work off unless I explicitly enable it. After approval, list available Guides before taking any action.

This is a generic MCP setup brief, not a compatibility guarantee for Codex, Cursor, Claude, or another client. Connect only when the client's exact version and test date are recorded by SEO Dispatch.

You control what ships

MCP provides Guide information to the AI tool you authorize. SEO Dispatch does not inspect that tool's later changes or publish them for you. Before using any output, review its assumptions, inspect the proposed files, run appropriate tests and security checks, keep a rollback path, and decide whether the change is suitable for your site.

You remain responsible for the connected accounts, instructions you give the tool, implementation decisions, and anything you choose to deploy or publish.

You can always copy or download a saved Guide instead of connecting an AI tool.

Review or remove access

Authorized AI tools shows the client, selected workspaces, permissions, connection time, and last use. Turn off Start Guide work to return to read-only access, remove individual workspaces, or revoke the connection completely.

Revocation blocks new SEO Dispatch requests. Remove the server from the AI client too. If any request succeeds after revocation, report it to your workspace administrator immediately.

Troubleshooting

The connection expired or was revoked: Remove the stale client connection, reconnect through SEO Dispatch, and approve the smallest required permissions.
The wrong workspace appears: Revoke access, confirm your SEO Dispatch account, then reconnect and select the intended workspaces. Do not continue using unexpected workspace data.
The client can read but cannot start work: Start Guide work may be off, the Guide may require approval, or an administrator may have paused state changes. Read access can remain available independently.
The client claims it can publish or mark work Done: Stop and deny the action. Those capabilities are outside the SEO Dispatch MCP permission boundary.

Need complete setup or privacy details? Open Authorized AI tools in Settings, read the Privacy Policy and Terms, or ask your workspace administrator for the current tested-client instructions.

Loading SEO Dispatch