MCP server for shared Elements engineering standards, domain knowledge, skills, prompts, and templates.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"elements-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# elements-mcp Project Guide `elements-mcp` is a read-only MCP server that packages shared Elements engineering standards, skills, and templates as a Python package for Codex, GitHub Copilot, and other AI coding agents. This document is for maintainers. It describes the project structure, development verification, release flow, and content maintenance rules. For user installation and MCP client setup, see [docs/install-elements-mcp-user-guide-zh.md](docs/install-elements-mcp-user-guide-zh.md). ## Goals and Boundaries Goals: - Consolidate engineering standards, domain knowledge, skills, prompts, and templates shared by multiple business repositories into reusable MCP content. - Distribute the Python package through PyPI so users get the latest version by default, while still allowing pinned versions when needed. - Expose packaged skills/templates and reusable prompts through MCP tools, resources, and prompts. - Keep the server read-only to reduce security risk. Boundaries: - The server may list, search, and read packaged skills/templates. - The server must not write files, delete files, execute shell commands, install dependencies, or read paths outside the package. - Any future write-capable or execution-capable tools require a separate security design. ## Repository Layout ```text elements-mcp/ README.md README.zh-CN.md MANIFEST.in pyproject.toml docs/ install-elements-mcp-user-guide-zh.md scripts/ install_elements_mcp.py publish-pypi.ps1 pypi-publish.env.example.ps1 update-package-metadata.ps1 src/ elements_mcp/ __init__.py server.py tools/ resources/ registry.py handlers.py content/ skills/ ui-standard-layout/ api-integration/ prompts/ registry.py handlers.py content/ tests/ ``` ## Key File Responsibilities - `pyproject.toml`: Python package conf…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.