GitHub repo analytics: stars, trending, code search, contributor maps for project research.
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.
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
What it does
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
Quickstart
# 1 — install (mcprush login holds a key from your dashboard)
npx mcprush@latest add atlasemoji-mcp
# 2 — ask your agent something
> AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
Atlasemoji is free: there is no plan to choose, no cap to set and nothing that can bill you.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add --transport http atlasemoji-mcp https://atlasemoji.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
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 as
Takes no parameters.
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.
Takes no parameters.
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.
Takes no parameters.
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Atlasemoji costs nothing to install and nothing to call, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
Pinned to 0.1.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
No release note was published with this version.
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Writing one takes an account with at least 50 real tool calls against Atlasemoji in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.