# Troubleshooting

Find the message you see, or the problem you have, below.

## Connecting

### This app cannot be connected

Subbly shows this page instead of the consent screen, with one of these
reasons:

| Message | What to do |
| --- | --- |
| Only the store owner or an admin can connect apps. | Ask the shop owner to give you the admin role, or to connect the app. |
| Your store does not have an active Subbly subscription. | Reactivate your Subbly subscription, then connect again. |
| Your account does not belong to a store. | Log in with the Subbly account of the shop you want to connect. |
| You are signed in to this store from Subbly admin. Apps cannot be connected while you masquerade. | Superadmins only: stop masquerading. The shop owner or an admin must connect the app. |

### The redirect_uri is not registered for this app

The app sent Subbly a callback address it did not register. This happens
when an app changes its settings after it registered. Remove the Subbly
server from the app, add it again, and connect.

### The browser opens, but the app never finishes connecting

- Desktop and command-line apps wait for the login on a local port. Keep
  the app open until the browser says you can close it.
- A firewall, VPN or browser extension can block `localhost`. Try again
  with them off, or in another browser.
- Log in to Subbly in the same browser window the app opened.

### The app asks for an API key, a header or a client secret

Subbly's MCP server signs in with OAuth only. Remove any header from the
app's settings, pick **OAuth** if it asks for an authentication type, and
leave the client ID and client secret empty. The app registers itself.

### The consent screen says “Unverified app”

The app registered itself instead of publishing its details. That is normal
for many desktop and command-line apps. Allow it only if you started the
connection yourself a moment ago. See
[Security and access](/developer-resources/subbly-mcp/security-and-access#the-consent-screen).

## Using the tools

### “This action needs the Subbly X plan”

The tool is in an area your plan does not open. See
[Plans and limits](/developer-resources/subbly-mcp/plans-and-limits).

### “The … feature is not available on your current plan”

A field in the request needs a plan feature, such as coupon customisation,
optional pause or gift cards. Ask the agent to try again without that field,
or check [Limits by resource](/developer-resources/subbly-mcp/plans-and-limits#limits-by-resource).

### Too Many Attempts.

The shop went over a rate limit, or two subscription changes ran at the
same time. Wait a minute. Then ask the agent to make one change at a time.

### Tool execution failed: …

The rest of the message comes from the Private API. It usually names the
field that is wrong, such as a date in the past or a product that does not
exist. The agent can read it and fix its request. If it keeps failing, look
up the field in the [Private API reference](/api/private).

### The app stopped working or asks me to log in again

The connection ended. That happens when:

- someone clicked **Disconnect** in **Settings › Connected apps**,
- the person who connected it is no longer the shop owner or an admin,
- the shop's Subbly subscription is not active,
- nobody used the app for 30 days.

Connect the app again. If the reason was a role or the subscription, fix
that first.

### The agent does not see a new tool

Apps load the tool list when they connect. Restart the app or reconnect the
server to load the latest list.

## Test the connection

First, check that the server answers. A request with no token should get
HTTP `401`:

```bash title="Check the server"
curl -i -X POST https://mcp.subbly.dev/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

```text title="Expected"
HTTP/2 401
www-authenticate: Bearer resource_metadata="https://mcp.subbly.dev/.well-known/oauth-protected-resource/mcp"
```

Then check the login settings the app reads:

```bash title="Check OAuth discovery"
curl https://mcp.subbly.dev/.well-known/oauth-protected-resource/mcp
curl https://www.subbly.co/.well-known/oauth-authorization-server
```

Last, ask your agent:

> Can you connect to Subbly? List my published subscription products.

If the agent lists your products, everything works.

## Get help

Still stuck? Contact [Subbly support](https://support.subbly.co). Tell us
which app you use, what you asked, and the exact message you saw.