mcpField
E
EOxElements

EOxElements

Remote
github.com/EOX-ADeveloper Tools36Updated today
Repository

About EOxElements

EOxElements is a collection of geospatial Web Components from EOX, covering maps, layer control, drawing, search and more. It also ships an MCP server that gives coding agents information about its custom elements.

Key features

  1. 01Geospatial UI elements built as Web Components
  2. 02Components such as eox-map and eox-drawtools
  3. 03Installable via npm or a script tag
  4. 04MCP server exposing information about custom elements

Use cases

  1. 01Building map interfaces in Vite or Webpack projects
  2. 02Letting a coding agent look up component usage
  3. 03Adding controls for STAC data or map time series

MCP support

This project is an MCP server that provides MCP clients with information about EOxElements custom elements for coding agents.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://elements.mcp.eox.at
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Packages
npm@eox/elements-mcp-server1.2.1

Tools

Details

From the project README

EOxElements

A Web Component collection of geospatial UI elements, crafted by EOX.

Documentation, Examples

Please find descriptions, API docs and interactive examples here.

Elements

  • ⭕️ Alpha elements are in-development and may have many frequent breaking changes.
  • 🟡 Beta elements are mostly polished and ready for use, but may still have breaking changes.
  • ✅ Stable elements are reviewed, documented, and API complete.
ElementDescriptionDocs & ExamplesVersionState
eox-chartDynamic chart with built-in data fetchingDocs & ExamplesREADME image✅
eox-drawtoolsDraw and manage features on a mapDocs & ExamplesREADME image✅
eox-feedbackQuick and easy feedback widgetDocs & ExamplesREADME image✅
eox-geosearchAn autocompleted search input for geographic locationsDocs & ExamplesREADME image✅
eox-itemfilterFilter/search large sets of items client-side or server-sideDocs & ExamplesREADME image✅
eox-jsonformRender a form from a JSON schemaDocs & ExamplesREADME image✅
eox-layercontrolManage and modify map layersDocs & ExamplesREADME image✅
eox-layoutEasily create a UI layoutDocs & ExamplesREADME image✅
eox-mapMap with powerful tools & helpersDocs & ExamplesREADME image✅
eox-stacinfoDisplay properties of STAC filesDocs & ExamplesREADME image✅
eox-storytellingStoryTelling tools based on markdownDocs & ExamplesREADME image✅
eox-timecontrolTime control and playback for map layersDocs & ExamplesREADME image✅
eox-tourGuided tour for UIsDocs & ExamplesREADME image✅

Usage

For detailed descriptions and documentation on the individual elements, please check out the READMEs in the element subfolders.

Bundlers (Vite, Webpack, etc.)
npm install @eox/<element>
import "@eox/<element>"
<eox-element></eox-element>
Script tag
<eox-element></eox-element>

<script type="module">
import "@eox/<element>" from "https://cdn.skypack.dev/@eox/<element>"
</script>

Development

For detailed development instructions, including monorepo structure, coding standards, and testing procedures, please refer to the Contributing Guide.

AI Agents working in this repository should also consult AGENTS.md for specific guidelines on maintaining documentation and ensuring compatibility with the MCP server.

License

By contributing to EOxElements, you agree that your contributions will be licensed under the repository's LICENSE.

Previous versions

The main branch of this project contains the v2 version of EOxElements. For the (legacy) v1 EOxElements, please see the v1 branch.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.