INDIVIDUAL MCP TOOL

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.

atlasemoji.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://atlasemoji.com/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for validate_geojson and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

atlasemoji.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.atlasemoji-mcp]
url = "https://atlasemoji.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "atlasemoji-mcp": {
      "type": "http",
      "url": "https://atlasemoji.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: atlasemoji-mcp
Remote MCP URL: https://atlasemoji.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "atlasemoji-mcp": {
      "url": "https://atlasemoji.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "atlasemoji-mcp": {
      "type": "http",
      "url": "https://atlasemoji.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "atlasemoji-mcp",
  "transport": "streamable-http",
  "url": "https://atlasemoji.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

list_capabilities — Discover how Atlasemoji supports Atlas DataSynch, GIS, geofencing, CRM, inventory, Atlas Intercept, handheld scanning, APIs, integrations, routing, storytelling, learning, and partner workflows.
get_datasynch_run_status — Support Atlas DataSynch operations by retrieving recent processing and workflow status for an authorized company, workspace, or manifest.
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.
validate_manifest_schema — Prepare geographic and operational manifest data for Atlasemoji use.
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.
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.
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.
preview_geofence — Prepare a radius-based geofence for an Atlasemoji location-aware workflow.