Skip to main content
Version: 3.x (Current)

MCP Troubleshooting

Common problems when connecting an AI client to the P4SaMD MCP server, and what to check. For connection instructions, see Setup.

Sign-in never completes, or the browser reports an error about the redirect URL​

Your client is redirecting to an address other than http://localhost or http://127.0.0.1, which the sign-in flow does not currently accept. This affects cloud-hosted connectors such as those in Claude.ai and ChatGPT. See the caution in Setup.

The assistant reports no available tools, or tools/list returns an empty result​

Either sign-in did not complete, or the session has expired. Sessions last 8 hours. Reconnect the client and complete the sign-in flow again.

A project is missing, or the assistant cannot see a project you expect​

MCP access is scoped to the single organization you chose during sign-in, for the whole session. If you belong to more than one organization and need to work in a different one, reconnect and choose that organization when prompted.

Within an organization, the assistant sees only the projects you have access to yourself. If a project is still missing, check your project membership in the web application.

A write action fails with a permission error​

The MCP server applies the same role-based permissions as the web application. See Roles and Permissions for the full matrix.

In particular, creating or editing requirements, risks or software items requires at least the Tech Team role in that project, and deleting a requirement additionally requires the Admin role. Check your role in the project if a write action is rejected unexpectedly.

A write action fails on a released version​

Some records cannot be changed once their version is released. Requirements in a released version cannot be updated at all, and edits to risks and software items on a released version require an explanation, which the assistant must supply as part of the call. Deprecated requirements cannot be updated either.