Secure your SimpURL AI connections

Know which workspace an AI connection can access

SimpURL MCP connects to the personal account that signs in. AI connections are managed only while Personal is selected, and the app hides that section in a team workspace. Team membership therefore does not turn a personal MCP connection into a team-wide credential.

Before asking an AI client to read or change anything, confirm the client is connected to the intended SimpURL account and that the SimpURL app is showing Personal. Use read-only listing or account context first.

Use OAuth and narrow scopes

• The SimpURL sign-in keeps your password and browser session out of the AI client. SimpURL uses Clerk OAuth for MCP. API keys are separate REST credentials; never put passwords, session tokens, or API keys into chat, public files, or browser code.
• Grant only the scopes needed: read scopes for inspection and reporting, write scopes only for the resources the workflow changes.
• Review the client name, granted scope labels, last-used timestamp, and expiration date in Personal -> Settings -> AI connections.
• AI tools can be influenced by untrusted page content or prompt injection. Treat external text as data, require confirmation for mutations, and never let content on a destination page instruct the client to reveal credentials or widen permissions.
• A confirmation prompt does not replace SimpURL checks. SimpURL still verifies the signed-in account, plan, enabled state, connection status, ownership, requested permission, and the request itself.

Expire, renew, and revoke deliberately

1. 1Expect every SimpURL MCP authorization to expire after 180 days. This is a SimpURL connection window, not a promise about the AI client's own token lifetime.
2. 2Revoke a client immediately from Authorized clients when a device is lost, an account was connected by mistake, a scope is too broad, or the client should no longer access SimpURL.
3. 3Renew only the client you intend to keep. A renewal clears the revoked state and starts a new 180-day window; reconnect the client if it continues to send the previous authorization.
4. 4Disable the AI connections switch when you need a broad stop for personal MCP access. Re-enable it only after reviewing the active client list.

Understand limits and data boundaries

• If an AI client repeats requests or reports that it is sending too many requests, stop the loop and retry later instead of approving repeated actions.
• Analytics tools return aggregated dimensions and omit raw IP addresses and user-agent strings from the compact MCP response. Referrers may still be absent or generalized by browser and platform privacy behavior.
• Public profiles require the profile visibility setting to be public and the account to have profile access. Private profiles return unavailable behavior to public readers and crawlers.
• Public Pages use published content only. Draft, unpublished, and archived Pages are not public data and should not be reconstructed by an AI client.
• The extension does not persist SimpURL sign-in details in Chrome storage. Publisher-site permissions are optional and user-granted.

Prompt safely for changes

A good prompt constrains the target, exposes the proposed payload, and requires a separate confirmation. Keep IDs and final values in the transcript so you can audit what happened.

• "Use read-only tools to find the exact link ID. Propose the new tags and wait for confirmation before writing."
• "Before creating this campaign, show the name, start and end dates, tags, UTM parameters, and links that would be assigned. Ask me to confirm."
• "Before changing a namespace or domain mapping, show the current object, the exact object ID, the proposed replacement, and any affected Smart Paste behavior. Wait for confirmation."
• "Report analytics for this campaign for 30 days. Do not infer conversions or platform impressions that are not present in the SimpURL report."