# EOxElements

Supplies coding assistants with reference data for EOxElements geospatial web components. Speeds up building maps and spatial user interfaces in front-end projects.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 36
- Author: EOX-A
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/EOX-A/EOxElements
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/eoxelements

## What it does

This server connects language models to specifications for the EOxElements v2 UI suite. It covers custom elements designed for maps like `eox-map` and feature drawing with `eox-drawtools`. That prevents invalid markup.

Every component ships as an individual npm package under `@eox/<element>`. The agent references these schemas directly, formatting tag attributes for bundlers or script tags.

Running the server requires either network access to `https://elements.mcp.eox.at` or local Node.js supporting `npx`. If the connection fails, the agent cannot inspect component structures.

## Requirements
- Needs: Node.js (commands run via npx)
- Remote server: `https://elements.mcp.eox.at`

## Install

### Claude Code (native platform)

1. **Platform CLI: remote server**
```bash
claude mcp add --transport http eoxelements https://elements.mcp.eox.at
```

2. **Platform CLI**
```bash
claude mcp add eoxelements -- npx -y @eox/elements-mcp-server
```

### Codex

1. **Platform CLI: remote server**
```bash
codex mcp add eoxelements --url https://elements.mcp.eox.at
```

2. **Platform CLI**
```bash
codex mcp add eoxelements -- npx -y @eox/elements-mcp-server
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "eoxelements": {
            "url": "https://elements.mcp.eox.at"
        }
    }
}
```
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "eoxelements": {
            "command": "npx",
            "args": [
                "-y",
                "@eox/elements-mcp-server"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "eoxelements": {
            "type": "http",
            "url": "https://elements.mcp.eox.at"
        }
    }
}
```
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "eoxelements": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@eox/elements-mcp-server"
            ]
        }
    }
}
```

### Gemini CLI

1. **Platform CLI: remote server**
```bash
gemini mcp add -t http eoxelements https://elements.mcp.eox.at
```

2. **Platform CLI**
```bash
gemini mcp add eoxelements npx -y @eox/elements-mcp-server
```

## When to use it
- configure eox-map alongside layer controls in front-end markup
- implement spatial feature editing with eox-drawtools
- add geographic autocomplete using eox-geosearch
- render STAC metadata records with eox-stacinfo

## Example prompts
- Show how to import eox-map and eox-layercontrol in a Vite setup.
- Add eox-geosearch to my layout and bind it to the main map.
- Create an eox-jsonform element configured with my JSON schema.

## Similar
- [Front-End Checklist](https://affpapa.org/en/nevibecode/mcp/front-end-checklist.md) — MCP server · ★ 74559
- [tldraw](https://affpapa.org/en/nevibecode/mcp/tldraw.md) — MCP server · ★ 51091
- [Figma-Context-MCP](https://affpapa.org/en/nevibecode/mcp/figma-context-mcp.md) — MCP server · ★ 16062
- [mcp-server-chart](https://affpapa.org/en/nevibecode/mcp/mcp-server-chart.md) — MCP server · ★ 4402
- [Dembrandt](https://affpapa.org/en/nevibecode/mcp/dembrandt.md) — MCP server · ★ 3821
- [RevoGrid DataGrid MCP Pro](https://affpapa.org/en/nevibecode/mcp/revogrid-datagrid-mcp-pro.md) — MCP server · ★ 3450

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md