AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
Connect Remote server
claude mcp add --transport http mcp https://atlasemoji.com/api/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"mcp": {
"url": "https://atlasemoji.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"mcp": {
"type": "http",
"url": "https://atlasemoji.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://atlasemoji.com/api/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 19 found in our last check
list_capabilitiesDiscover how Atlasemoji supports Atlas DataSynch, GIS, geofencing, CRM, inventory, Atlas Intercept, handheld scanning, APIs, integrations, routing, storytelling, learning, and partner workflows. Returns the related public APIs, partner access paths, production capabilities, curr…
get_atlas_profileReturn the Atlasemoji profile represented by the current authenticated MCP credentials so ChatGPT can identify the connected Atlas account. This operation is read-only and never accepts a user or account identifier from the model.
verify_atlas_agentComplete proof of life for an already configured Atlas Agent MCP connection. The authenticated MCP principal must be authorized for the requested company and for this tool. Atlas verifies that the connection belongs to the requested Agent and records the current Manifest revisio…
get_datasynch_run_statusSupport Atlas DataSynch operations by retrieving recent processing and workflow status for an authorized company, workspace, or manifest. Agents can use the result to explain integration progress, identify stalled activity, and understand the current state of EDI, EDIFACT, cXML,…
get_failed_runsHelp support, implementation, operations, and partner agents investigate failed Atlas DataSynch activity across APIs, files, EDI, EDIFACT, cXML, mappings, inventory, telemetry, locations, and downstream workflows. Returns authorized failure and exception context without changing…
validate_manifest_schemaPrepare geographic and operational manifest data for Atlasemoji use. Checks the supplied manifest structure, durable identity, locations, addresses, and coordinates before the data is used with workspaces, routes, storytelling, geofencing, DataSynch, inventory, CRM, or other Atl…
get_manifest_summaryRetrieve authorized Atlasemoji manifest context so an agent can understand the places, routes, boundaries, layers, records, workflow purpose, workspace relationship, and operational context represented by the manifest.
validate_coordinatesPrepare latitude and longitude values for Atlasemoji maps, routes, geofences, telemetry, mobile events, customer locations, assets, vessels, aircraft, storytelling, and operational workflows by checking accepted geographic ranges and returning normalized coordinates.
validate_geojsonPrepare GeoJSON features, collections, points, lines, polygons, and geometry collections for Atlasemoji maps, routes, service areas, stories, manifests, geofences, learning exercises, APIs, and location-aware workflows by checking their basic structure.
detect_location_columnsIdentify address, city, state, province, region, postal code, latitude, and longitude fields in supplied business or operational records so they can be connected to Atlasemoji locations, customer sites, facilities, routes, territories, inventory, telemetry, geofences, and DataSy…
preview_geofencePrepare a radius-based geofence for an Atlasemoji location-aware workflow. Helps agents and users evaluate the proposed center, radius, coverage area, label, and tenant context before using production geofencing for movement, scans, arrivals, exits, dwell, proximity, telemetry,…
check_point_in_geofenceEvaluate whether a vehicle, shipment, mobile device, scan, person-authorized location event, asset, aircraft, vessel, or other coordinate is inside a proposed radius boundary used in Atlasemoji geofencing and event-driven workflows.
detect_file_schemaAnalyze a bounded preview of CSV, spreadsheet, JSON, EDI-normalized, EDIFACT-normalized, cXML-derived, inventory, telemetry, CRM, item, location, shipment, or partner records to identify their structure and determine how they may fit Atlas DataSynch workflows.
preview_datasynch_rowsReview a bounded preview of partner, customer, ERP, WMS, TMS, CRM, inventory, telemetry, location, API, spreadsheet, EDI-normalized, EDIFACT-normalized, or cXML-derived records in the context of an authorized Atlasemoji company, workspace, or manifest.
suggest_field_mappingSuggest an initial bridge between external partner, API, ERP, WMS, TMS, CRM, file, EDI-normalized, EDIFACT-normalized, cXML-derived, inventory, telemetry, item, and location fields and common Atlasemoji data targets. Intended to support integration design and human-reviewed mapp…
summarize_workspace_activitySummarize recent authorized activity across an Atlasemoji company, workspace, or manifest so agents can explain what has happened across DataSynch, locations, manifests, integrations, telemetry, exceptions, inventory, partner workflows, and operational records.
wanderloop.research_placeAssemble a cited, geographically grounded Wanderloop research package for a location. Queries Atlasemoji-approved historical, archival, academic, environmental, wildlife, and place-record providers through the same provider registry used by the Wanderloop application. Returns ev…
wanderloop.get_manifestRetrieve a previously saved Wanderloop topic or place-research manifest by manifest ID, including its normalized provider evidence, statuses, map data, citations, and source links when available.
wanderloop.list_provider_capabilitiesList every registered Wanderloop source integration without dropping unavailable or unconfigured providers. Returns provider identity, current topic assignment, execution mode, and required environment configuration so an agent can understand which historical, academic, archival…
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Atlasemoji partner or client bearer token. Enter the complete value: Bearer YOUR_TOKEN |
Details
| Endpoint | https://atlasemoji.com/api/mcp (Streamable HTTP) |
| First published | 11 Jul 2026 |
| Last updated | 11 Jul 2026 |
| Registry name | com.atlasemoji/mcp |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
