About MCP
MCP is an MCP server published by eodash in the AI category: model Context Protocol server for @eodash/eodash custom widgets, templates, configuration and architecture.
The repository has 11 stars and 4 forks, with the last commit 4 days ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
claude mcp add mcp-6de5 -- npx -y @eodash/mcpnpx -y @eodash/mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about MCP
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 3 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- ✓License declaredUsable under a stated license.
- ✓Tests presentA test suite exists in the repository.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
1 check has not been run yet.
Releases
README
@eodash/eodash 
A package for creating earth observation dashboards. To learn more about eodash ecosystem visit eodash.org
Usage
Checkout the documentation for a detailed guide.
Get Started
Install all the required dependencies after cloning or downloading the repository using Node v24 or higher:
npm run install
Run the dev server:
npm run dev
To compile and minify a demo instance:
npm run build
To preview the compiled production files :
npm run preview
To compile and minify a demo instance as a web component library:
npm run build -- --lib
Folder Structure
.
├── core # CLI & Client source code
├── docs # Documentation files
├── templates # Base configurations and eodash templates
├── tests # CLI & Client component tests folder
├── widgets # Vue components as internal widgets.
├── public # Statically served directory
└── README.md
Writing commits
To ensure clear communication with the package consumers and enable machine-readable commits, we adhere to The Conventional Commits specification that allows the generation of semVer releases and associated change logs using googleapis/release-please.
The most important prefixes you should have in mind are:
- fix: which represents bug fixes, and correlates to a SemVer patch.
- feat: which represents a new feature, and correlates to a SemVer minor.
- feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a SemVer major.
README fetched from the repository 3 days ago. The original is authoritative.