Analytics
StreetLight Data
Connect StreetLight Data once and hand every teammate a governed MCP endpoint with 24 tools ready to call from Claude, ChatGPT, Cursor, or any MCP client, inside the same permissions they already have, with every call checked and logged.
Automations & dashboards
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 ship on the Black plan.
Automations
Put StreetLight Data work on a schedule.
A trigger starts a sequence of steps: call a StreetLight Data tool, transform the result, branch, wait, and ask a person when it matters.
StreetLight Data digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch analysises
StreetLight Data
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
StreetLight Data
Queued
Collections and dashboards
Report on StreetLight Data without asking.
Collections hold your own data, written by an automation and read by a dashboard that refreshes on a schedule.
StreetLight Data health
Refreshed 4 minutes ago · every 15 minutes · from the analysises collection
Analysises
1,284 ↓ 12%
Tags
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Analysises created
Last 14 days
By workspace
Share of activity
Engineering 34%
Product 27%
Support 21%
Sales 18%
AI tools
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.
create_a_streetlightdata_debug
Echo a message to verify connectivity with StreetLight. Returns: message, status, openapi, info, servers, security, paths, components, x-readme, x-readme-fauxas.
create_a_streetlightdata_zone_set
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_streetlightdata_zone_sets
Search StreetLight InSight zone sets. Returns zone sets including zone_set_uuid, zone_set_name, status, created_date, and zones. Max 100 results.
streetlightdata_osm_ids_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_streetlightdata_date_ranges
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.
list_all_streetlightdata_tags
List available tags in your StreetLight organization. Returns: analysis_num, created_by, created_date, tag_name.
create_a_streetlightdata_tag
Create a new StreetLight tag to organize analyses. Returns: tag_name, status, openapi, info, servers, security, paths, components, x-readme, x-readme-fauxas. Required: insight_login_email, tag_name.
delete_a_streetlightdata_tag_by_id
Delete a tag in StreetLight. Returns: status, openapi, info, servers, security, paths, components, x-readme, x-readme-fauxas. Required: insight_login_email, id.
streetlightdata_tags_bulk_create
Add one or more tags to one or more StreetLight analyses. Returns: status, openapi, info, servers, security, paths, components, x-readme, x-readme-fauxas. Required: insight_login_email, tags, analyses.
streetlightdata_tags_bulk_delete
Remove one or more tags from one or more StreetLight analyses. Returns: status, openapi, info, servers, security, paths, components, x-readme, x-readme-fauxas. Required: insight_login_email, tags, analyses.
create_a_streetlightdata_analysis
Create and run a new StreetLight analysis. Returns the created analysis name, status, and UUID. Required: insight_login_email, analysis_type, travel_mode_type, oz_sets.
streetlightdata_analyses_search
Search StreetLight analyses by date range, name, type, travel mode, tags, queue status, or API key. Returns: analysis_name, analysis_type, analysis_uuid, created_by_uuid, created_date, data_period, number_of_zones, tags, travel_mode.
list_all_streetlightdata_analyses
Check the status and included metrics for one or more StreetLight analyses. Returns: name, status. Required: analyses.
update_a_streetlightdata_analysis_by_id
Update the name or description of a StreetLight analysis by id. Returns: analysis_name, analysis_uuid, status, openapi, info, servers, security, paths, components, x-readme, x-readme-fauxas. Required: id, name.
delete_a_streetlightdata_analysis_by_id
Delete a StreetLight analysis by id. Returns: analysis_name, analysis_uuid, status, openapi, info, servers, security, paths, components, x-readme, x-readme-fauxas. Required: id.
create_a_streetlightdata_analysis_cancellation
Cancel a StreetLight analysis by its analysis name. Returns: analysis_name, analysis_uuid, status, openapi, info, servers, security, paths, components, x-readme, x-readme-fauxas. Required: cancel_id.
list_all_streetlightdata_analysis_metrics_by_uuid
Download StreetLight analysis metrics by UUID. Returns the metrics file in the `content` field as a CSV or zip payload with metric-specific columns. Required: uuid_id, metric.
list_all_streetlightdata_analysis_metrics_by_name
Download metrics for a StreetLight analysis by name. Returns a CSV-formatted metrics file with columns that vary by the requested metric. Required: name_id, metric.
list_all_streetlightdata_satc_metrics
Get StreetLight traffic metrics for segments within a defined geometry. Returns an array of metric rows, each row an array of values ordered by the requested columns (segment_id followed by the requested metric fields). Required: geometry, country, mode, fields, day_part, day_type, and direction. One of date or date_range is required, but not both. Queries count against your segment quota; do not…
list_all_streetlightdata_satc_metric_pages
List metric rows from a previous StreetLight SATC metrics query by paging id. Returns an array of metric rows, each row an ordered array of numeric values matching the requested columns. Required: paging_id.
list_all_streetlightdata_satc_geometries
List StreetLight segment geometries in GeoJSON format. Returns an array of geometry records, each containing a segment_id and its GeoJSON LineString. Required: mode, geometry, country. Max 10,000 results per page.
list_all_streetlightdata_satc_geometry_pages
List the next page of segment geometries for a StreetLight geometry query. Returns segment_id and line_geometry for each record. Required: paging_id. Max 10000 per page.
list_all_streetlightdata_satc_segment_counts
Count segments in a StreetLight geometry. Returns the matching segment count. Required: geometry, country, mode. Result is never lower than the metrics endpoint count but may be higher.
list_all_streetlightdata_satc_usage
List previous StreetLight SATC usage requests. Returns: status, created_date, type, job_id, billed_fields_queried, segments_queried, is_billable.
No tools match your search.
How it works
From StreetLight Data account to governed MCP endpoint
Connect
Link a StreetLight Data account through Elaichi's hosted connect flow. Credentials are vaulted, so nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which StreetLight Data tools are exposed, rename them, or freeze arguments.
Authorize
Point Claude, ChatGPT, Cursor, or any MCP client at the one Elaichi endpoint and sign in with OAuth, governed by roles, restrictions, and audit logs.
Put your agents to work in the tools you already use
Start a 14-day Gold trial. Connect a product, curate a toolbox, and paste a governed MCP endpoint into Claude, ChatGPT, or Cursor in minutes.