# Connections troubleshooting

> Diagnose and fix Delegate connection, authentication, and MCP server issues: failed connections, missing scopes, and unreachable or misconfigured MCP servers.

## Connection failed, or an authentication error

**Cause:** The connection expired or was revoked.

**Solution:** Reconnect from **Add-ons & Integrations** → **Connections**.

If reconnecting doesn't fix it:
1. Disconnect and recreate the connection.
2. Check the service's own third-party app settings.

## "No connection found for \<service\>"

**Cause:** The service isn't connected yet.

**Solution:**
- Create the connection from **Add-ons & Integrations** → **Connections**.
- Or take an approach that doesn't need it.

## Delegate can't perform certain operations

**Cause 1:** The connection was created with narrower scopes than the action needs.
**Solution 1:** Disconnect and reconnect from **Add-ons & Integrations** → **Connections**, granting the additional scopes when prompted.

**Cause 2:** An organization policy restricts scopes.
**Solution 2:** Check with your administrator.

## MCP server won't connect

**Cause 1:** The server is down or unreachable.
**Solution 1:** Confirm it's running (local) or reachable (remote).

**Cause 2:** The URL or command has a typo.
**Solution 2:**
1. Check the URL.
2. Test the endpoint directly.

**Cause 3:** A firewall is blocking it.
**Solution 3:**
1. Check firewall settings.
2. Review the local process logs for a startup error.

## MCP server connects but has no tools available

**Cause:** It hasn't registered any tools, or they failed to initialize.

**Solution:**
1. Check the server's own documentation and environment variables.
2. Restart it.

## MCP tool call failed

**Cause:** The server received the request but couldn't execute it.

**Solution:**
- Check the specific error in the tool card.
- Confirm the required parameters were provided.
- Confirm the underlying resource (file, database, API) is reachable.