Togal is the hands, the AI assistant is the driver.

Note: TogalMCP is not a chatbot inside the Togal platform. It is a connection the user adds to an AI assistant they already use to work like them in Togal.

Common Issues

Cannot connect to TogalMCP or browser showing "Authorization header with a Bearer token is required"

Possible reasons:

AI assistants are not enabled by your organization
MCP url was typed directly into a browser

Troubleshooting steps:

Check your IT, AI security & Governance policy
Type MCP url as custom connector inside the assistant , never into a tab in your browser

ChatGPT	Claude

Can't add a custom connector at all

Possible reasons:

No admin access to add custom connectors

Troubleshooting steps:

Let your workspace admin ( IT or billing contact inside Togal) add the Togal connector for the organization

401, or connection keeps dropping

Possible reasons:

Lost connection while also signed into the Togal web app

Troubleshooting steps:

Sign out of the Togal web app, then reconnect the connector

Request Blocked

Possible reasons:

Unknown OAuth client_id when reauthorizing

Troubleshooting steps:

Delete the connector, type and search for Togal to add as a new connector; if it repeats, escalate via chat to Togal Customer Support inside the Togal platform

Constantly asked to sign in again after a week

Possible reasons:

The requests asks to authenticate login

Troubleshooting steps:

This is a safety measure. All MCP users are required to re-authorize weekly

Copilot overwhelmed when all tools are enabled

Troubleshooting steps:

Toggle on only the tools a task needs

404 on the final sign-in screen

Troubleshooting steps:

Retry, or use the short-code sign-in

SSO-enabled organization can’t use MCP

Possible reasons:

User can’t use SSO org through the connector

Troubleshooting steps:

MCP sign-in needs a Togal email and password. Try turning off Single sign-on (SSO) and password blocking temporarily. if it repeats, escalate via chat to Togal Customer Support inside the Togal platform

Tool Call & API errors

Scale endpoint Issues returns 400

Possible reasons:

POST /v2/togal/scale/{view} returns 400s: missing gross_area, missing gross_area_internal, code 3020

Troubleshooting steps:

Confirm scale - Set scale with PUT /v2/page/{page}. For 1/4" = 1'-0": {"scale_drawing": 0.25, "scale_real": 12, "scale_type": "architectural", "scale_units": "imperial"}
Start processing with POST /v2/togal/scale/{view} sending all 10 flags below and nothing else. { "gross_area": true, "gross_area_internal": false, "net_area": true, "walls_area": true, "count": true, "walls_centerline": true, "footprint": true, "doors_area": true, "doors_centerline": true, "walls_perimeter": true }

Step 2 saves the filters to the View, re-renders the page at the confirmed scale, and runs vectorization and area naming; results arrive asynchronously.

To confirm scale without starting AI processing, run step 1 only. Step 2 is the prerequisite for a paint workflow.

Overlaying drawings fails

Possible reasons:

MCP or In-app Chat to overlay a matching drawing set does nothing.

Troubleshooting steps:

In the app, open Compare Mode → Add overlay → pick the drawing → Add

Documentation has not specified if MCP should perform Overlay function yet. Subject to internal updates

Large drawing files can't be passed through the assistant

Troubleshooting steps:

Large drawings and blueprints will max out tokens significantly. Its best to use Togal for drawing uploads first, before implement tasks through TogalMCP