Skip to content

Connect your assistant

MCP lets an AI assistant use Getsitecontrol tools in your conversation. You can ask about your account, investigate results, and perform supported changes.

MCP server URL

https://api.getsitecontrol.com/v1/mcp

You sign in to Getsitecontrol in your browser and approve access on our consent screen, which names the app and where it returns. No password, token, or key is pasted into a chat.

Other clients that support remote MCP servers with OAuth sign-in can connect the same way. Use the remote MCP or custom connector feature described in the client’s own documentation:

  1. Add a connection named Getsitecontrol with the server URL above.
  2. Choose OAuth if the client asks for an authentication method.
  3. Sign in to Getsitecontrol, check the account shown, and click Allow.
  4. Enable the connection for your conversation.

The client finds the sign-in endpoints from the server and identifies itself with its published client metadata document, so you do not need a client ID or secret. A client that supports only manual or dynamic client registration cannot connect. An API key is for the REST API and is not accepted by MCP.

Start with a read-only request:

Try this prompt

List the Getsitecontrol sites I can access. Show their names and IDs, and do not change anything.

Check that the expected account and sites are shown. Then choose the site you want to work on:

Try this prompt

Use the site example.com. List its widgets and their current status.

MCP includes tools that can change your account. Read each tool result and review changes in Getsitecontrol.

Widget tools change your own draft of the widget, kept by Getsitecontrol. The widget on your site changes only when the assistant saves the draft, which it should do after you approve the change. Other tools, such as those for contacts, segments or automations, change saved account data directly.