Skip to main content

Connect Cloneable to Claude and ChatGPT

Connect an AI assistant to your authorized field data, review records, and create custom reports.

Connect an AI assistant to your Cloneable organization to inspect field jobs, review records against criteria you define, and create custom files from authorized data.

Before connecting

You need an existing Cloneable account, active organization membership, and MCP access enabled by your organization. Your organization role and the permissions you approve determine which tools and operations are available.

Connect Claude

In Claude, open Customize → Connectors and add a custom remote connector named Cloneable. Use https://api.cloneable.ai/mcp as the server URL. Start Connect, sign in using your normal Cloneable sign-in method, and review the requested permissions. OAuth clients register automatically; you do not need to enter a client ID or secret. If your Claude workspace restricts custom connectors, ask its administrator to approve access.

Connect ChatGPT

Until the directory listing is published, use ChatGPT Developer Mode to create a custom app with the name Cloneable and server URL https://api.cloneable.ai/mcp. Choose OAuth. The discovered configuration uses Dynamic Client Registration. Review the requested scopes, then sign in to Cloneable and approve access. Developer Mode is intended for testing; availability depends on your ChatGPT account and workspace settings.

Confirm your organization

After connecting, ask: “Confirm my Cloneable organization and list the field jobs I can access.” Check the organization name before proceeding. If it is wrong, ask the assistant to list your available organizations and select the intended one.

Try it

“Find my job and summarize its configuration and export status.”

“Review five active poles for missing location, pole class and grounding values. Label the sample, distinguish missing from unknown, and do not change anything.”

“Create a custom CSV for those five poles with object_id, pole_class, is_grounded and location_available. Leave unknown values blank and preserve false values.”

QA follows the criteria you provide; a job status badge does not prove completion. Ask the assistant to state the records reviewed and any unknown checks. Custom CSVs and reports are files the assistant builds from returned data, separate from launching a configured integration export.

Permissions and changes

Read tools retrieve records allowed by your organization membership and role. Write tools can update data, run configured operations, or administer access when your role and approved scopes permit it. Confirm targets and proposed changes, and request a dry-run preview where supported before saving. Queuing an export does not mean the export completed.

Data shared with your assistant

Tool results can include job records, customer-entered fields, names, photos, locations, and activity data when available to your account. Connecting authorizes your chosen AI service to receive the results it requests within your permissions. Review that service’s privacy and retention settings and your organization’s policies before connecting. Treat temporary download links as private.

Troubleshooting and disconnecting

If write tools are missing, check both the OAuth scopes you approved and your organization role; reconnect after correcting permissions. An administrator may need to enable MCP access. Expired sessions may require reconnection. For incomplete data, ask for unknown values rather than inferred facts. Large reports may require a download; if unavailable, request a clearly labeled bounded sample. Disconnect Cloneable in the AI assistant’s connector settings when access is no longer needed. Disconnecting does not delete information already included in chats or exported files; manage those in the AI service.

For help, visit https://help.cloneable.ai. Do not include passwords, access tokens or signed download links in support screenshots.

Did this answer your question?