Atlasemoji
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
Should I use this
Quality & Safety
Findings (4)
- LOWTool 'wanderloop.research_place' doesn't follow camelCase/snake_casein wanderloop.research_place
- LOWTool 'wanderloop.get_manifest' doesn't follow camelCase/snake_casein wanderloop.get_manifest
- LOWTool 'wanderloop.list_provider_capabilities' doesn't follow camelCase/snake_casein wanderloop.list_provider_capabilities
- LOWTool 'wanderloop.list_provider_capabilities' name length outside 3-30 rangein wanderloop.list_provider_capabilities
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"mcp": {
"url": "https://atlasemoji.com/api/mcp"
}
}
}Remote endpoints
https://atlasemoji.com/api/mcpstreamable-httpWhat it can do
Tool inventory
Tools (17)
🟢list_capabilities(includeTools, includePlatformCapabilities, includeLearningResources)
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.
Input Schema
{
"type": "object",
"properties": {
"includeTools": {
"type": "boolean",
"default": true,
"description": "Include currently callable Atlasemoji MCP tools and show which solutions each tool supports."
},
"includePlatformCapabilities": {
"type": "boolean",
"default": true,
"description": "Include the complete Atlasemoji solution catalog with business outcomes, APIs, production capabilities, learning opportunities, access requirements, and next actions."
},
"includeLearningResources": {
"type": "boolean",
"default": true,
"description": "Include Atlasemoji learning, help, quick-start, glossary, and MCP documentation resources."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_datasynch_run_status(companyId, workspaceId, manifestId, timeWindow)
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.
Input Schema
{
"type": "object",
"properties": {
"companyId": {
"type": "string",
"minLength": 1,
"description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
},
"workspaceId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
},
"manifestId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji manifest identifier used to narrow the authorized operation."
},
"timeWindow": {
"type": "string",
"enum": [
"1h",
"6h",
"24h",
"7d",
"30d"
],
"default": "24h",
"description": "Time window used for read-only operational summaries and diagnostics."
}
},
"required": [
"companyId"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_failed_runs(companyId, workspaceId, manifestId, timeWindow)
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.
Input Schema
{
"type": "object",
"properties": {
"companyId": {
"type": "string",
"minLength": 1,
"description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
},
"workspaceId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
},
"manifestId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji manifest identifier used to narrow the authorized operation."
},
"timeWindow": {
"type": "string",
"enum": [
"1h",
"6h",
"24h",
"7d",
"30d"
],
"default": "24h",
"description": "Time window used for read-only operational summaries and diagnostics."
}
},
"required": [
"companyId"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢validate_manifest_schema(manifestJson)
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.
Input Schema
{
"type": "object",
"properties": {
"manifestJson": {
"type": "object",
"additionalProperties": {},
"description": "Manifest-like JSON object to inspect locally. The object is not saved or published."
}
},
"required": [
"manifestJson"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_manifest_summary(companyId, workspaceId, manifestId)
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.
Input Schema
{
"type": "object",
"properties": {
"companyId": {
"type": "string",
"minLength": 1,
"description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
},
"workspaceId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
},
"manifestId": {
"type": "string",
"minLength": 1,
"description": "Required Atlasemoji manifest identifier to summarize."
}
},
"required": [
"companyId",
"manifestId"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢validate_coordinates(point)
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.
Input Schema
{
"type": "object",
"properties": {
"point": {
"type": "object",
"properties": {
"latitude": {
"type": "number",
"minimum": -90,
"maximum": 90,
"description": "Latitude in decimal degrees between -90 and 90."
},
"longitude": {
"type": "number",
"minimum": -180,
"maximum": 180,
"description": "Longitude in decimal degrees between -180 and 180."
}
},
"required": [
"latitude",
"longitude"
],
"additionalProperties": false,
"description": "Coordinate pair to validate and normalize."
}
},
"required": [
"point"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢validate_geojson(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.
Input Schema
{
"type": "object",
"properties": {
"geojson": {
"type": "object",
"additionalProperties": {},
"description": "A GeoJSON Feature, FeatureCollection, Geometry, or GeometryCollection object for basic structural inspection."
}
},
"required": [
"geojson"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢detect_location_columns(rows)
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.
Input Schema
{
"type": "object",
"properties": {
"rows": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": {}
},
"minItems": 1,
"maxItems": 100,
"description": "Between 1 and 100 preview records whose column names should be inspected for likely location fields."
}
},
"required": [
"rows"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢preview_geofence(companyId, workspaceId, manifestId, center, radiusMeters, ...)
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.
Input Schema
{
"type": "object",
"properties": {
"companyId": {
"type": "string",
"minLength": 1,
"description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
},
"workspaceId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
},
"manifestId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji manifest identifier used to narrow the authorized operation."
},
"center": {
"type": "object",
"properties": {
"latitude": {
"type": "number",
"minimum": -90,
"maximum": 90,
"description": "Latitude in decimal degrees between -90 and 90."
},
"longitude": {
"type": "number",
"minimum": -180,
"maximum": 180,
"description": "Longitude in decimal degrees between -180 and 180."
}
},
"required": [
"latitude",
"longitude"
],
"additionalProperties": false,
"description": "Center coordinate of the proposed radius geofence."
},
"radiusMeters": {
"type": "number",
"minimum": 1,
"maximum": 100000,
"description": "Radius in meters. Accepted range is 1 through 100,000 meters."
},
"label": {
"type": "string",
"maxLength": 200,
"description": "Optional human-readable label for the calculation-only preview."
}
},
"required": [
"companyId",
"center",
"radiusMeters"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢check_point_in_geofence(center, point, radiusMeters)
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.
Input Schema
{
"type": "object",
"properties": {
"center": {
"type": "object",
"properties": {
"latitude": {
"type": "number",
"minimum": -90,
"maximum": 90,
"description": "Latitude in decimal degrees between -90 and 90."
},
"longitude": {
"type": "number",
"minimum": -180,
"maximum": 180,
"description": "Longitude in decimal degrees between -180 and 180."
}
},
"required": [
"latitude",
"longitude"
],
"additionalProperties": false,
"description": "Center coordinate of the radius geofence."
},
"point": {
"type": "object",
"properties": {
"latitude": {
"$ref": "#/properties/center/properties/latitude"
},
"longitude": {
"$ref": "#/properties/center/properties/longitude"
}
},
"required": [
"latitude",
"longitude"
],
"additionalProperties": false,
"description": "Coordinate to test against the radius geofence."
},
"radiusMeters": {
"type": "number",
"minimum": 1,
"maximum": 100000,
"description": "Radius in meters. Accepted range is 1 through 100,000 meters."
}
},
"required": [
"center",
"point",
"radiusMeters"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢detect_file_schema(rows)
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.
Input Schema
{
"type": "object",
"properties": {
"rows": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": {},
"description": "One preview record represented as an object of source column names and values."
},
"minItems": 1,
"maxItems": 100,
"description": "Between 1 and 100 preview rows from a CSV, spreadsheet, JSON, EDI-normalized, or other tabular payload. Rows are inspected in memory and are not committed by MCP preview tools."
}
},
"required": [
"rows"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢preview_datasynch_rows(companyId, workspaceId, manifestId, 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.
Input Schema
{
"type": "object",
"properties": {
"companyId": {
"type": "string",
"minLength": 1,
"description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
},
"workspaceId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
},
"manifestId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji manifest identifier used to narrow the authorized operation."
},
"rows": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": {},
"description": "One preview record represented as an object of source column names and values."
},
"minItems": 1,
"maxItems": 100,
"description": "Between 1 and 100 preview rows from a CSV, spreadsheet, JSON, EDI-normalized, or other tabular payload. Rows are inspected in memory and are not committed by MCP preview tools."
}
},
"required": [
"companyId",
"rows"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢suggest_field_mapping(rows, targetTable)
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.
Input Schema
{
"type": "object",
"properties": {
"rows": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": {},
"description": "One preview record represented as an object of source column names and values."
},
"minItems": 1,
"maxItems": 100,
"description": "Between 1 and 100 preview rows from a CSV, spreadsheet, JSON, EDI-normalized, or other tabular payload. Rows are inspected in memory and are not committed by MCP preview tools."
},
"targetTable": {
"type": "string",
"enum": [
"locations",
"items",
"inventory",
"telemetry",
"crm"
],
"description": "Optional Atlasemoji target-table family. When omitted, the tool uses its heuristic business-object candidate."
}
},
"required": [
"rows"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢summarize_workspace_activity(companyId, workspaceId, manifestId, timeWindow)
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.
Input Schema
{
"type": "object",
"properties": {
"companyId": {
"type": "string",
"minLength": 1,
"description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
},
"workspaceId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
},
"manifestId": {
"type": "string",
"minLength": 1,
"description": "Optional Atlasemoji manifest identifier used to narrow the authorized operation."
},
"timeWindow": {
"type": "string",
"enum": [
"1h",
"6h",
"24h",
"7d",
"30d"
],
"default": "24h",
"description": "Time window used for read-only operational summaries and diagnostics."
}
},
"required": [
"companyId"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪wanderloop.research_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.
Input Schema
{
"type": "object",
"properties": {}
}🟢wanderloop.get_manifest(manifestId)
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.
Input Schema
{
"type": "object",
"properties": {
"manifestId": {
"type": "string",
"minLength": 1,
"maxLength": 300
}
},
"required": [
"manifestId"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢wanderloop.list_provider_capabilities(topic)
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.
Input Schema
{
"type": "object",
"properties": {
"topic": {
"type": "string",
"enum": [
"record",
"life",
"study"
]
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence