ecomdly MCP server

• Registry namecom.ecomdly/ecomdlyverified in the MCP registry

The registry name sits under ecomdly.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-13
• Tools15
• Server calls itselfecomdly
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 329 ms.

• search_skills

  Use this FIRST, before any non-trivial task, to find a ready-made skill in the ecomdly catalog (reviewed Markdown playbooks for AI agents). Query with 1–3 short keywords naming the kind of work (e.g. "product feed", "shopping", "ga4…

• get_skill

  Read a skill's Markdown to inspect it (does not install anything). To install, call install_skill — it returns the file plus the exact path to write it to. Pass version to pin one.

• install_skill

  Install a skill into the agent you are running in. Returns the complete skill file and the exact path to write it to — YOU must then create that file verbatim (Claude Code: ~/.claude/skills/<name>/SKILL.md, so it becomes available as…

• get_collection

  Curated bundles of skills. Without an argument: list the available collections (slug, name, size). With a slug: the skills in that collection, in order — then call install_skill for each one the user wants (usually all).

• submit_skill

  Submit a skill to ecomdly for review (needs sign-in). Creates it under your account — or a new version if you already own one with this name — runs the automated checks and the AI safety scan, and queues it for a human reviewer. Nothing…

• brain_list

  List the files in your Brains (named sets of private Markdown memory), including brains shared with you. Needs your agent bearer token. Returns the brain, your role in it, name, folder, size, whether the file is in the agent context and…

• brain_search

  Use this BEFORE answering anything about the user's own context — their projects, conventions, decisions, people, infrastructure, past work. Searches the user's Brain files (their brains plus those shared with them); every word of the…

• brain_get

  Read one Brain file by name (e.g. coding-conventions.md), across your brains and brains shared with you. Needs your agent bearer token.

• brain_write

  Create or update a Brain file. Writes to your default brain unless you name one; shared brains need editor access. Replaces the whole body (use mode "append" to add to the end); the previous body is kept as a version. Credentials are…

• brain_create

  Create a new Brain — a named set of private Markdown memory, e.g. for a project, a client or a store — owned by you. Then write files into it with brain_write and brain set to its name. Needs a signed-in user or a bearer token; a hosted…

• github_repos

  List the GitHub repositories you can work with: the ones the Eco GitHub App was installed on. Returns owner/name, whether it is private, the default branch and the description.

• github_read

  Read a file, or list a directory, in a GitHub repository you connected. Give repo as owner/name, a path (empty for the root) and optionally a branch, tag or commit as ref. Text files up to 1 MB; binary files are refused.

• github_search

  Search the code of one GitHub repository you connected (default branch only, as GitHub indexes it). Returns matching file paths with a short matching fragment. Read a file with github_read.

• github_create_issue

  Open an issue in a GitHub repository you connected: a finding, a proposal or a to-do for the team. The issue says it came from Eco. Nothing in the code changes.

• github_propose_change

  Propose a change to a GitHub repository you connected as a pull request: creates a new eco/… branch from the base branch, commits the files you give (full new content per file) and opens a pull request for a person to review and merge…