← Atlas · Topics: components, agents-and-prompts
mapcn
- Site
- mapcn.dev
- Type
- component library
- Verdict
- Useful
- Licence
- Ship licence, open source permissive
open-source-permissivefree; MIT licence in the AnmolSaini16/mapcn repository on GitHub - Agent channels
- registry, prompts
- Pricing
- free
- Reviewed
What it is
A library of ready-to-use map components, built on MapLibre GL and Tailwind CSS, distributed as a shadcn/ui registry: the code is copied into the project instead of installed as a closed package.
When to open it
When a project needs an interactive map (routes, markers, clustering, GeoJSON) matching the same visual conventions as the rest of the shadcn components, without wiring up the MapLibre integration from scratch.
Most useful
Components for a base map, controls, markers, popups, routes, arcs, GeoJSON support and clustering. Requires Tailwind CSS and shadcn/ui already set up in the project; installed with pnpm dlx shadcn@latest add @mapcn/map (or the npm/yarn/bun equivalent), a command that also installs maplibre-gl automatically.
Using it with agents
It includes a "Copy prompt for your agent" button meant to hand component context straight to a coding agent; no dedicated MCP server was found during this review.
Watch out for
Since code is copied instead of relying on a versioned package, mapcn updates don't arrive automatically: you need to re-run the command or manually merge changes. If you need to self-host MapLibre's Web Worker, you must manually copy it into the public folder and update the worker URL.
Reusable ideas
- Extend shadcn's registry model to a specific domain (maps) instead of only generic UI components
- A "copy prompt for your agent" button as a cheap way to hand an agent context without exposing a full MCP
- Explicitly document the point where a developer can "drop down" to the raw map instance when the component isn't enough