MCP Server
emdly
com.emdly/emdly
What this MCP does
Searches, installs and submits Markdown skills for AI agents and manages private Markdown-based Brain files.
Capabilities
Tools
9
tools
brain_get
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.
Input schema
{'type': 'object', 'required': ['name'], 'properties': {'name': {'type': 'string', 'description': 'File name including .md'}, 'brain': {'type': 'string', 'description': 'Optional brain to read from (owner-handle/name for shared brains). Omit to search all your brains.'}}}
brain_list
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 shared with members, and when it changed.
Input schema
{'type': 'object', 'properties': {'brain': {'type': 'string', 'description': 'Optional brain name; for a brain shared with you, owner-handle/name (e.g. jan/Team). Omit to list every brain.'}, 'folder': {'type': 'string', 'description': 'Optional folder filter, e.g. Engineering.'}}}
brain_search
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 query is matched on its own, case-insensitively, and files are ranked by how many words hit. Returns the matching files with the surrounding lines so you can decide what to brain_get. Needs a signed-in user.
Input schema
{'type': 'object', 'required': ['query'], 'properties': {'brain': {'type': 'string', 'description': 'Optional brain to search (owner-handle/name for shared brains). Omit to search all.'}, 'query': {'type': 'string', 'description': 'Keywords to look for; each word is matched on its own, case-insensitively.'}}}
brain_write
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 refused — the Brain is memory, not a vault. Needs your agent bearer token.
Input schema
{'type': 'object', 'required': ['name', 'body'], 'properties': {'body': {'type': 'string', 'description': 'Markdown content.'}, 'mode': {'type': 'string', 'description': 'replace (default) or append.'}, 'name': {'type': 'string', 'description': 'File name ending in .md, e.g. customer-faq.md'}, 'brain': {'type': 'string', 'description': 'Brain to write into (owner-handle/name for shared brains, needs editor access). Omit for your default brain.'}, 'folder': {'type': 'string', 'description': 'Folder, e.g. Company. New files default to "Agent".'}}}
get_collection
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).
Input schema
{'type': 'object', 'properties': {'collection': {'type': 'string', 'description': 'Collection slug, e.g. laravel-starter. Omit to list all collections.'}}}
get_skill
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.
Input schema
{'type': 'object', 'required': ['skill'], 'properties': {'skill': {'type': 'string', 'description': 'owner/name, e.g. opsmith/jira-ticket-scorer'}, 'version': {'type': 'integer', 'description': 'Pin a version number; omit for latest.'}}}
install_skill
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 /<name> in every project; other agents: ./skills/<name>.md) and tell the user where it is. Counts the install. Use target=hermes for Hermes Agent, target=generic for any other agent, scope=project to keep a skill inside the current Claude Code project only (.claude/skills, committable for the team). When emdly agent hosting is enabled and you have a hosted agent, pass agent= to install there instead.
Input schema
{'type': 'object', 'required': ['skill'], 'properties': {'agent': {'type': 'string', 'description': 'Hosted agent name (only when emdly agent hosting is enabled and you have one).'}, 'scope': {'enum': ['project', 'user'], 'type': 'string', 'description': 'Claude Code only: user (default, ~/.claude/skills, available in every project) or project (.claude/skills in the current project — only when the user asks for a project-local install).'}, 'skill': {'type': 'string', 'description': 'owner/name, e.g. opsmith/jira-ticket-scorer'}, 'target': {'enum': ['claude-code', 'generic', 'hermes'], 'type': 'string', 'description': 'Where the file goes: claude-code (default) → ~/.claude/skills/<name>/SKILL.md; hermes → ~/.hermes/skills/<category>/<name>/SKILL.md; generic → ./skills/<name>.md.'}}}
search_skills
Search Skills
Use this FIRST, before any non-trivial task, to find a ready-made skill in the emdly catalog (reviewed Markdown playbooks for AI agents). Query with 1–3 short keywords naming the kind of work (e.g. "code review", "jira", "seo audit"); words are matched independently, so a sentence works too. If the result is empty, retry with a single noun, or send an empty query for the top skills. Returns ranked skills with their owner/name id, category, description and install command.
Input schema
{'type': 'object', 'required': ['query'], 'properties': {'query': {'type': 'string', 'description': '1–3 short keywords for the kind of work (each word is matched on its own against name, description, tags, category and author). Empty = the most popular skills.'}, 'category': {'type': 'string', 'description': 'Optional category slug or name, e.g. code-review.'}}}
submit_skill
Submit Skill
Submit a skill to emdly 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 is published by this tool; you get the check results back. The body must be a complete Markdown skill with a title and a "## License" section (MIT recommended).
Input schema
{'type': 'object', 'required': ['name', 'body'], 'properties': {'body': {'type': 'string', 'description': 'Full Markdown: # title, when to use, rules, output format, ## License'}, 'name': {'type': 'string', 'description': 'kebab-case skill name, unique within your account'}, 'note': {'type': 'string', 'description': 'Release note when submitting a new version of an existing skill.'}, 'category': {'type': 'string', 'description': 'Category name; required for a new skill.'}}}
History
Recent tool changes
Changed
install_skill
Sept. 21, 2026, 2:59 a.m.
Added
brain_write
Sept. 17, 2026, 12:34 p.m.
Added
brain_get
Sept. 17, 2026, 12:34 p.m.
Added
brain_search
Sept. 17, 2026, 12:34 p.m.
Added
brain_list
Sept. 17, 2026, 12:34 p.m.
Added
submit_skill
Sept. 17, 2026, 12:34 p.m.
Added
get_collection
Sept. 17, 2026, 12:34 p.m.
Added
install_skill
Sept. 17, 2026, 12:34 p.m.
Added
get_skill
Sept. 17, 2026, 12:34 p.m.
Added
search_skills
Sept. 17, 2026, 12:34 p.m.
Discover
Similar MCP servers
cypher-mcp
io.github.lonniev/cypher-mcp
Provides named Cypher graph queries and code-orientation tools for tracing capabilities, symbols, invariants, provenance, changes…
canton-ccpedia
io.github.UnityNodes/canton-ccpedia
Searches and explains Canton Network and Daml documentation, governance proposals, forums, code examples, APIs, releases, and eco…
ALM X++ MCP Server
io.github.alimbenhelal-pro/alm-xpp-mcp
Supports D365 Finance and Operations development with X++ and AOT search, code analysis, Azure DevOps workflows, telemetry querie…
Kaiku
tech.kaiku/kaiku
Manages team issues, comments, attachments, projects, wiki pages, and related development workflows.
api-evangelist
com.apievangelist/api-evangelist
Provides API governance analysis, OpenAPI overlays and version diffs, security-sensitive field classification, code samples, matu…
Forge Engine
app.forgeengine/forge
Manages software design specifications, systems, milestones, tasks, code mappings, project decisions, UI screens, and implementat…
Avalanche AVAX MCP
io.github.Airpote/avalanche-docs
Searches and retrieves Avalanche documentation, community proposals, CLI guidance, Builder Console workflows, blockchain identifi…
Github
io.github.pipeworx-io/github
Reads public GitHub repository files, releases, commits, issues, repository metadata, user profiles, and trending repositories.