> ## Documentation Index
> Fetch the complete documentation index at: https://docs.printools.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Resolve PRINTOOLS connection, permission, approval, and operation-status problems.

## The connection cannot be added

Use exactly `https://mcp.printools.io/mcp`, including the final path. Do not use the documentation URL or a development API URL as the connection endpoint.

In ChatGPT, check **Settings → Security and login → Developer mode**, then **Plugins → +**. In Claude, check your connector controls and any workspace-owner requirement. Follow [ChatGPT setup](/mcp/connect-chatgpt) or [Claude setup](/mcp/connect-claude).

## Sign-in or refresh fails

Complete the OAuth flow for the intended PRINTOOLS account. If a stored session can no longer refresh, reconnect. Never share passwords, bearer tokens, or refresh tokens in a support message.

For custom client implementations, verify the resource URL, registered redirect URI, and PKCE against [Authentication](/mcp/authentication).

## A tool or action is missing

Refresh client discovery and start a new conversation. Then check the scopes approved for this connection. Tool groups include only authorized child actions; a group can disappear when none of its actions are available.

A feature's existence in the PRINTOOLS app or in this catalogue does not establish that it is enabled for your MCP grant. Do not invent an action name to work around a missing capability.

## The wrong organization appears

Use an available current-organization read in `settings_manage`. Disconnect the client connection and authorize again for the intended account and organization. An existing browser session in the PRINTOOLS app does not by itself prove the MCP connection uses that organization.

## A request is forbidden or a record is not found

Check your role, grant scopes, and organization. Verify the record ID with a permitted search or list action. Do not repeatedly try unrelated IDs. A tool being visible does not guarantee access to every record.

## Invalid action or input

Follow the exact returned schema: select an advertised `action` and provide its `input`. Names are case-sensitive. Resolve required IDs, valid status values, and missing fields before retrying.

## Approval is required

`APPROVAL_REQUIRED` is not a completed write. Use the supported PRINTOOLS-hosted flow. If your client cannot complete it, keep the operation unexecuted and report the missing approval capability. See [Approvals](/mcp/approvals).

## The assistant says it sent something, but it has not arrived

Read the actual delivery or operation status using the returned identifier. Accepted and pending results are not evidence of delivery. Check the recipient and error summary, and avoid a duplicate send until the original request's outcome is known.

## Large reads or rate limits

Narrow the date range or selection, follow pagination, and respect a returned retry delay. Do not retry an entire bulk write merely because its result was too large for the conversation.

## Reporting an issue

Provide the client name, approximate time, tool/action, exact error code, and correlation ID when returned. Include the affected record or operation ID only through an appropriate support channel. Omit credentials and approval claim tokens.

[Overview](/mcp/overview) · [Tools](/mcp/tools) · [Authentication](/mcp/authentication)