EOxElements
Let your coding agent fetch accurate EOxElements custom-element API and usage details while you build Earth-observation or map UIs.
Overview
EOxElements MCP is an MCP server for the Build phase that exposes EOxElements custom-element documentation and metadata to coding agents via streamable HTTP.
What is this MCP server?
- MCP reference server for EOxElements custom elements aimed at coding agents
- Hosted streamable-http remote at elements.mcp.eox.at
- Local option via npm @eox/elements-mcp-server with configurable port (default 3000)
- Version 1.2.1 aligned with EOX-A/EOxElements GitHub repository
- Server version 1.2.1
- npm package @eox/elements-mcp-server
- Default local port 3000
Community signal: 32 GitHub stars.
What problem does it solve?
Agents guess wrong props and events on niche geospatial web components, wasting iterations on EOXT UIs.
Who is it for?
Solo developers building EOXT-powered map or EO data frontends with Claude Code, Cursor, or similar HTTP MCP clients.
Skip if: Projects with no EOxElements stack, or teams that only need generic HTML/CSS help without EO component APIs.
What do I get? / Deliverables
After connecting the server, your agent can pull authoritative EOxElements element info over MCP while you implement map and layer interfaces.
- Agent-accessible EOxElements element reference via MCP
- Optional locally hosted elements MCP on a chosen port
- Fewer hallucinated component APIs during EOXT UI build
Recommended MCP Servers
Journey fit
How it compares
Specialized component-docs MCP remote, not a general design skill or UI generator.
Common Questions / FAQ
Who is EOxElements MCP for?
Builders and agents working on web apps that use EOxElements custom elements who need live, queryable element documentation.
When should I use EOxElements MCP?
Use it during frontend implementation whenever the agent writes or refactors EOXT tags, slots, or configuration.
How do I add EOxElements MCP to my agent?
Add the remote URL https://elements.mcp.eox.at as streamable-http, or install @eox/elements-mcp-server from npm and point your client at http://localhost:3000 (or your port).