---
title: "Troubleshooting"
description: "Check the address, the authentication method, the membership and the tool list."
canonical: https://past.dev/docs/mcp/troubleshooting
last-updated: 2026-10-09
---
# Troubleshooting

> Check the address, the authentication method, the membership and the tool list.

Product: past.dev MCP Server. Source: https://past.dev/docs/mcp/troubleshooting

| What you see | What to do |
| --- | --- |
| **“Couldn't register” or the connector will not add** | Check the URL is exactly `https://app.past.dev/mcp` for the account server, with no trailing slash and no path after `/mcp`. Leave the advanced client ID and secret fields empty. |
| **It connects, but the tool list is short** | The list is filtered by your platform role. A Member sees the project tools they reach and nothing about members or access; Billing sees the plan and usage and nothing else. Call `get_viewer` to see the role you are acting under. |
| **It connects, but the tool list is empty** | The caller did not resolve to an accepted membership. Check that your invitation was accepted, and that the membership still exists. |
| **A tool the docs list is missing** | Your role does not hold its scope, so it is never advertised. Section 03 names the role each tool needs. Ask an Owner or an Admin to change the role, or to run the action in the console. |
| **A destructive call did nothing** | A destructive tool without `confirm: true` does nothing on purpose. It answers with the sentence describing what it would do. Read that sentence, then tell the assistant to go ahead. |
| **`project-required`** | The organization has several live projects and the call named none. Give the project's slug, exactly as `get_viewer` or `list_projects` returned it. |
| **`429` with `Retry-After`** | The per-person rate budget is spent. It is shared by every client and token you connected. Wait the stated interval. |
| **Suddenly unauthorized mid-session** | The token expired and the refresh failed, or the membership changed. Reconnect the connector. On the end-user server, check that the identity still matches the connection's access rule. |
| **One of your users is refused at sign-in** | The Refused page names the reason: the server is off, no login connection is enabled, the connection refuses people it has not seen, or the identity does not match the access rule. It never says which trait fell short. Check the rule on Build › MCP server. |
| **Results are from the wrong organization** | The account connection follows your account's active organization. Switch it in the console; the change applies from the following call. |

#### Confirming the server itself is healthy

```
curl -i -X POST https://app.past.dev/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'
```

A healthy server returns `401` with a `WWW-Authenticate` header naming its discovery document. The client uses that response to find the sign-in service. A 403, a 404 or a timeout usually means the address is wrong.