> For the complete documentation index, see [llms.txt](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp.md).

# DevAlly MCP

The DevAlly MCP lets your team query and manage your accessibility testing directly from any AI assistant that supports MCP — Claude.ai, Claude Desktop, Claude Code, Cursor, and others. Ask plain-English questions like *"what critical issues are open on our checkout product?"* and get answers without leaving your editor or chat.

***

## What the DevAlly MCP gives you

Connect it once, then ask your AI assistant questions and give it instructions in plain English. The assistant talks to DevAlly on your behalf, so you don't need to learn a new UI for every task.

You can use it to:

* **Pull issues and cases** — *"Show me all critical open issues on our marketing site."*
* **Investigate a single issue** — *"What's the recommended fix for issue ABC-1, and which pages does it affect?"*
* **Trigger audits** — *"Run a site audit on our login product and tell me when it's done."*
* **Manage workflows** — *"List the user journey workflows we have set up for the checkout product."*
* **Build reports** — *"Generate a stakeholder report of all serious-and-above issues from the last 30 days."*
* **Track progress** — *"How many issues have we resolved this quarter, broken down by product?"*

{% hint style="info" %}
New here? If you just want to ask questions, start with [Using the MCP](/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp/using-the-mcp.md). If you're setting it up for the first time, jump to [Installation](/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp/installation.md).
{% endhint %}

***

## Explore this section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-comments">:comments:</i> <strong>Using the MCP</strong></td><td>Example prompts, tips for getting good answers, and what the MCP won't do.</td><td><a href="/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp/using-the-mcp.md">Using the MCP</a></td></tr><tr><td><i class="fa-download">:download:</i> <strong>Installation</strong></td><td>Connect DevAlly to Claude.ai, Claude Desktop, Claude Code, or Cursor.</td><td><a href="/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp/installation.md">Installation</a></td></tr><tr><td><i class="fa-lock">:lock:</i> <strong>Authentication</strong></td><td>How OAuth sign-in works — no API keys to generate or rotate.</td><td><a href="/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp/authentication.md">Authentication</a></td></tr><tr><td><i class="fa-wrench">:wrench:</i> <strong>Troubleshooting</strong></td><td>Fixes for the most common connection and tool-call problems.</td><td><a href="/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devally.com/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.