Connect Claude or ChatGPT to search, read and update authorized Cartograph information from a conversation. The connection acts as your Cartograph identity in the workspace you select.

Review both sides of the connection: Cartograph permissions and the external client’s access, confirmation and data-handling settings.

Before you start

You need an eligible external-assistant account and permission under its organization policy. Client availability and setup labels can change; use the official references below if your screen differs.

Scout Agent Permissions page showing global controls and the tool permissions introduction.

Permissions controls apply alongside channel and connection access.

Connect and verify the client

Confirm you can enter the intended Cartograph workspace and have accepted the current terms yourself. Ask an administrator to check that Connected assistants is enabled in Scout → Deploy → Permissions.
In Claude, open Settings → Connectors → Add custom connector where your account supports it. Name the connection Cartograph and use the server address shown below.
In ChatGPT, use the supported custom MCP app/connector flow in developer mode where your plan and organization policy allow it. Use the same server address.
Connect, sign in to Cartograph and select the intended workspace. Review the access request before approving it.
Ask a narrow read question first, such as finding a record by its identifier. Inspect the returned workspace context and links.
For a change, review the client’s confirmation and then inspect the saved result in Cartograph. Keep email drafts for review and sending in Cartograph.

Check the result

The assistant reads the intended workspace under your access. A change is complete only when the target task, record, draft or other supported resource reflects it.

Server address

Use https://mcp.cartograph.ai/v1. Each authorization selects one workspace. Reconnect with the intended workspace if you chose the wrong one.

What the assistant can do

Supported tools can find records, tasks, conversations and knowledge; inspect reports; create or update supported records and tasks; organize Inbox; and prepare email drafts. Review the tool list in your connected client for its available operations.

The connection follows workspace access and Scout Chat permissions. A tool set to Never is refused. The connected client controls its change-confirmation prompts; changing its “always allow” policy can reduce prompts, so review that policy deliberately.

Administrator controls

In Scout → Deploy → Permissions, administrators can turn connected assistants off for the workspace and inspect connected teammates. Turning the global control off blocks their access while retaining connection entries.

Use Disconnect to revoke a specific connection. Removing Cartograph from the client is also part of managing the client-side connection. Verify revocation by checking the connection state rather than assuming a particular delay.

Data handling

Information returned to Claude or ChatGPT is handled by Anthropic or OpenAI under their terms and your account settings. Review your organization’s policy before using workspace information with an external assistant.

A connected assistant sees what your identity can access; it does not grant access to another person’s private mailbox. Creating a task can still lead to normal downstream work under the workspace’s rules and permissions.

If something does not look right

What you see	What to check
The client says terms acceptance is required	Open Cartograph and review the current terms yourself before retrying.
A supported action is refused	Check the workspace, identity, global Connected assistants control and Scout Chat permission.
The connector option is missing	Check your client plan, organization policy and the current official setup instructions.

Can I connect another workspace?

Each authorization is tied to the selected workspace. Disconnect and reconnect using the intended workspace.

Does connecting authorize unattended changes?

Review the client’s confirmation policy and Cartograph permissions. Do not assume every future action requires a fresh prompt if the client allows you to remember approvals.