Atlasemoji documentation

Atlasemoji MCP tools and access model

The current Atlasemoji MCP release provides authenticated, read-only, non-destructive tools for capability discovery, GIS and GeoJSON validation, geofence calculations, manifest inspection, DataSynch preparation, and operational diagnostics.

Endpoint

https://atlasemoji.com/api/mcp

Transport

Streamable HTTP

Authentication

Atlasemoji-issued bearer credential. OAuth support is planned separately.

Current tool contracts

Discover Atlasemoji Solutions and Agent Capabilities

list_capabilities
Read-onlyLocalmcp available

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.

Required scope
atlasemoji.mcp.read
Tenant requirements
None
Output
Returns the complete Atlasemoji solution catalog and shows how each solution relates to APIs, MCP tools, production services, learning resources, and approved access.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED

Example input

{
  "includeTools": true,
  "includePlatformCapabilities": true,
  "includeLearningResources": true
}

Representative output

{
  "platform": "Atlasemoji",
  "solutionCount": 10,
  "solutions": [
    "Atlas DataSynch",
    "Locations & GIS Foundation",
    "Geofencing",
    "CRM",
    "Inventory & Items",
    "Atlas Intercept",
    "Handheld Scanner",
    "API & Integration Hub",
    "Travel & Routing",
    "Learning & Help"
  ]
}

Review Atlas DataSynch Workflow Status

get_datasynch_run_status
Read-onlyAtlas tenant datapartner access

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.

Required scope
atlasemoji.datasynch.read
Tenant requirements
companyId
Output
Returns recent Atlas DataSynch execution status and related operational context for the authorized tenant scope.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Atlas DataSynch execution information unavailable

Example input

{
  "companyId": "authorized-company-id",
  "workspaceId": "authorized-workspace-id",
  "manifestId": "authorized-manifest-id",
  "timeWindow": "24h"
}

Representative output

{
  "summaryType": "datasynch_run_status",
  "timeWindow": "24h",
  "source": {
    "ok": true,
    "status": 200
  }
}

Review DataSynch Failures and Exceptions

get_failed_runs
Read-onlyAtlas tenant datapartner access

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.

Required scope
atlasemoji.telemetry.read
Tenant requirements
companyId
Output
Returns failed workflow information and available exception context for the authorized company, workspace, manifest, and time window.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Atlas DataSynch exception information unavailable

Example input

{
  "companyId": "authorized-company-id",
  "timeWindow": "7d"
}

Representative output

{
  "summaryType": "failed_runs",
  "timeWindow": "7d",
  "source": {
    "ok": true,
    "status": 200
  }
}

Prepare a Manifest for Atlasemoji Workflows

validate_manifest_schema
Read-onlyLocalmcp available

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.

Required scope
atlasemoji.manifests.read
Tenant requirements
None
Output
Returns structural findings that help a user or agent prepare manifest data for Atlasemoji workflows.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Invalid manifest input schema

Example input

{
  "manifestJson": {
    "manifestId": "manifest-example",
    "locations": [
      {
        "latitude": 47.6101,
        "longitude": -122.2015
      }
    ]
  }
}

Representative output

{
  "valid": true,
  "errors": [],
  "warnings": [],
  "totalLocationCount": 1
}

Understand an Atlasemoji Manifest

get_manifest_summary
Read-onlyAtlas tenant datapartner access

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.

Required scope
atlasemoji.manifests.read
Tenant requirements
companyId, manifestId
Output
Returns the authorized manifest context made available to the client or partner.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Manifest unavailable

Example input

{
  "companyId": "authorized-company-id",
  "manifestId": "authorized-manifest-id"
}

Representative output

{
  "summaryType": "manifest_summary",
  "safeFieldsOnly": true
}

Prepare Coordinates for Atlasemoji GIS Workflows

validate_coordinates
Read-onlyLocalmcp available

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.

Required scope
atlasemoji.geo.validate
Tenant requirements
None
Output
Returns accepted and normalized coordinate values for use in Atlasemoji geographic workflows.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Latitude or longitude outside the accepted range

Example input

{
  "point": {
    "latitude": 47.6101,
    "longitude": -122.2015
  }
}

Representative output

{
  "valid": true,
  "normalized": {
    "latitude": 47.6101,
    "longitude": -122.2015
  }
}

Prepare GeoJSON for Atlasemoji

validate_geojson
Read-onlyLocalmcp available

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.

Required scope
atlasemoji.geo.validate
Tenant requirements
None
Output
Returns structural findings that help users and agents prepare GeoJSON for Atlasemoji workflows.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Unsupported or missing GeoJSON type
  • • Malformed GeoJSON structure

Example input

{
  "geojson": {
    "type": "Point",
    "coordinates": [
      -122.2015,
      47.6101
    ]
  }
}

Representative output

{
  "valid": true,
  "type": "Point",
  "errors": [],
  "warnings": []
}

Identify Location Data for Atlasemoji

detect_location_columns
Read-onlyLocalmcp available

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.

Required scope
atlasemoji.geo.validate
Tenant requirements
None
Output
Returns candidate source fields that may contain geographic information used by Atlasemoji.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Preview rows are missing or exceed the accepted input limit

Example input

{
  "rows": [
    {
      "Store": "Bellevue",
      "Address": "123 Main Street",
      "City": "Bellevue",
      "State": "WA",
      "ZIP": "98004",
      "Latitude": 47.6101,
      "Longitude": -122.2015
    }
  ]
}

Representative output

{
  "candidates": {
    "latitude": [
      "Latitude"
    ],
    "longitude": [
      "Longitude"
    ],
    "address": [
      "Address"
    ],
    "city": [
      "City"
    ],
    "state": [
      "State"
    ],
    "postalCode": [
      "ZIP"
    ]
  }
}

Prepare an Atlasemoji Geofence

preview_geofence
Read-onlyLocalmcp available

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.

Required scope
atlasemoji.geofences.preview
Tenant requirements
companyId
Output
Returns a geofence preview that can support planning, learning, implementation, and approved production setup.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Invalid center coordinates
  • • Radius outside the accepted input range

Example input

{
  "companyId": "authorized-company-id",
  "center": {
    "latitude": 47.6101,
    "longitude": -122.2015
  },
  "radiusMeters": 50,
  "label": "Receiving area"
}

Representative output

{
  "label": "Receiving area",
  "radiusMeters": 50,
  "approximateAreaSquareMeters": 7854
}

Evaluate a Location Against a Geofence

check_point_in_geofence
Read-onlyLocalmcp available

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.

Required scope
atlasemoji.geofences.preview
Tenant requirements
None
Output
Returns the relationship between the supplied point and radius boundary for geofencing, learning, implementation, and workflow planning.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Invalid center or point coordinates
  • • Radius outside the accepted input range

Example input

{
  "center": {
    "latitude": 47.6101,
    "longitude": -122.2015
  },
  "point": {
    "latitude": 47.6102,
    "longitude": -122.2014
  },
  "radiusMeters": 50
}

Representative output

{
  "inside": true,
  "distanceMeters": 13,
  "radiusMeters": 50
}

Prepare Partner and Operational Data for Atlas DataSynch

detect_file_schema
Read-onlyLocalmcp available

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.

Required scope
atlasemoji.datasynch.read
Tenant requirements
None
Output
Returns discovered fields and an initial business-object classification for Atlas DataSynch preparation.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Preview rows are missing or exceed the accepted input limit

Example input

{
  "rows": [
    {
      "sku": "SKU-100",
      "warehouse": "SEA-01",
      "quantity": 25
    }
  ]
}

Representative output

{
  "columns": [
    "sku",
    "warehouse",
    "quantity"
  ],
  "businessObject": {
    "candidate": "inventory"
  }
}

Preview Data for an Atlas DataSynch Workflow

preview_datasynch_rows
Read-onlyLocalmcp available

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.

Required scope
atlasemoji.datasynch.read
Tenant requirements
companyId
Output
Returns field, completeness, and business-object information that supports DataSynch mapping, onboarding, integration design, and workflow preparation.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Preview rows are missing or exceed the accepted input limit

Example input

{
  "companyId": "authorized-company-id",
  "rows": [
    {
      "locationId": "SEA-01",
      "latitude": 47.6101,
      "longitude": -122.2015
    }
  ]
}

Representative output

{
  "rowCount": 1,
  "columns": [
    "locationId",
    "latitude",
    "longitude"
  ]
}

Prepare a DataSynch Field Mapping

suggest_field_mapping
Read-onlyLocalmcp available

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.

Required scope
atlasemoji.datasynch.read
Tenant requirements
None
Output
Returns candidate field relationships that can support DataSynch onboarding and mapping design.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Preview rows are missing or exceed the accepted input limit
  • • Unsupported target table

Example input

{
  "targetTable": "locations",
  "rows": [
    {
      "street": "123 Main Street",
      "city": "Bellevue",
      "state": "WA",
      "zip": "98004",
      "lat": 47.6101,
      "lng": -122.2015
    }
  ]
}

Representative output

{
  "targetTable": "locations",
  "suggestedMapping": {
    "latitude": "lat",
    "longitude": "lng",
    "address": "street",
    "city": "city",
    "state": "state",
    "postalCode": "zip"
  }
}

Summarize Atlasemoji Workspace Activity

summarize_workspace_activity
Read-onlyAtlas tenant datapartner access

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.

Required scope
atlasemoji.telemetry.read
Tenant requirements
companyId
Output
Returns an operational summary for the selected authorized tenant context and time window.
Expected errors
  • • ATLAS_MCP_AUTH_REQUIRED
  • • ATLAS_MCP_POLICY_DENIED
  • • ATLAS_MCP_RATE_LIMITED
  • • Workspace activity unavailable

Example input

{
  "companyId": "authorized-company-id",
  "workspaceId": "authorized-workspace-id",
  "timeWindow": "24h"
}

Representative output

{
  "summaryType": "workspace_activity",
  "timeWindow": "24h"
}

Platform capability classifications

These entries describe Atlasemoji’s broader APIs, products, learning surfaces, and partner capabilities. They do not imply that every platform function is currently callable as an MCP tool.

production platform

Atlas DataSynch

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.

Atlas DataSynch is a production platform. MCP currently supports preparation, discovery, status, exception, and activity use cases while additional approved capabilities can be added for specific client and partner relationships.

production platform

Locations & GIS Foundation

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.

Atlasemoji treats geography as reusable infrastructure that can support applications, people, workflows, and agents.

partner access

Geofencing

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

MCP tools currently support geofence preparation and evaluation. Production geofencing, event processing, alerts, and integrations are available through approved Atlasemoji relationships.

production platform

CRM

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

Atlasemoji CRM capabilities are production platform capabilities. Additional MCP access can be defined for approved client and partner use cases.

production platform

Inventory & Items

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

Inventory and item capabilities can be exposed to approved agents and partners through purpose-built access scopes.

partner access

Atlas Intercept

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

Atlas Intercept is the response layer connecting Atlasemoji events to controlled operational action.

production platform

Handheld Scanner

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

Handheld Scanner is a production solution and is not represented as a standalone public sandbox tool.

partner access

API & Integration Hub

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

The API & Integration Hub is the primary access layer for applications, partners, developers, and approved agents.

public api

Travel & Routing

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

Travelers and Routing provides immediate value for human users, developers, and agents working with movement and geographic planning.

learning resource

Learning & Help

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.

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.

Learning resources

Atlasemoji Learning

Introductions to geography, mapping, spatial data, Atlasemoji solutions, and location-aware workflows.

GeoJSON Conversation Quick Start

Learn how GeoJSON represents places, routes, boundaries, and map features.

Field Guide

Reference material for common Atlasemoji, GIS, map, location, and workflow concepts.

Glossary

Definitions for GIS, GeoJSON, routing, geofencing, integration, DataSynch, telemetry, and spatial workflows.

MCP Documentation

Atlasemoji solutions, MCP functions, API relationships, access requirements, and partner options.

Sandbox access

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 MCP access