How to connect to and use the Siteimprove MCP Server

Summary

The Siteimprove MCP Server lets AI assistants and agents call Siteimprove's agentic capabilities directly, using the open Model Context Protocol (MCP).

Once connected, a compatible client (such as Claude, GitHub Copilot in VS Code, Cursor, or another MCP-enabled agent) can ask Siteimprove to check a page for accessibility issues and suggest code fixes, without you leaving your development or content workflow.

The Siteimprove MCP Server currently provides three tools:

• detect_from_url: checks a live, publicly reachable web page for accessibility issues.
• detect_from_html: checks a snippet of raw HTML you provide for accessibility issues.
• remediate: returns WCAG-grounded code-fix suggestions for supported accessibility issues.

What you need before you start

• A Siteimprove account with an active Accessibility subscription (Pro or Advanced).
• An MCP-compatible client (for example Claude, VS Code with Copilot, or Cursor).
• Permission to add a connector or edit your client's MCP configuration.

Which tools can I use?

Access to each tool depends on your Siteimprove Accessibility subscription and entitlements. Tools are enabled automatically based on what you're subscribed to. There's no separate setup required on your end.

If a tool call fails with an entitlement error, contact your Siteimprove administrator or Customer Success contact to check your subscription and entitlements.

Choosing your server URL

Use the endpoint for your data region.

If you are not sure which region your account is in, contact your Siteimprove administrator or Customer Success contact.

Connecting to the server

You connect with OAuth, signing in with your existing Siteimprove credentials so that tool calls run against your own account and entitlements.

1. In your MCP client, add a new remote MCP server and paste the endpoint for your region (see the table above).
2. When prompted, complete the sign-in with Siteimprove at identity.siteimprove.com.
3. Approve the connection. Your client can now call the accessibility tools.

VS Code example (mcp.json):

{
  "servers": {
     "accessibility": {
       "type": "http",
      "url": "https://mcp.siteimprove.com/mcp",
       "oauth": {
         "clientId": "8985f072-09c6-4284-9cfa-37f24b730182"
      }
    }
  },
  "inputs": []
}

Using the tools

After connecting, ask your assistant in natural language, for example:

• "Check https://example.com/pricing for accessibility issues."
• "Here's some HTML, are there any WCAG problems before I publish it?"
• "Suggest a fix for the missing form labels you found."

Your assistant selects the right tool and returns the results. Detection reports the issues found; remediation returns code-fix suggestions you can review and apply.

What the remediate tool covers

The remediate tool returns code-fix suggestions for a defined set of accessibility rules: the issues that can be reliably fixed at the code level. You can read more about the feature here: How to use AI Remediate to fix accessibility issues in Siteimprove

Troubleshooting

• The connection fails or asks me to sign in repeatedly. Confirm you are using the correct regional endpoint and that your Siteimprove account has an active Accessibility subscription (Pro or Advanced).
• A tool returns an entitlement error. The tool you called requires an entitlement your subscription doesn't currently include. See "Which tools can I use?" above. Contact your Siteimprove administrator or Customer Success contact about upgrading.
• My client can't add the server by URL. Some platforms only allow connectors from a curated catalog. Check your client's documentation for how to add a custom or remote MCP server.