Atlasemoji

com.atlasemojiPublished by atlasemoji.comOfficial publisherv0.1.0Updated Oct 24, 2026

AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.

VerifiedStreamable HTTPWeb executableLocation & LifestyleDeveloper ToolsData & Analytics

Overview

AI-generated overview

Atlasemoji is a remote MCP server for location-aware operations: GIS manifests, geofences, coordinate checks, DataSynch integration status and place research.

What you can do
Inspect the connected Atlas account and verify the agent connection, and list available capabilities and partner access paths. Validate and summarize geographic manifests, coordinates and GeoJSON, and detect location columns in records. Preview radius geofences and test whether a point falls inside one. Review DataSynch run status, failed runs, file schemas and record previews, and suggest field mappings. Summarize workspace activity, and assemble cited place-research packages from registered historical, academic and environmental providers.
When to use it
Use it when an assistant needs to work with Atlasemoji location data, geofences, manifests or DataSynch integrations, or to investigate failed integration runs and prepare field mappings. Also useful for geographically grounded place research with citations.
Requirements
A remote streamable HTTP endpoint at atlasemoji.com. A bearer token is required in the Authorization header, entered as the full value including the Bearer prefix. The token must be authorized for the requested company, workspace or manifest.
Before you install
The bearer token is a secret credential granting access to an Atlas account; keep it private. Most tools are read-only or validation-only, but the token's scope determines which company, workspace and manifest data the assistant can see. Place research queries third-party provider integrations and returns source links.

Installation

In SourceWeft

  1. Open Atlasemoji in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.atlasemoji%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "atlasemoji": {
      "type": "http",
      "url": "https://atlasemoji.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

19

list_capabilities

Discover Atlasemoji Solutions and Agent 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.

ParametersincludeToolsincludeLearningResourcesincludePlatformCapabilities

get_atlas_profile

Get the connected Atlasemoji profile

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

Takes no parameters.

verify_atlas_agent

Verify an Atlas Agent Connection

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.

ParametersagentIdrequiredcompanyIdrequiredconnectionIdrequired

get_datasynch_run_status

Review Atlas DataSynch Workflow 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.

ParameterscompanyIdrequiredmanifestIdtimeWindowworkspaceId

get_failed_runs

Review DataSynch Failures and Exceptions

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.

ParameterscompanyIdrequiredmanifestIdtimeWindowworkspaceId

validate_manifest_schema

Prepare a Manifest for Atlasemoji Workflows

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.

ParametersmanifestJsonrequired

get_manifest_summary

Understand an Atlasemoji Manifest

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.

ParameterscompanyIdrequiredmanifestIdrequiredworkspaceId

validate_coordinates

Prepare Coordinates for Atlasemoji GIS Workflows

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.

Parameterspointrequired

validate_geojson

Prepare GeoJSON for Atlasemoji

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.

Parametersgeojsonrequired

detect_location_columns

Identify Location Data for Atlasemoji

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.

Parametersrowsrequired

preview_geofence

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

ParameterslabelcenterrequiredcompanyIdrequiredmanifestIdworkspaceIdradiusMetersrequired

check_point_in_geofence

Evaluate a Location Against a 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.

ParameterspointrequiredcenterrequiredradiusMetersrequired

detect_file_schema

Prepare Partner and Operational Data for Atlas DataSynch

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.

Parametersrowsrequired

preview_datasynch_rows

Preview Data for an Atlas DataSynch Workflow

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.

ParametersrowsrequiredcompanyIdrequiredmanifestIdworkspaceId

suggest_field_mapping

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

ParametersrowsrequiredtargetTable

summarize_workspace_activity

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

ParameterscompanyIdrequiredmanifestIdtimeWindowworkspaceId

wanderloop.research_place

Wanderloop — Research a Place

Assemble 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 evidence records, provider execution status, citations, GeoJSON map features, and saved manifest links. This is evidence assembly, not an unsupported AI-written story.

Takes no parameters.

wanderloop.get_manifest

Wanderloop — Get Saved Manifest

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

ParametersmanifestIdrequired

wanderloop.list_provider_capabilities

Wanderloop — List Provider Capabilities

List 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, environmental, and natural-history sources Atlasemoji can invoke.

Parameterstopic

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.