Atlasemoji for AI agents

Turn places, movement, events, and business records into reusable geography and actionable workflows.

Atlasemoji gives people, applications, clients, partners, developers, and AI agents access to AtlasEvo Workspaces, GIS, geofencing, Atlas DataSynch, CRM, inventory, operational response, handheld scanning, APIs, integrations, routing, storytelling, learning, and location-aware workflows.

How Atlasemoji MCP is organized

Atlasemoji solution

  → business outcome

  → public API / partner API / MCP access

  → current callable MCP tools

  → access requirements and next action

MCP tools support Atlasemoji solutions. Individual tools are implementation access points and do not redefine or limit what the Atlasemoji platform provides.

AtlasEvo + MCP

Configure the project once, then let approved agents return to the same context

AtlasEvo holds the project structure around sources, datasets, layers, research stations, observations, provenance, mappings, and downstream connections. MCP is the bounded agent-access layer around capabilities that are actually registered and granted to a client credential.

1. People configure the integration

Build the Workspace, identify the source, map fields or standards, configure station and connection paths, and decide what can leave the project. Research REST and DataSynch remain the programmatic ingestion and movement paths where they are enabled.

2. MCP gets a defined capability set

An agent credential receives only the tools, scopes, tenant access, and environment needed for its job. The current tool catalog below is the source of truth for what is callable through MCP in this release.

3. The caller controls cadence

An external agent, scheduler, or application can return hourly, daily, or on demand. MCP controls which Atlas data and capabilities the credential can access; the calling system controls when it asks.

AtlasEvo Workspace GuideStandards & mapping guide

Agent access policy

Atlasemoji grants capabilities, not blanket platform access

Atlasemoji treats an AI agent as a bounded operator. An agent can be given access to the specific data, tools, application area, tenant, environment, and actions needed for an approved task without receiving general authority across the platform.

Instructions given to an AI model help guide its behavior, but Atlasemoji does not rely on model instructions alone as an authorization boundary. Access to consequential operations is controlled by Atlasemoji credentials, tenant context, available tools, policy, and approval requirements.

Gate 1

Identity

Who is acting, on whose behalf, and through which approved agent or application session?

Gate 2

Scope

Which tenant, Atlasemoji solution, functional area, resources, tools, and environment are needed for the task?

Gate 3

Policy

Is this specific operation permitted for this identity, tenant, capability, resource, and environment?

Gate 4

Consequence

Does the requested action only observe or propose, or can it change, transmit, execute, or promote production activity?

A bounded request

Atlasemoji can evaluate agent access across several dimensions rather than treating access as a single yes-or-no permission.

WHO

  → WHICH TENANT

  → WHICH APPLICATION

  → WHICH FUNCTION

  → WHICH RESOURCE

  → WHAT ACTION

  → WHICH ENVIRONMENT

Tenant isolation is therefore one boundary in a broader capability model. An agent can be inside an approved tenant and still be limited to a specific application, function, resource, action, or environment.

Reasoning authority is not execution authority

Atlasemoji separates operations that observe, analyze, or propose from operations that write, execute, transmit, or promote. A model may be able to recommend an action without being granted the capability to perform that action.

Observe

  → Reason

  → Propose

  → Authorize

  → Execute

Higher-consequence operations can require additional policy checks, credentials, approval, or promotion gates even when an agent has already been approved for lower-risk work.

Capability vocabulary

Design agents around the smallest useful capability

The examples below illustrate how Atlasemoji can describe agent authority independently of a page or user-interface route. They are policy examples, not a list of currently callable MCP tool names. Current callable tools remain listed by solution below.

datasynch.integration.trace.read

datasynch.integration.mapping.propose

datasynch.integration.mapping.write

datasynch.integration.production.promote



b2btest.scenario.execute

A developer should not assume that access to one capability implies access to another. Read, proposal, write, execution, and production promotion can be independently scoped.

Build Atlasemoji-compatible agents for rational scope

Agent integrations should request only the capabilities necessary for a defined task. Scope should be established before access is granted, and broader authority should require a separate policy or approval decision rather than being assumed from an existing session.

Where practical, Atlasemoji can make higher-risk operations unavailable to an agent rather than merely instructing the agent not to use them. This allows external agents to work with useful Atlasemoji capabilities while preserving clear boundaries around tenant data and consequential actions.

Atlasemoji solutions

What Atlasemoji helps people, businesses, developers, and agents accomplish

Data integration and operations

Atlas DataSynch

production platform

Map-aware operating hub for locations, partner data, Xref, telemetry, inventory, exceptions, and normalized workflow records. Atlas DataSynch connects EDI, EDIFACT, cXML, APIs, spreadsheets, files, cloud applications, business systems, telemetry, inventory, customer data, and geographic context to reusable operational workflows.

Who uses it

  • • Integration and implementation teams
  • • Supply-chain and operations teams
  • • EDI, B2B, API, and iPaaS partners
  • • Customer support and managed-service teams
  • • Developers and AI agents working with approved tenant data

Business outcomes

  • • Connect partner and business-system data to Atlasemoji
  • • Normalize records across files, APIs, EDI, EDIFACT, cXML, and applications
  • • Manage Xref relationships and partner-specific identifiers
  • • Connect locations, inventory, telemetry, CRM, items, and operational events
  • • Track processing, exceptions, activity, and downstream workflow status

Production capabilities

  • • Locations, items, inventory, CRM, telemetry, and operational master data
  • • EDI, EDIFACT, cXML, spreadsheets, files, JSON, and API intake
  • • Schema mapping, Xref, normalization, parsing, and workflow preparation
  • • Processing runs, exceptions, dispatch, telemetry, and operational ledgers
  • • Connectors, webhooks, cloud services, applications, and partner systems

Learning opportunities

  • • Understand how business data becomes usable geographic and operational context
  • • Learn schema mapping, normalization, Xref, and integration workflow concepts
  • • Explore how agents can support implementation, support, and operations teams

Current MCP tools

  • detect_file_schema
  • preview_datasynch_rows
  • suggest_field_mapping
  • get_datasynch_run_status
  • get_failed_runs
  • summarize_workspace_activity

Public APIs

  • /api/datasynch/openapi
  • /api/datasynch/openapi.yaml

Partner APIs and access

  • • Tenant-secured master-table and workflow APIs
  • • Integration profile and connector APIs
  • • Execution, processing, telemetry, exception, and dispatch APIs
  • • Partner-specific integration and onboarding APIs

Access requirements

  • • Public API documentation is available
  • • MCP preparation and diagnostic tools require configured access
  • • Production tenant data and workflow operations require approved client or partner authorization

Next action: Review the public DataSynch API documentation or contact Atlasemoji to establish client, partner, implementation, or sandbox access.

GIS and spatial data

Locations & GIS Foundation

production platform

Load stores, distribution centers, yards, campuses, service areas, routes, customer sites, facilities, addresses, coordinates, observations, boundaries, and GeoJSON, then make that geography reusable across Atlasemoji workflows.

Who uses it

  • • Operations and planning teams
  • • GIS and mapping users
  • • Developers and integration teams
  • • Field, sales, service, and customer-success teams
  • • Educators, researchers, travelers, and AI agents

Business outcomes

  • • Create durable, reusable geographic objects
  • • Connect business records to places, routes, boundaries, and coordinates
  • • Use geography across DataSynch, CRM, inventory, geofencing, stories, and APIs
  • • Give agents structured spatial context instead of static screenshots

Production capabilities

  • • Locations, addresses, coordinates, places, routes, service areas, and boundaries
  • • GeoJSON features, collections, points, lines, polygons, and layers
  • • Workspaces and manifests for reusable geographic context
  • • Geocoding, map visualization, imports, exports, and geographic workflows

Learning opportunities

  • • Learn coordinates, GeoJSON, routes, polygons, and map layers
  • • Understand how geography connects to business and operational records
  • • Use Atlasemoji examples and quick starts for spatial reasoning

Current MCP tools

  • validate_coordinates
  • validate_geojson
  • detect_location_columns
  • validate_manifest_schema
  • get_manifest_summary
  • summarize_workspace_activity

Public APIs

  • /api/openapi
  • /api/openapi.yaml

Partner APIs and access

  • • Tenant-secured locations and manifest APIs
  • • Workspace, import, export, route, and layer APIs
  • • Partner-specific geographic workflow APIs

Access requirements

  • • Public documentation and selected learning materials are available
  • • MCP validation and preparation tools require configured access
  • • Persistent tenant geography requires account and tenant authorization

Next action: Use the public developer documentation, review learning resources, or contact Atlasemoji for workspace, client, partner, or sandbox access.

Location-aware events

Geofencing

partner access

Create radius or polygon boundaries that turn movement, scans, arrivals, exits, dwell time, proximity, mobile updates, telemetry, and asset locations into operational events.

Who uses it

  • • Logistics and transportation teams
  • • Field service and mobile-workforce teams
  • • Retail, distribution, facilities, and yard operations
  • • Developers, partners, and AI agents building event-driven workflows

Business outcomes

  • • Create fixed and dynamic geographic boundaries
  • • Evaluate vehicles, shipments, devices, scans, people-authorized events, and assets
  • • Detect arrivals, exits, dwell, proximity, and boundary crossings
  • • Connect events to Atlas Intercept, alerts, exceptions, and downstream workflows

Production capabilities

  • • Radius and polygon geofences
  • • Fixed and dynamic boundaries
  • • Movement, proximity, arrival, exit, dwell, scan, and telemetry events
  • • Location-aware alerting and operational workflow integration

Learning opportunities

  • • Learn how point-in-boundary logic works
  • • Explore radius, polygon, movement, and proximity concepts
  • • Discuss isolated demonstrations and educational geofence environments

Current MCP tools

  • preview_geofence
  • check_point_in_geofence
  • validate_coordinates
  • validate_geojson

Public APIs

  • /api/datasynch/geofences
  • /api/atlasemoji/geofence-trial

Partner APIs and access

  • • Tenant-secured production geofence APIs
  • • Geofence event and telemetry APIs
  • • Alert, exception, webhook, and downstream-action integrations

Access requirements

  • • The geofence trial has its own public consent-based workflow
  • • MCP planning and evaluation tools require configured access
  • • Production tracking, events, and downstream actions require approved tenant access

Next action: Review the geofence trial and help materials or contact Atlasemoji for production, partner, developer, or sandbox access.

Customer and territory operations

CRM

production platform

Connect accounts, contacts, partners, campaigns, field coverage, territories, support activity, cases, communications, and customer relationships to the places where work happens.

Who uses it

  • • Sales and marketing teams
  • • Customer success and support teams
  • • Partner and channel teams
  • • Field operations and territory managers
  • • Agents supporting customer and account workflows

Business outcomes

  • • Connect accounts and contacts to customer geography
  • • Map territories, field coverage, campaigns, and partner relationships
  • • Connect support, billing, onboarding, and sales activity to places
  • • Use DataSynch to prepare and integrate CRM records

Production capabilities

  • • Accounts, contacts, cases, activities, communications, and handoffs
  • • Territory and customer-location mapping
  • • Marketing, sales, onboarding, billing, and support workflows
  • • DataSynch preparation and integration for CRM records

Learning opportunities

  • • Learn how customer data connects to geographic context
  • • Explore territory, field coverage, and location-aware CRM concepts

Current MCP tools

  • detect_file_schema
  • preview_datasynch_rows
  • suggest_field_mapping
  • detect_location_columns
  • summarize_workspace_activity

Public APIs

No public API path is advertised for this solution. Access may be tenant-secured or relationship-based.

Partner APIs and access

  • • Tenant-secured CRM account, contact, case, activity, and communication APIs
  • • CRM intake, territory, partner, and support integrations

Access requirements

  • • CRM records require approved tenant access
  • • MCP currently supports related data preparation and authorized activity summaries

Next action: Contact Atlasemoji to discuss CRM, territory, customer-location, partner, or DataSynch integration use cases.

Supply chain and asset visibility

Inventory & Items

production platform

Track products, parts, consignment stock, truck inventory, store inventory, warehouse inventory, high-value items, and operational assets by location or movement.

Who uses it

  • • Retail and distribution teams
  • • Warehouse and transportation teams
  • • Field service and truck-inventory teams
  • • Manufacturing, consignment, and asset-management teams

Business outcomes

  • • Connect items, inventory, and assets to locations
  • • Support store, warehouse, vehicle, field, and consignment visibility
  • • Connect inventory movement to telemetry, geofences, scans, and operational events
  • • Use DataSynch to integrate item and inventory records

Production capabilities

  • • Items, SKUs, parts, products, quantities, and master data
  • • Store, warehouse, truck, field, and consignment inventory
  • • Location-aware inventory and asset movement
  • • DataSynch integration with external inventory systems

Learning opportunities

  • • Learn how inventory records connect to geography and movement
  • • Explore supply-chain data preparation and location-aware operations

Current MCP tools

  • detect_file_schema
  • preview_datasynch_rows
  • suggest_field_mapping
  • summarize_workspace_activity

Public APIs

No public API path is advertised for this solution. Access may be tenant-secured or relationship-based.

Partner APIs and access

  • • Tenant-secured item and inventory APIs
  • • Inventory ingestion, movement, location, and operational integrations

Access requirements

  • • Production item and inventory data requires approved tenant access
  • • MCP currently supports related data preparation and activity use cases

Next action: Contact Atlasemoji to discuss inventory, item, asset, consignment, vehicle, store, or warehouse workflows.

Operational events and response

Atlas Intercept

partner access

Route alerts, webhooks, exceptions, notifications, and downstream actions when geographic, integration, telemetry, inventory, scan, customer, or operational events require a response.

Who uses it

  • • Operations and support teams
  • • Integration and managed-service teams
  • • Logistics, field, and exception-management teams
  • • Partners building event-driven workflows

Business outcomes

  • • Identify operational and integration exceptions
  • • Connect events to alerts and downstream business actions
  • • Support controlled escalation and response workflows
  • • Separate business exceptions from system notices and delivery failures

Production capabilities

  • • Business exceptions and system notices
  • • Alerts, webhooks, Slack, email, and downstream integrations
  • • Retry, delivery, dispatch, and response ledgers
  • • Geofence, telemetry, DataSynch, and operational event handling

Learning opportunities

  • • Learn event-driven workflow and exception-management concepts
  • • Explore how spatial and integration events can trigger business responses

Current MCP tools

  • get_failed_runs
  • summarize_workspace_activity
  • check_point_in_geofence

Public APIs

No public API path is advertised for this solution. Access may be tenant-secured or relationship-based.

Partner APIs and access

  • • Exception, alert, dispatch, webhook, and notification APIs
  • • Partner-specific event and downstream-action integrations

Access requirements

  • • Diagnostic MCP tools require approved access
  • • Production dispatch and downstream actions require tenant authorization and appropriate approval controls

Next action: Contact Atlasemoji to define event, exception, alert, webhook, or downstream-action requirements.

Mobile and field operations

Handheld Scanner

production platform

Use Android and mobile scanning for pick-pack, scan-n-pack, proof capture, inventory activity, proximity checks, field events, and location-aware operational workflows.

Who uses it

  • • Warehouse and distribution teams
  • • Retail and store operations
  • • Field service and mobile workforces
  • • Delivery, inventory, and proof-capture workflows

Business outcomes

  • • Capture barcode and mobile events
  • • Connect scans to items, inventory, locations, and workflows
  • • Support pick-pack, scan-n-pack, proof, and field-event operations
  • • Combine scans with proximity, geofencing, and DataSynch

Production capabilities

  • • Android and mobile scanning
  • • Barcode, inventory, item, and proof events
  • • Proximity and location-aware field workflows
  • • Integration with DataSynch, inventory, geofencing, and Atlas Intercept

Learning opportunities

  • • Learn how mobile scans become operational events
  • • Explore connections between devices, inventory, geography, and workflows

Current MCP tools

  • validate_coordinates
  • check_point_in_geofence
  • summarize_workspace_activity

Public APIs

No public API path is advertised for this solution. Access may be tenant-secured or relationship-based.

Partner APIs and access

  • • Mobile device, scan, inventory, location-event, and operational workflow APIs

Access requirements

  • • Production scanner and mobile workflows require approved device and tenant configuration
  • • Related MCP access can be defined for approved implementations

Next action: Contact Atlasemoji to discuss handheld, Android, warehouse, retail, delivery, or field-workflow requirements.

Developer and partner integration

API & Integration Hub

partner access

Provide RESTful access for Google Cloud, webhooks, EDI, EDIFACT, cXML, spreadsheets, files, applications, cloud storage, business systems, connectors, and partner workflows.

Who uses it

  • • Developers and platform teams
  • • Integration, EDI, iPaaS, and B2B partners
  • • Application, cloud, and data teams
  • • AI agents with approved business access

Business outcomes

  • • Connect applications and business systems to Atlasemoji
  • • Use REST APIs, OpenAPI, webhooks, and managed integrations
  • • Support EDI, EDIFACT, cXML, files, spreadsheets, and JSON
  • • Create approved client, partner, and agent workflows

Production capabilities

  • • REST APIs and OpenAPI documents
  • • Webhooks and downstream integrations
  • • Google Cloud, storage, files, applications, EDI, EDIFACT, and cXML
  • • Connector and partner workflow orchestration
  • • Scoped client and agent access

Learning opportunities

  • • Learn REST, OpenAPI, webhooks, MCP, and integration concepts
  • • Explore how agents can use approved APIs and partner workflows

Current MCP tools

  • list_capabilities
  • detect_file_schema
  • preview_datasynch_rows
  • suggest_field_mapping
  • get_datasynch_run_status
  • get_failed_runs

Public APIs

  • /api/openapi
  • /api/openapi.yaml
  • /api/datasynch/openapi
  • /api/datasynch/openapi.yaml

Partner APIs and access

  • • Tenant-secured Atlasemoji and DataSynch APIs
  • • Connector, credential, execution, webhook, and integration APIs
  • • Partner-specific API products and scoped MCP access

Access requirements

  • • Public API documentation is available
  • • Operational and tenant APIs require approved credentials and scopes
  • • Partner MCP and integration access is configured per relationship

Next action: Review the public API documentation or contact Atlasemoji to establish developer, client, partner, connector, or MCP access.

Routes and movement

Travel & Routing

public api

Build route visuals for field movement, customer visits, trips, vessels, aircraft, deliveries, waypoints, travel manifests, and operational planning.

Who uses it

  • • Travelers and trip planners
  • • Field, sales, service, and delivery teams
  • • Logistics, vessel, and aircraft users
  • • Developers, educators, and AI agents

Business outcomes

  • • Create and visualize routes and waypoints
  • • Build travel and movement context
  • • Geocode destinations and locations
  • • Support weather-aware and operational planning
  • • Give agents useful route and travel information

Production capabilities

  • • Routes, waypoints, trips, and travel manifests
  • • Geocoding, weather context, route visuals, and imports
  • • Field, customer, delivery, vessel, aircraft, and operational planning
  • • Reusable route and geographic content

Learning opportunities

  • • Learn routes, coordinates, waypoints, GeoJSON, and movement
  • • Use travel and routing examples for programming and agent development

Current MCP tools

  • validate_coordinates
  • validate_geojson
  • validate_manifest_schema
  • get_manifest_summary

Public APIs

  • /api/travelers/route
  • /api/travelers/geocode
  • /api/travelers/weather
  • /api/travelers/parse
  • /api/travelers/import/share
  • /api/route-polyline
  • /api/route-skeleton

Partner APIs and access

  • • Approved persistent trip, route, manifest, and operational movement APIs

Access requirements

  • • Selected Travelers APIs are public-facing
  • • Persistent user-owned or tenant-owned routes require appropriate authorization

Next action: Review Travelers and routing resources or contact Atlasemoji for persistent, partner, educational, or operational access.

Education, enablement, and community

Learning & Help

learning resource

Provide quick starts, field guides, help files, API explainers, implementation notes, examples, and relationship-based sandboxes for business users, technical users, developers, educators, students, and AI agents.

Who uses it

  • • Students and educators
  • • Developers and AI learners
  • • Business and technical users
  • • Clients, partners, implementation teams, and community users

Business outcomes

  • • Make GIS, GeoJSON, maps, routes, geofences, APIs, and integrations easier to understand
  • • Help people connect AI agents to useful real-world capabilities
  • • Support implementation, onboarding, development, and experimentation
  • • Create paths from learning to client, partner, community, and commercial relationships

Production capabilities

  • • Learning pages, help content, quick starts, field guides, and API documentation
  • • Implementation and partner enablement
  • • Approved sandbox and demonstration environments

Learning opportunities

  • • GIS and spatial reasoning
  • • GeoJSON, coordinates, routes, and boundaries
  • • Geofencing and event-driven workflows
  • • APIs, MCP, EDI, EDIFACT, cXML, files, and integrations
  • • DataSynch, inventory, CRM, telemetry, and operational workflows

Current MCP tools

  • list_capabilities
  • validate_coordinates
  • validate_geojson
  • validate_manifest_schema
  • check_point_in_geofence
  • detect_location_columns
  • detect_file_schema
  • suggest_field_mapping

Public APIs

No public API path is advertised for this solution. Access may be tenant-secured or relationship-based.

Partner APIs and access

  • • Relationship-based educational, demonstration, developer, and partner sandbox access

Access requirements

  • • Public learning and documentation resources are available
  • • MCP access requires configured credentials in the current release
  • • Sandboxes and expanded learning environments are available by relationship and request

Next action: Review Atlasemoji learning resources or contact Atlasemoji to discuss educational, developer, classroom, community, client, or partner access.

Current MCP access layer

Callable tools supporting the Atlasemoji solutions above

These tools are not standalone products. Each is an access point supporting one or more Atlasemoji solutions, APIs, implementation workflows, learning experiences, or approved tenant operations.

Supports Atlasemoji Platform

Discover Atlasemoji Solutions and Agent Capabilities

list_capabilities

Discover 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, current MCP tools, learning opportunities, and access requirements for each solution.

Access classification: mcp available

Supports AtlasAgents

Verify an Atlas Agent Connection

verify_atlas_agent

Complete 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 revision before returning a sanitized Connection Card.

Access classification: partner access

Supports Atlas DataSynch

Review Atlas DataSynch Workflow Status

get_datasynch_run_status

Support 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, API, file, telemetry, inventory, location, and partner-data workflows.

Access classification: partner access

Supports Atlas DataSynch / Atlas Intercept

Review DataSynch Failures and Exceptions

get_failed_runs

Help 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 workflow records.

Access classification: partner access

Supports Locations & GIS Foundation / Atlas DataSynch

Prepare a Manifest for Atlasemoji Workflows

validate_manifest_schema

Prepare 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 Atlasemoji workflows.

Access classification: mcp available

Supports Locations & GIS Foundation / Atlas DataSynch

Understand an Atlasemoji Manifest

get_manifest_summary

Retrieve 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.

Access classification: partner access

Supports Locations & GIS Foundation

Prepare Coordinates for Atlasemoji GIS Workflows

validate_coordinates

Prepare 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.

Access classification: mcp available

Supports Locations & GIS Foundation / Learning & Help

Prepare GeoJSON for Atlasemoji

validate_geojson

Prepare 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.

Access classification: mcp available

Supports Locations & GIS Foundation / Atlas DataSynch

Identify Location Data for Atlasemoji

detect_location_columns

Identify 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 DataSynch workflows.

Access classification: mcp available

Supports Geofencing

Prepare an Atlasemoji Geofence

preview_geofence

Prepare 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, alerts, or downstream actions.

Access classification: mcp available

Supports Geofencing / Atlas Intercept

Evaluate a Location Against a Geofence

check_point_in_geofence

Evaluate 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.

Access classification: mcp available

Supports Atlas DataSynch / API & Integration Hub

Prepare Partner and Operational Data for Atlas DataSynch

detect_file_schema

Analyze 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.

Access classification: mcp available

Supports Atlas DataSynch

Preview Data for an Atlas DataSynch Workflow

preview_datasynch_rows

Review 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.

Access classification: mcp available

Supports Atlas DataSynch / API & Integration Hub

Prepare a DataSynch Field Mapping

suggest_field_mapping

Suggest 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 mapping preparation.

Access classification: mcp available

Supports Atlas DataSynch / Locations & GIS Foundation / Atlas Intercept

Summarize Atlasemoji Workspace Activity

summarize_workspace_activity

Summarize 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.

Access classification: partner access

Learning, demonstration, developer, client, and partner sandboxes

Atlasemoji can provide isolated learning, demonstration, developer, classroom, client, and partner sandboxes for approved GIS, GeoJSON, routing, geofencing, telemetry, DataSynch, integration, and agent-development use cases. Access, data isolation, rate limits, available capabilities, and permitted operations are defined for each relationship.

Discuss Atlasemoji access

MCP endpoint

https://atlasemoji.com/api/mcp

Transport: Streamable HTTP. Current MCP access requires an Atlasemoji-issued credential. Public APIs and documentation are listed by solution above.