Connect an AI client to SimpURL

Before you connect

SimpURL exposes a public remote MCP endpoint at https://go.simpurl.click/mcp. Clerk is the sign-in service SimpURL uses: you complete your normal SimpURL sign-in in the browser. MCP uses OAuth, not an API key. API keys for REST integrations are managed separately in Settings > API keys. Never paste a password or sign-in token into an AI client.

AI connections are isolated to your Personal workspace. When a team workspace is selected, Settings shows that profile and AI connections remain personal; switch to Personal before managing this feature. Team members do not automatically share a personal MCP authorization.

OpenAI: connected apps availability Anthropic: MCP overview

AI connections showing the MCP server URL, 180-day access, client permissions, Renew, and Revoke — Example authorized clients. No real account credentials or connections are shown.

Enable the connection in SimpURL

Sign in to SimpURL and switch to Personal if a team workspace is active.
Open Settings, then choose the AI connections section. If it is unavailable, review your plan or switch out of the team workspace.
Turn on the Enabled switch. The panel shows the MCP server URL, the client list, the authorization window, and any previously authorized clients.
In your AI client, add a remote MCP server using the exact URL https://go.simpurl.click/mcp. Choose the sign-in or OAuth option when the client asks for authentication, then complete your SimpURL sign-in in the browser.
After authorization, let the client scan or refresh the server tools. Use the client help page for its exact menu names because connector setup differs by product and plan.

MCP server URL

https://go.simpurl.click/mcp

OpenAI: ChatGPT MCP apps OpenAI: Codex MCP setup example Anthropic: Claude Code MCP setup

Supported setup patterns

These are verified patterns for clients whose current documentation supports remote HTTP MCP. They are not a promise that every account or desktop build exposes the same connector controls.

Codex CLI or IDE: run codex mcp add simpurl --url https://go.simpurl.click/mcp, then run codex mcp login simpurl to open the browser sign-in. Confirm it with codex mcp list. The current Codex source documents login and logout for OAuth-enabled MCP servers.
Claude Code: run claude mcp add --transport http simpurl https://go.simpurl.click/mcp, then claude mcp list. Use /mcp to authenticate if Claude asks you to sign in.
Claude Desktop: open Customize -> Connectors, choose + or Add custom connector, enter https://go.simpurl.click/mcp, choose Add, then choose Connect and finish your SimpURL sign-in. This is a remote connector saved to your Claude account; do not create a local JSON server entry or install a desktop extension for SimpURL.
Claude Cowork: open the Cowork tab, then Customize and Connectors. Add or select the same custom remote connector and enable it for the conversation. Remote connectors are brokered through your Claude account, so Cowork does not need a local MCP process or a local config file.
Claude Team or Enterprise: an Owner or Primary Owner must first use Organization settings -> Connectors -> Add -> Custom -> Web and enter the URL. Members then use Customize -> Connectors -> Connect and complete their own SimpURL sign-in.
ChatGPT: when your account exposes custom MCP apps, use the current developer-mode flow on ChatGPT web: enable the feature if permitted, create an app with the endpoint, choose OAuth, scan tools, finish Clerk authorization, and select the draft app in a chat. OpenAI currently documents full write/modify MCP support for Business and Enterprise/Edu, with more limited Pro behavior; do not assume the same flow exists on mobile or every desktop surface.

Add SimpURL to Codex

codex mcp add simpurl --url https://go.simpurl.click/mcp

Sign in from Codex

codex mcp login simpurl

OpenAI: developer mode and MCP apps OpenAI: Codex remote MCP configuration OpenAI: Codex MCP login source Anthropic: custom remote MCP connectors Anthropic: desktop and web connectors Anthropic: Claude Code MCP

Review scopes and permissions

The OAuth grant is scoped. The connection record displays human-readable labels for the scopes granted to that client. Grant only the capabilities needed for the workflow, and expect write actions to change your SimpURL data immediately after the client calls them.

links:read - View links.
links:write - Create and organize links, including updating tags and assigning links to campaigns.
campaigns:read - View campaigns.
campaigns:write - Create and update campaigns.
analytics:read - View aggregated analytics and campaign analytics.
namespaces:read - View namespaces and mappings.
namespaces:write - Create, rename, delete unused namespaces, and manage domain mappings.
smart_paste:read - View Smart Paste sites.
smart_paste:write - Add or remove Smart Paste site patterns.

Renew or revoke access

Return to Personal -> Settings -> AI connections and find the client under Authorized clients.
Select Revoke on an active client to invalidate that SimpURL connection. The server rejects later calls from that revoked connection.
Select Renew on an expired or revoked client when AI connections are enabled and your account is still eligible. Renewal creates a new 180-day authorization window.
Use the status label, such as Active until a date, Expired, or Revoked, to confirm the result. Reconnect in the client if it still holds an old OAuth session.