Live feature services
Every synced table is served as an ArcGIS-compatible FeatureServer — query, applyEdits, attachments and
relationships — so existing GIS clients work without a translation layer.
Sync Server
Point it at your data. Get live, editable feature services, vector tiles and GeoJSON — with authentication built in.
What it does
Section titled “What it does”Vector tiles & GeoJSON
The same table is available as Mapbox Vector Tiles and plain GeoJSON, for MapLibre, Mapbox GL, deck.gl or anything else that reads those formats.
Editable, with a full history
Writes go through to the source system, and every change is logged with a before-snapshot — so you can see who changed what, and roll it back.
Authentication
Sign users in with the identity provider your organization already uses, then hand your app a short-lived token. Machine access uses scoped, revocable API keys.
Any stack
Plain HTTP endpoints, plus npm packages for browser sign-in and an AI chat. React, Vue, Svelte, vanilla JS, a backend job — if it can make a request, it can use Sync Server.
MCP for LLM clients
Each base exposes a Model Context Protocol server, so an LLM client can explore and edit the data through tools — attributed to the person driving them.
Start here
Section titled “Start here”How Sync Server worksBases, tables, providers, strategies and the cache — the terms used throughout these docs.
Authenticating a browser appSign users in, get an app token, and read and edit through the feature service — with ArcGIS Maps SDK and MapLibre examples.
Working with data
Section titled “Working with data”Reading and editing featuresThe FeatureServer surface: queries, applyEdits, field metadata, relationships and concurrency.
The records APIPlain JSON CRUD over a table, addressed by provider record key.
Editing in the gridWhat the built-in grid lets you do to a table — cells, clipboard, undo, batched saves, conflicts, attachments and restore.
Saved grid viewsPersist column layout, filters, sorts and colour rules as personal or shared views.
AttachmentsRead, add and delete files through the Esri attachment endpoints, with cached bytes and thumbnails.
Collaboration and safety
Section titled “Collaboration and safety”Realtime changes and presenceSubscribe to live table changes over WebSocket and see who else is editing.
Activity history and rollbackWho changed what, when — and how to restore a record, a table or a whole base.
Getting data out
Section titled “Getting data out”Exporting layers to filesShapefile, GeoPackage, File Geodatabase, Excel, KML, FlatGeobuf, GeoParquet and more, as async jobs.
Vector tiles and snapshotsLive MVT from the cache or PostGIS, or an immutable hosted tileset behind a CDN.
MCP for LLM clientsConnect Claude, or any MCP client, to a base's tables and tools.
Reference
Section titled “Reference”Endpoint referenceEvery route, grouped by purpose, with the access each one requires.
Client packages (npm)@imaps/sync-server-auth and @imaps/ai-chat — install lines, entry points and how they fit together.
Organizations, roles and API keysHow access is decided, and how to scope and restrict a key.
Providers and table configurationEvery data source, and the full set of options on a base and a table.