> 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/installation.md).

# Installation

The DevAlly MCP is a remote server — you connect your AI client to it once, sign in with your DevAlly account, and pick your organization. Pick the tab for your client below.

***

## Prerequisites

* A DevAlly account with at least one workspace.
* An MCP-compatible client (Claude.ai, Claude Desktop, Claude Code, Cursor, etc.).

{% hint style="success" %}
**No API keys required.** Authentication is OAuth — you'll sign in with your DevAlly account on first connect and pick the organization you want to work with. See [Authentication](/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp/authentication.md) for details.
{% endhint %}

***

## MCP server details

|                           |                                                                                                                    |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Production server URL** | `https://mcp.devally.com/mcp`                                                                                      |
| **Transport**             | Remote MCP over HTTP (Claude Desktop / Cursor bridge via `mcp-remote`; Claude Code and Claude.ai connect natively) |
| **Authentication**        | OAuth 2.1 — sign in with your DevAlly account, then pick your organization                                         |
| **Rate limits**           | No published limit — email <support@devally.com> if you need higher throughput.                                    |

***

## Connect your client

{% tabs %}
{% tab title="Claude.ai (web)" %}
Easiest path for non-developers.

1. Go to **Claude.ai → Settings → Integrations → Add custom connector**.
2. Set:
   * **Name:** `DevAlly`
   * **URL:** `https://mcp.devally.com/mcp`
3. Click the new connector in the list, hit **Connect**, sign in with your DevAlly account, and pick your organization.
4. Start a new chat and ask *"list my DevAlly workspaces"* to confirm it's wired up.
   {% endtab %}

{% tab title="Claude Desktop" %}
The simplest path is the built-in custom connector.

1. In Claude Desktop, open **Connectors** (under Settings) and click **Add custom connector**.
2. Set:
   * **Name:** `DevAlly`
   * **Remote MCP server URL:** `https://mcp.devally.com/mcp`
3. Leave **OAuth Client ID** and **OAuth Client Secret** (under **Advanced settings**) blank — DevAlly registers your client automatically.
4. Click **Add**, then **Connect**, sign in with your DevAlly account, and pick your organization.
5. Test it: start a new chat and ask *"list my DevAlly workspaces"*.
   {% endtab %}

{% tab title="Claude Code" %}
Claude Code supports remote MCP servers natively — no shim needed.

Add a `.mcp.json` to your project root (for project-scoped access) or to `~/.claude.json` (for user-global access):

```json
{
  "mcpServers": {
    "devally": {
      "type": "http",
      "url": "https://mcp.devally.com/mcp"
    }
  }
}
```

Run `claude` in your terminal. The OAuth flow kicks off automatically on first use — Claude Code opens your browser to sign in to DevAlly and pick your organization.

Verify with `/mcp` inside a Claude Code session, or `claude mcp list` from the terminal.
{% endtab %}

{% tab title="Cursor / other IDEs" %}
Recent versions of Cursor connect to remote MCP servers natively. Edit `~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "devally": {
      "url": "https://mcp.devally.com/mcp"
    }
  }
}
```

Restart Cursor. The OAuth flow runs in your browser on first connect.

**Older Cursor, or another client?** Clients without native remote support (older Cursor, Windsurf, Cline, Zed) bridge to the hosted server through the `mcp-remote` shim instead:

```json
{
  "mcpServers": {
    "devally": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.devally.com/mcp"]
    }
  }
}
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
Hitting a 404, a sign-in loop, or a 401/403? See [Troubleshooting](/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp/troubleshooting.md).
{% endhint %}


---

# 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/installation.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.