Agent connection and authorization problems

Confirm the client uses Streamable HTTP and the exact endpoint https://app.quire.bot/mcp. Compatible clients should discover Quire's OAuth endpoints automatically.

Approval does not open or complete

Make sure pop-ups or external browser handoff are allowed. Sign in to the intended Quire account, select a team where you are an active member, and complete any two-factor challenge. Rejecting the approval leaves the client unauthenticated.

Claude Code must use version 2.1.207 or newer and name the connection quire. Run /mcp after adding it. In Cursor, open MCP settings and choose Needs login. In claude.ai, reconnect the custom connector.

A connected agent cannot act

Check the approved scopes. Read, search, and write capabilities are separate. Also verify the authorizing member can access the target collection now; authorization never bypasses current visibility.

Review the Security page to see whether the session expired or was revoked. If IP binding is enabled and the client's public IP changed, create a new authorization.

Image forwarding fails

Automatic chat-pasted image forwarding requires the current Quire Claude Code plugin. Update the plugin, reload plugins, and retry once if a short-lived upload expired. Other clients should use a public HTTPS URL, supported base64 data, or an existing Quire image.