Skip to content

Analytics

StreetLight Data MCP connector

The StreetLight Data connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent create zone sets, launch and track analyses, read metrics and segment counts, and manage tags inside StreetLight Data, all under each person's own access.

Connect on Elaichi How to connect
  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

List every analysis still running for the Route 9 corridor study

Working in StreetLight Data with Elaichi

  • List all StreetLight Data zone sets
  • StreetLight Data osm IDS search
  • List all StreetLight Data date ranges
Ask anything…
Governance / Audit log Last 24 hours
StreetLight Data List all StreetLight Data date ranges Emily Carter · Claude · 9:41 AM Done
StreetLight Data StreetLight Data osm IDS search Emily Carter · Claude · 9:41 AM Done
StreetLight Data List all StreetLight Data zone sets Emily Carter · Claude · 9:41 AM Done
StreetLight Data Create a StreetLight Data debug Megan Brooks · ChatGPT · 9:38 AM Done
StreetLight Data Create a StreetLight Data zone set Ryan Hayes · Cursor · 9:35 AM Done

How to connect StreetLight Data to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

StreetLight Data 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.

StreetLight Data MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

StreetLight Data 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. The plugin directory lives at chatgpt.com/plugins.

StreetLight Data 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.

StreetLight Data MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect StreetLight Data 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.

Connect StreetLight Data on Elaichi See pricing

What teams do with StreetLight Data through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in StreetLight Data is logged.

  • Planning

    Set up a corridor study in plain language

    Describe the corridor and the date range you care about, and the agent builds the zone set and launches the analysis in StreetLight Data for you.

  • Traffic engineering

    Pull segment counts for a signal review

    Ask for volumes on the segments around an intersection and get the segment counts and metrics read back, ready to drop into the review memo.

  • Consulting

    Check which client analyses are still running

    List the analyses for a project, see which are finished, and cancel one that was launched with the wrong settings before it uses more of the account.

  • GIS

    Find the right OSM IDs for a street

    Search StreetLight Data for the OSM IDs along a named road so a new zone set lands on the correct segments the first time.

  • Public works

    Tag analyses by grant or project

    Create a set of tags in one go and attach them to the analyses for a grant program, so every study can be found by project later.

  • Research

    Read finished metrics without opening the console

    Ask for the metrics of a completed analysis by name and get a plain summary of what the numbers say, including which date ranges were covered.

Try asking

  • “List every analysis still running for the Route 9 corridor study”
  • “Show segment counts from the Main Street analysis for last spring”
  • “Tag all analyses for the I-80 grant with the project name”

See all 24 StreetLight Data tools →

What connecting StreetLight Data gets you

6 screens from Elaichi, each doing one job for your StreetLight Data account.

Elaichi Agent

Ask Elaichi to work across your apps.

List every analysis still running for the Route 9 corridor study

Show segment counts from the Main Street analysis for last spring

Tag all analyses for the I-80 grant with the project name

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about traffic studies in plain language.

Zone sets, analyses and segment counts answered from live StreetLight Data records.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

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

AI apps

One endpoint reaches StreetLight Data from every client.

Claude, ChatGPT, Cursor and Microsoft Copilot share one governed endpoint, no SDK and no shared API key.

ElaichiTools
Tool Action Description
Create a StreetLight Data debug Create Echo a message to verify connectivity with StreetLight. Returns: message, status, openapi, info, servers, security, paths, components, x-readme, x-readme-fauxas.
Create a StreetLight Data zone set Create Create a new zone set in StreetLight InSight. Returns: name, status, uuid. Required: insight_login_email. zones and osm_ids are mutually exclusive.
List all StreetLight Data zone sets List Search StreetLight InSight zone sets. Returns zone sets including zone_set_uuid, zone_set_name, status, created_date, and zones. Max 100 results.
StreetLight Data osm IDS search Search Search StreetLight OSM segments by geometry. Returns an array of records, each containing osm_id, road_classification, and osm_segment_count. Required: geometry.
List all StreetLight Data date ranges List List available date ranges for a Streetlight travel mode and country. Returns default, supports, and AGPS-specific Network_Performance and Network_OD date ranges. Required: country, travel_mode_type.

Tool catalog

24 StreetLight Data tools, no code to write.

Zone sets, analyses, tags, metrics and segment counts, covered out of the box.

ElaichiToolboxes
Name Source template Tools Created

Planning toolbox

StreetLight Data · corridor studies and zone sets

 StreetLight Data starter 18 Mar 4, 2026

Traffic engineering toolbox

StreetLight Data · segment counts and metrics

 — 9 Mar 2, 2026

Consulting toolbox

StreetLight Data · client analyses and tags

 — 24 Feb 27, 2026

GIS toolbox

StreetLight Data · OSM IDs and geometries

 StreetLight Data starter 6 Feb 19, 2026

Public works toolbox

StreetLight Data · project tags and analysis status

 — 31 Jan 30, 2026

Research toolbox

StreetLight Data · date ranges and account usage

 — 12 Jan 22, 2026

Toolboxes

Every team gets its own StreetLight Data toolbox.

Planners, engineers and consultants each work from a toolbox scoped to their team.

ElaichiConnections
Connection Scope Status Access
ST

StreetLight Data (Long range planning)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
ST

StreetLight Data (Traffic engineering)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
ST

StreetLight Data (GIS)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
ST

StreetLight Data (Consulting)

Connected by Tyler Reed

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

StreetLight Data (Public works)

Connected by Ryan Hayes

 Personal • Active Not shared
ST

StreetLight Data (Research)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Shared connections

Teammates run analyses without seeing the key.

One person connects StreetLight Data, shares it, and nobody else handles the API key.

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]

 StreetLight Data Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

[email protected]

 StreetLight Data Zone sets Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

[email protected]

 StreetLight Data Zone sets List Toolbox

Audit log

Know who launched every StreetLight Data analysis.

When, who, what happened and which analysis, kept in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

StreetLight Data digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch zone sets

    StreetLight Data

    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 Jake Morgan

    Approve

  6. Post the digest

    StreetLight Data

    Queued

Automations

A schedule turns finished analyses into a digest.

Analyses are fetched, grouped, drafted, approved by a person, then tagged back in StreetLight Data.

StreetLight Data health

Refreshed 4 minutes ago · every 15 minutes · from the zone sets collection

Live

Zone sets

1,284 ↓ 12%

Analyses

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Zone sets created

Last 14 days

By team

Share of activity

Long range planning 34%

Traffic engineering 27%

GIS 21%

Consulting 18%

Collections and dashboards

StreetLight Data health, computed with no model.

Four metrics, 14 days of analyses created and a team breakdown, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for StreetLight Data

All three can connect StreetLight Data 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 StreetLight Data, 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 StreetLight Data tools Allow or restrict single StreetLight Data 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 StreetLight Data 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 Free for one person; $15 per user per month on Gold. 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.

StreetLight Data tools for your AI agents

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

More from the catalog

Browse all 650+ connectors →

Questions, answered

How do I connect StreetLight Data to Claude?

Connect StreetLight Data in Elaichi by pasting in your StreetLight Data API key. Then in Claude, open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, and the whole thing takes a few minutes.

Does StreetLight Data work with ChatGPT and Cursor as well as Claude?

Yes. Once StreetLight Data is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect StreetLight Data once and every client picks it up.

What can an AI agent actually do with my StreetLight Data account?

An agent connected to StreetLight Data can create zone sets, search OSM IDs, launch, update or cancel analyses, and list what is running or finished. It can read the metrics, geometries and segment counts from completed analyses, check available date ranges and account usage, and create or remove tags to keep projects organized.

Does connecting StreetLight Data give the AI access to everything in the account?

No. Every call into StreetLight Data runs under the access of the person who signed in to Elaichi, so the AI can only see the analyses, zone sets and metrics that person could already see. Elaichi can narrow that access further with restrictions, and it can never widen it beyond what StreetLight Data itself allows.

Can my team share one StreetLight Data connection?

Yes. One person connects StreetLight Data in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who launched or changed each StreetLight Data analysis.

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

Yes. Restrictions in Elaichi apply per action, so you can allow reading StreetLight Data metrics and segment counts while restricting the actions that delete analyses, cancel them or remove tags. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.

What happens to a StreetLight Data connection when someone leaves?

Offboarding a person in Elaichi ends their access to StreetLight Data through every client at once. A shared StreetLight Data connection keeps working for everyone else on the team. If you ever want to remove StreetLight Data entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

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

Yes. StreetLight Data 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, Microsoft Copilot, 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 StreetLight Data?

Yes. Both let Claude, ChatGPT or Cursor use StreetLight Data. 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 StreetLight Data call.

How is Elaichi different from Composio for StreetLight Data?

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 StreetLight Data: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put StreetLight Data in front of your team

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

Connect StreetLight Data Talk to us

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot