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

# Troubleshooting

Fixes for the most common problems connecting to the MCP and running tool calls.

***

### `get_workflow` returns 404 using the workflowId from an issue's `source` field

The workflowId in the issue source can be a snapshot reference. Use `list_workflows` against the product to find the live workflow IDs.

### OAuth sign-in opens but returns a 404 or never completes

Most often happens after a server-side deploy. Wait a few minutes and try again. If it persists, disconnect the integration in your client and re-add it to restart the flow.

### Tool calls return 401 / 403

Your OAuth session has expired, or you're authenticated to an organization that doesn't have access to the resource you're asking about. Re-authorize the connector and confirm you've selected the right organization. See [Authentication](/EfyQpV4281edZ3h0g8tY/integrations/devally-mcp/authentication.md).

### The MCP isn't appearing in my client

If you added DevAlly as a **custom connector** (Claude.ai, Claude Desktop), reopen the connector settings, confirm the URL is exactly `https://mcp.devally.com/mcp`, and click **Connect** again. If you configured it via a **config file** (Claude Code, Cursor), restart the client after saving so it picks up the change.

Either way, confirm `https://mcp.devally.com/mcp` is reachable from your network, and check the client's MCP status (`/mcp` in Claude Code; **Settings → Connectors** in Claude Desktop and Claude.ai).

### `npx mcp-remote` errors on first run

The first invocation downloads the package. Make sure Node.js ≥ 18 is on your `PATH` and you have outbound internet access. Re-run after the install completes.

{% hint style="info" %}
Still stuck? Email DevAlly support at <support@devally.com> with your client name and the exact error message.
{% 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/troubleshooting.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.