Skip to content

DataScope MCP connector

Connect DataScope to Elaichi and Claude, ChatGPT, Cursor or any MCP client can read form answers, update statuses, manage locations and track signature requests, each person inside their own access, every call logged.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect DataScope to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect DataScope once

  1. Open Connections, choose Add connection, and pick DataScope.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a DataScope API key. One person generates a token in DataScope and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

datascope
DataScope
Alchemer
Canny
Fillout
Fulcrum
Google Forms
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

DataScope MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

DataScope MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

DataScope MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect DataScope to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with DataScope through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Operations

    Catch up on today's field submissions

    Ask which DataScope forms came in from each site this morning and get the answers summarized before the standup, without opening every PDF.

  • Field service

    Move a finished inspection to approved

    Once a technician's checklist is in, change the answer's status to approved or send it back for correction in a single request.

  • Quality

    Find every failed audit in a form

    Pull the answers for a quality checklist, keep only the ones that failed, and see the sites and dates listed together.

  • Safety

    Chase outstanding signatures on incident reports

    List the signature requests that are still open and see which safety forms are waiting on a signer.

  • Facilities

    Keep the site list current

    Add a new location or correct an address so the next form picks the right place, no spreadsheet upload required.

  • Office

    Get the next step started when a PDF is signed

    Set up a flow so a newly signed or rejected PDF in DataScope kicks off what follows, such as a status change or a hand-off to another team.

Try asking

  • “Summarize yesterday's safety checklist answers by location”
  • “Which signature requests are still waiting on a signer?”
  • “Mark the plant 3 inspection answer as approved”

See all 38 DataScope tools below

Compare

Elaichi vs Zapier MCP vs Composio for DataScope

All three can connect DataScope to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for DataScope, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over DataScope tools Allow or restrict single DataScope tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per DataScope call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

DataScope tools for your AI agents

38 tools are ready to call through Elaichi's MCP endpoint the moment you connect DataScope, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting DataScope gets you

6 screens from the product, each doing one job for your DataScope account.

The agent

Ask DataScope a question, get live answers back.

Form submissions, task status and open signatures, answered in plain language from live records.

  • forms
  • answers
  • locations
  • signature requests

Ask Elaichi to work across your apps.

Summarize yesterday's safety checklist answers by location

Which signature requests are still waiting on a signer?

Mark the plant 3 inspection answer as approved

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint serves Claude, ChatGPT and Cursor.

Work with DataScope forms from any MCP client, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

38 DataScope tools, ready with no custom code.

Forms, answers, statuses, locations, signature requests and hooks, covered without an engineer.

  • Get single DataScope form schema by ID
  • Create a DataScope hooks flow
  • List all DataScope tasks forms flows
  • List all DataScope list users
ElaichiTools
Tool Action Description
Get single DataScope form schema by ID Get Get the field schema of a selected form in datascope. Returns the schema object with its id and attributes containing the form's form-specific question and field definitions. Required: id.
Create a DataScope hooks flow Create Register a hooks flow webhook in datascope that fires when a new answer is submitted for a form. Returns the registration outcome in result. Only one active connection per form is supported. Required: hooks_flow_id, subscription_url.
List all DataScope tasks forms flows List List the forms available in the Datascope account. Returns the form entries with their type, key, and label.
List all DataScope list users List List the users available in the datascope account. Returns an array of user records with type, user_key, and identifier. Takes no query or body parameters.
Create a DataScope power automate finding changed status Create Create a Power Automate trigger subscription in DataScope that fires whenever a ticket changes its status. Returns the registration outcome (result). Only one active connection per account is supported. Required: event, subscription_url, version, platform.

Toolboxes

Every team gets its own DataScope toolbox.

Field service, quality and safety each see the forms and answers they work with.

  • Operations
  • Field service
  • Quality
  • Safety
ElaichiToolboxes
Name Source template Tools Created

Operations toolbox

DataScope · forms and answers

DataScope starter 18 Mar 4, 2026

Field service toolbox

DataScope · tasks and checklists

— 9 Mar 2, 2026

Quality toolbox

DataScope · audits and statuses

— 24 Feb 27, 2026

Safety toolbox

DataScope · incident reports and signatures

DataScope starter 6 Feb 19, 2026

Facilities toolbox

DataScope · locations and site lists

— 31 Jan 30, 2026

Admin toolbox

DataScope · users and flows

— 12 Jan 22, 2026

Shared connections

Share a DataScope connection, never the API key.

One person connects, teams work through it, and nobody else handles a credential.

  • Field ops
  • Quality
  • Safety
  • Facilities
ElaichiConnections
Connection Scope Status Access
DA

DataScope (Field ops)

Connected by Emily Carter

Personal • Active 1 team · 6 members
DA

DataScope (Quality)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
DA

DataScope (Safety)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
DA

DataScope (Facilities)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
DA

DataScope (Plant north)

Connected by Ryan Hayes

Personal • Active Not shared
DA

DataScope (Contractors)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every DataScope change is logged with a name.

See who updated an answer status or location, when, and on which record.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

DataScope Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

DataScope Forms Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

DataScope Forms List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule starts the digest, a person approves.

Yesterday's DataScope answers are fetched, grouped by site, drafted, approved, then posted back.

DataScope digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch forms

    DataScope

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    DataScope

    Queued

Collections and dashboards

DataScope health, computed on a schedule, no model.

Four metrics, 14 days of answers created, and a breakdown by team, refreshed automatically.

DataScope health

Refreshed 4 minutes ago · every 15 minutes · from the forms collection

Live

Forms

1,284 ↓ 12%

Answers

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Forms created

Last 14 days

By team

Share of activity

Field ops 34%

Quality 27%

Safety 21%

Facilities 18%

FAQ

Frequently asked questions

How do I connect DataScope to Claude?

Two steps. In Elaichi, add DataScope and paste in your DataScope API key, which you copy from your DataScope account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and DataScope forms, answers and locations are available in the conversation.

Does DataScope work with ChatGPT and Cursor as well as Claude?

Yes. DataScope is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. There is nothing extra to set up per client.

What can an AI agent actually do with my DataScope data?

It can list the forms your team uses, read the answers submitted against them, change an answer's status, add or correct locations, look up list elements and check which signature requests are still open. It can also set up flows that react when a PDF is signed, rejected or a status changes in DataScope. Short, concrete asks such as "show yesterday's answers for the safety checklist" work better than long paragraphs.

Does connecting DataScope give the AI access to every form and answer?

No. Every request runs as the person who signed in, so the AI sees only the DataScope forms, answers and locations that person can already see. Elaichi can narrow that further by role or by action, and it never widens what DataScope itself allows.

Can my team share one DataScope connection?

Yes. One person connects DataScope with the API key and shares the connection with a team in Elaichi; nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who changed an answer status or added a location, not the account that connected it.

Can I stop an agent from deleting or changing things in DataScope?

Yes. Restrictions in Elaichi work per action, so you can allow reading DataScope answers while blocking status updates, location edits or hook deletion. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.

What happens to a DataScope connection when someone leaves?

Offboarding that person in Elaichi ends their access to DataScope through every client at once. A shared DataScope connection keeps working for everyone else on the team. If you disconnect DataScope in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client in one step.

Does the DataScope MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. DataScope is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for DataScope?

Yes. Both let Claude, ChatGPT or Cursor use DataScope. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every DataScope call.

How is Elaichi different from Composio for DataScope?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to DataScope: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put DataScope in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.