Frontmcp Testing
agentfront/frontmcp
A skill your agent uses for anything about testing FrontMCP servers: writing or running unit, integration, and E2E tests and reaching the 95%+ coverage bar.
How to manually e2e-test each EDT-MCP server tool against a live EDT workbench + TestConfiguration.
Install Edt MCP Testing
$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install DitriXNew/EDT-MCP edt-mcp-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/edt-mcp-testing .claude/skills/edt-mcp-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "edt-mcp-testing" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-testing into .claude/skills/edt-mcp-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install DitriXNew/EDT-MCP edt-mcp-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/edt-mcp-testing .agents/skills/edt-mcp-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "edt-mcp-testing" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-testing into .agents/skills/edt-mcp-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install DitriXNew/EDT-MCP edt-mcp-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/edt-mcp-testing .cursor/skills/edt-mcp-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "edt-mcp-testing" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-testing into .cursor/skills/edt-mcp-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/DitriXNew/EDT-MCP.git --path .claude/skills/edt-mcp-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install DitriXNew/EDT-MCP edt-mcp-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/edt-mcp-testing .gemini/skills/edt-mcp-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "edt-mcp-testing" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-testing into .gemini/skills/edt-mcp-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install DitriXNew/EDT-MCP edt-mcp-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/edt-mcp-testing .github/skills/edt-mcp-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "edt-mcp-testing" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-testing into .github/skills/edt-mcp-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install DitriXNew/EDT-MCP edt-mcp-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/edt-mcp-testing .opencode/skills/edt-mcp-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "edt-mcp-testing" agent skill from https://github.com/DitriXNew/EDT-MCP/tree/master/.claude/skills/edt-mcp-testing into .opencode/skills/edt-mcp-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edt-mcp-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
edt-mcp-testing- GitHub stars
- 295
- Token cost
- ~2.1k tokens
- SKILL.md length
- 589 words
- Files
- 67 (incl. references)
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
How to manually e2e-test each EDT-MCP server tool against a live EDT workbench + TestConfiguration.
- Works in 4 steps: Run the tool live with real arguments on… → Record the exact call + actual output +… → Link the family SETUP.md. → …
- Validating an MCP tool end-to-end by actually calling it (for build/unit tests see edt-mcp-build-test)
- SKILL.md covers Structure, Test bench (harness), How to add a tool reference and Index — debug…, plus 4 more sections
- Calls git, pwsh and bash
What it does
Edt MCP Testing is an agent skill from DitriXNew/EDT-MCP. How to manually e2e-test each EDT-MCP server tool against a live EDT workbench + TestConfiguration. One reference per tool under references/<family/, each with the exact MCP call, the real expected result, and gotchas. Use when validating an MCP tool end-to-end by actually calling it (for build/unit tests see edt-mcp-build-test).
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 70 other files, including reference files (for example `references/debug/SETUP.md`, `references/debug/debug_status.md` and `references/debug/evaluate_expression.md`).
It sits in Testing & QA, covering MCP servers, End-to-end testing and Unit testing. It works with Model Context Protocol and Git. The licence is AGPL-3.0.
When your agent uses it
- Validating an MCP tool end-to-end by actually calling it (for build/unit tests see edt-mcp-build-test)
- Tasks that involve MCP servers
- Tasks that involve End-to-end testing
Example prompts
- “/edt-mcp-testing”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Run the tool live with real arguments on TestConfiguration.
- Record the exact call + actual output + gotchas in references//.md.
- Link the family SETUP.md.
- If the run needs a base mutation — document it and the revert.
What it can do on your machine
Read from SKILL.md and the folder at commit 6d18531. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitpwshbash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Edt MCP Testing loads about 2.1k tokens when it runs, and up to ~93k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 589 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from DitriXNew/EDT-MCP at commit 6d18531, republished under its AGPL-3.0 licence (© DitriXNew). 589 words, ~2,074 tokens.
Download SKILL.mdSave it as
.claude/skills/edt-mcp-testing/SKILL.md (or your agent's skills folder). This skill also uses 66 other files; get the full folder from GitHub.- name
- edt-mcp-testing
- description
- How to manually e2e-test each EDT-MCP server tool against a live EDT workbench + TestConfiguration. One reference per tool under references/<family>/, each with the exact MCP call, the real expected result, and gotchas. Use when validating an MCP tool end-to-end by actually calling it (for build/unit tests see edt-mcp-build-test).
EDT-MCP — manual e2e testing of tools
How to run each MCP tool live against a working EDT and confirm it actually works (not just compiles / passes a unit test). Build and unit tests are in edt-mcp-build-test; this is live e2e through real MCP calls. (The automated black-box suite is edt-mcp-e2e-testing.)
Structure
references/<family>/<tool>.md— one reference per tool: purpose, exact call, expected result, gotchas.references/<family>/SETUP.md— shared family preconditions (what the family's tools can't be tested without).
Test bench (harness)
- Non-elevated EDT copy + workspace
D:\WS\EDT; MCP listens on:8765. Deploy edits withpwsh D:\Soft\edt-redeploy.ps1(build → kill EDT → swap bundle →-cleanrelaunch → wait for:8765). The script sometimes returns exit 1 yet printsMCP server UP on 8765— that is success; check the port /get_edt_version, don't trust the exit code. - Test base — the
TestConfigurationproject (in repoTestConfiguration/src, open in the workspace). Run destructive/mutating cases only on it; revert after:git checkout HEAD -- TestConfiguration && git clean -fd -- TestConfiguration. - Workflow invariant: edit →
bash source/compile.sh→ redeploy → live MCP call →git diff→ revert. After a-cleanredeploy EDT loses unsaved in-memory changes — mutate through MCP (write_module_sourceetc.) so model and disk stay in sync. - Flaky tool output: the channel sometimes drops text (you see a bare
Error/Doneinstead of JSON). Re-verify state independently:debug_status,git status,Get-Process, and especially the EDT logD:\WS\EDT\.metadata\.log(it records the full request/response). Don't trust the echo.
How to add a tool reference
- Run the tool live with real arguments on
TestConfiguration. - Record the exact call + actual output + gotchas in
references/<family>/<tool>.md. - Link the family
SETUP.md. - If the run needs a base mutation — document it and the revert.
Index — debug (references/debug/)
- SETUP — bring up a debuggable scenario (executable code + trigger + stop).
- Configs/launch:
list_configurations,launch,debug_status,terminate_launch. - Breakpoints:
set_breakpoint,list_breakpoints,remove_breakpoint. - Break and inspect:
wait_for_break,get_variables,evaluate_expression,step,resume.
Full debug flow: set_breakpoint → launch(update) → wait_for_break(hit) → get_variables → step over → get_variables → evaluate_expression → resume → remove_breakpoint. Details per tool in its reference.
Index — navigation / read (references/navigation/)
Read-only navigation and read tools, each with a real live call on TestConfiguration.
- SETUP — project ready (not
building), BSL index built, modulePath addressing, UI-thread tools. - Workspace/listing: list_projects, list_modules.
- Source: read_module_source, read_method_source, get_module_structure.
- AST/refs: go_to_definition, find_references, get_method_call_hierarchy, get_symbol_info, get_content_assist.
Show full SKILL.md (228 more words)Show less
Index — metadata-read (references/metadata-read/)
Read-only reading of the configuration model (objects, details, properties, subsystems, tags). Each with a real live call on TestConfiguration.
- Objects: get_metadata_objects, get_metadata_details.
- Configuration: get_configuration_properties (YAML).
- Subsystems: list_subsystems, get_subsystem_content.
- Tags: get_tags, get_objects_by_tags.
Index — query / problems / misc (read-only)
- query (
references/query/): validate_query (dialect-aware,valid:false≠ failure). - problems (
references/problems/): get_project_errors, get_problem_summary, get_check_description (reads<checkId>.mdfrom a configurable folder; the feature is OFF by default; checkId is sanitized — dotted codes don't resolve). - misc (
references/misc/): get_edt_version (TEXT, liveness probe), get_platform_documentation, get_markers, get_applications.
Index — profiling / forms / xml / translation / launch / metadata-write
Families with write/destructive/special setup. For mutating/destructive tools the docs describe the test procedure from source (mutate-then-revert / preview-then-confirm), without live destruction.
- profiling (
references/profiling/): start_profiling (a TOGGLE; applicationId = the debug-session id, not the infobase GUID), get_profiling_results (read-only; returns only the most recent measurement session). - forms (
references/forms/): get_form_screenshot, get_form_layout_snapshot — need the JVM flag-DnativeFormBufferedLayoutRender=true; blank ≠ a bug; native vs buffered render. - xml (
references/xml/): export_configuration_to_xml, import_configuration_from_xml (MUTATES → revert). - translation (
references/translation/): get_translation_project_info (read-only), generate_translation_strings, translate_configuration (MUTATES + external providers). - launch (
references/launch/): update_database (DESTRUCTIVE, exclusive infobase access), run_yaxunit_tests, debug_yaxunit_tests. - metadata-write (
references/metadata-write/): create_metadata (FQN-addressed), modify_metadata (set properties=[{name,value,language?}] by FQN), write_module_source (mutate→verify→revert), rename_metadata_object, delete_metadata (FQN-addressed; CASCADE; preview→confirm→revert; explicit-request-only), adopt_metadata_object (adopt a base object/member into an extension; MUTATES→revert).
Coverage: debug + navigation, metadata-read, query, problems, misc, profiling, forms, xml, translation, launch, metadata-write = every MCP tool (62 today) has a per-tool e2e reference. Write/destructive tools document the procedure from source (mutate-then-revert / preview-then-confirm), not live destruction.
© DitriXNew, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 66 other files (references) in .claude/skills/edt-mcp-testing of DitriXNew/EDT-MCP.
- SKILL.md
- references/debug/SETUP.md
- references/debug/debug_status.md
- references/debug/evaluate_expression.md
- references/debug/get_variables.md
- references/debug/launch.md
- references/debug/list_breakpoints.md
- references/debug/list_configurations.md
- references/debug/remove_breakpoint.md
- references/debug/resume.md
- references/debug/set_breakpoint.md
- references/debug/step.md
- references/debug/terminate_launch.md
- references/debug/wait_for_break.md
- references/forms/get_form_layout_snapshot.md
- references/forms/get_form_screenshot.md
- references/launch/debug_yaxunit_tests.md
- … and 50 more
Open the folder on GitHubat commit 6d18531
Compare with similar skills
Edt MCP Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Edt MCP Testing this skillDitriXNew/EDT-MCP | 295 | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Frontmcp Testingagentfront/frontmcp | 146 | — | ~10k | Automated safety check: Notes | Apache-2.0 | |
| Qwen Code E2E TestingQwenLM/qwen-code | 28k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Adding LLM MCP ToolsTriliumNext/Trilium | 38k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| Exploring The WizardPostHog/wizard | 197 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Diff-Driven Smoke TestsSkyvern-AI/skyvern | 23k | — | ~5.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Qwen Code E2E Testing
QwenLM/qwen-code
Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.
Adding LLM MCP Tools
TriliumNext/Trilium
A skill your agent uses when adding, changing, or reviewing an LLM/MCP tool in Trilium (the defineTools definitions under packages/trilium-core/src/services/llm/tools/ —…
- Official
Exploring The Wizard
PostHog/wizard
Drive the PostHog wizard headlessly against a throwaway app through wizard-ci MCP tools, inspect decisions, and capture the real TUI.
Diff-Driven Smoke Tests
Skyvern-AI/skyvern
Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.
Glance Test
DebugBase/glance
Run E2E browser tests on any web application using Glance MCP.
More from DitriXNew/EDT-MCP
All 24 skills in this repoEdt MCP Autopilot
DitriXNew/EDT-MCP
Autonomous, spec-driven, multi-agent pipeline that takes an EDT-MCP task or issue end-to-end — research → critics → architect → parallel development → review loop → tests → live-stand check →…
Edt MCP Build Test
DitriXNew/EDT-MCP
How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo.
Edt MCP E2E Testing
DitriXNew/EDT-MCP
How to write/run the AUTOMATED black-box e2e suite (tests/e2e/) that covers every EDT-MCP tool (62 today) against a live server with git-fixture isolation, happy + negative + error-quality coverage…
Edt MCP Tool Descriptions
DitriXNew/EDT-MCP
How to size, write and A/B-test the text of a tool — its description and its inputSchema parameter prose — so that cutting it does not cost call quality, and so that a tool that IS getting called…
Edt MCP Yaxunit
DitriXNew/EDT-MCP
How to write and run YAXUnit unit tests for a 1C configuration through 1C:EDT + the EDT-MCP runyaxunittests / debugyaxunittests tools.
Edt MCP Architecture
DitriXNew/EDT-MCP
Map of the EDT-MCP plugin's target architecture — where the shared helpers live, the layering rules, and the canonical way to do project/metadata/code resolution.
Related
Works with
Categories
Questions about Edt MCP Testing
What does Edt MCP Testing do?
How to manually e2e-test each EDT-MCP server tool against a live EDT workbench + TestConfiguration. Edt MCP Testing is an agent skill from DitriXNew/EDT-MCP. How to manually e2e-test each EDT-MCP server tool against a live EDT workbench + TestConfiguration.
When should I use Edt MCP Testing?
Edt MCP Testing fits situations like: validating an MCP tool end-to-end by actually calling it (for build/unit tests see edt-mcp-build-test); tasks that involve MCP servers; tasks that involve End-to-end testing.
How do I install Edt MCP Testing in Claude Code?
Run `npx skills add DitriXNew/EDT-MCP --skill edt-mcp-testing -a claude-code`. Or copy the skill folder (.claude/skills/edt-mcp-testing in DitriXNew/EDT-MCP) into .claude/skills/edt-mcp-testing in your project. Claude Code loads it when a task matches its description.
How do I install Edt MCP Testing in Codex?
Run `npx skills add DitriXNew/EDT-MCP --skill edt-mcp-testing -a codex`. Or copy the skill folder (.claude/skills/edt-mcp-testing in DitriXNew/EDT-MCP) into .agents/skills/edt-mcp-testing in your project. Codex loads it when a task matches its description.
Can I use Edt MCP Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DitriXNew/EDT-MCP --skill edt-mcp-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/edt-mcp-testing, .gemini/skills/edt-mcp-testing, .github/skills/edt-mcp-testing and .opencode/skills/edt-mcp-testing in your project.
What does Edt MCP Testing need to run?
Going by SKILL.md and its folder, Edt MCP Testing needs the command-line tools its instructions call (git, pwsh and bash).
Does Edt MCP Testing access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Edt MCP Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Edt MCP Testing use?
Edt MCP Testing is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Edt MCP Testing use?
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 91k tokens, read only when the agent opens those files.
What are the alternatives to Edt MCP Testing?
Skills that share tags, products or a category with Edt MCP Testing: Frontmcp Testing (agentfront/frontmcp, 146 stars), Qwen Code E2E Testing (QwenLM/qwen-code, 28k stars), Adding LLM MCP Tools (TriliumNext/Trilium, 38k stars) and Exploring The Wizard (PostHog/wizard, 197 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Edt MCP Testing?
DitriXNew (a GitHub user) maintains it in DitriXNew/EDT-MCP, which has 295 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.
Source: DitriXNew/EDT-MCP on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.