Athenode
NPM · @ATHENODE/CLI
Spec-driven development for AI coding agents: specs, skills, agents, rules and MCP servers.
Available components
Last scanned (15 hours ago)
Scores higher than 42% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 4.6.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 39 of 115 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 21 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 15625 tokens (~248/item across 63 items; 63 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 9 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "library_merge_preview" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 64 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +5
- Stability: fail → pass ▲ security
- 19 Nov 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 75 to 69.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 68 to 72.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 62 to 65.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 55 to 58.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 45 to 48.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 38 to 42.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 32 to 35.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@athenode/cli@0.10.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 115 packages
| Packages resolved | 115 |
|---|---|
| Stale | 39 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agents_create Create agent ~422
Create an agent and attach it to the installed plugin. `prompt` is the inline prompt/instructions; `description` is usually required metadata, and missing required metadata fails instead of prompting. Then regenerates the installed plugin locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`, whose `pluginChanges` lists the tools whose plugin package or declaration was rewritten, with `suppressedIn` naming another tool's local settings file the plugin was switched off in; `missingEnvVars` is checked against the MCP server's environment, not your shell). If regeneration fails, the backend change is still saved and the tool returns an error. Requires an installed plugin (`npx @athenode/cli init`), unless `pluginId` names another plugin of the project: that one is changed on the server only, with no local regeneration.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Agent description. |
| metadata | object | – | Metadata fields to set, as {key: value}; "<target>.<field>" sets a per-target field (target: claudecode, codexcli, cursor, copilot, copilotcli, opencode, antigravity-ide, antigravity-cli, devin, juni… |
| name | string | yes | Agent name. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
| prompt | string | – | Inline prompt/instructions content (CLI: --prompt). |
No output schema declared.
No examples provided.
agents_list List agents ~79
List the agents attached to the installed plugin (not the whole catalog). `pluginId` targets another plugin of the project instead of the installed one. Returns an array ({items} in structuredContent).
| Name | Type | Req | Description |
|---|---|---|---|
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
No output schema declared.
No examples provided.
agents_remove Remove agent ~272
Detach an agent (by name, or id with `byId`) from the installed plugin without confirmation, removing its generated files; the server deletes the row itself once no plugin links it any more (one another plugin still links is kept). Then regenerates the installed plugin locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`, whose `pluginChanges` lists the tools whose plugin package or declaration was rewritten, with `suppressedIn` naming another tool's local settings file the plugin was switched off in; `missingEnvVars` is checked against the MCP server's environment, not your shell). If regeneration fails, the backend change is still saved and the tool returns an error. Requires an installed plugin (`npx @athenode/cli init`), unless `pluginId` names another plugin of the project: that one is changed on the server only, with no local regeneration.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `identifier` is a backend id, not a name (CLI: --by-id). |
| identifier | string | yes | Agent name, or its backend id with byId. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
No output schema declared.
No examples provided.
agents_update Update agent ~523
Fork-update an agent of the installed plugin (by name, or id with `byId`): a new backend row gets the changes, keeping unchanged fields and metadata, and replaces the old row in the plugin in the same request; the server deletes the old row unless another plugin still links it. A `rename` to the name of another one in the plugin is refused (409, code `agent_name_conflict`) and changes nothing. Then regenerates the installed plugin locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`, whose `pluginChanges` lists the tools whose plugin package or declaration was rewritten, with `suppressedIn` naming another tool's local settings file the plugin was switched off in; `missingEnvVars` is checked against the MCP server's environment, not your shell). If regeneration fails, the backend change is still saved and the tool returns an error. Requires an installed plugin (`npx @athenode/cli init`), unless `pluginId` names another plugin of the project: that one is changed on the server only, with no local regeneration.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `identifier` is a backend id, not a name (CLI: --by-id). |
| description | string | – | New agent description. |
| identifier | string | yes | Agent name, or its backend id with byId. |
| metadata | object | – | Metadata fields to set, as {key: value}; "<target>.<field>" sets a per-target field (target: claudecode, codexcli, cursor, copilot, copilotcli, opencode, antigravity-ide, antigravity-cli, devin, juni… |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
| prompt | string | – | New inline prompt content (CLI: --prompt). |
| rename | string | – | New name; the current one is kept if omitted. |
No output schema declared.
No examples provided.
library_add Add library entry as plugin ~219
Add a library entry to the project as a new plugin, a full copy of its latest version, and return the plugin. The server only is changed: no local file is written and nothing is installed (run `npx @athenode/cli init --plugin <id or slug>` to install it, both of which are in the result). A name the project already uses is refused with code `plugin_name_conflict` and a free `suggestedName`. `entry` is the entry's exact name (matched case-insensitively, surrounding spaces ignored), or its id with `byId: true`; a value that looks like an id is still taken as a name without `byId`.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `entry` is an entry id, not a name (CLI: --by-id). |
| entry | string | yes | Library entry name, or its id with byId. |
| name | string | – | The new plugin's name, at most 200 characters; the entry's name if omitted. |
No output schema declared.
No examples provided.
library_edit Edit library entry ~683
Change a library entry's name, description, category and/or public display (at least one); omitted fields keep their value and no version is created. `description: ""` clears the description, and a given `category` replaces the current one. Public display shows the entry's name, description and category and the full content of its agents, skills with their bundle files, rules and plugin files on the open web, without an account, where search engines can index them. Its MCP server configuration is public too: anyone can install the entry, MCP servers included, without an account with `npx @athenode/cli use <slug>`, so MCP values must stay ${VAR} references. After it is turned off, the entry can stay on the public site for up to a day and longer in search engines' caches. So `publicDisplay: true` needs `confirmPublic: true`, even when the entry already has it on, and is refused without it before anything is sent; ask the user specifically about public display before setting it. `publicDisplay: false` needs no confirmation. Turning it on for an entry an administrator excluded from the public site is refused with code `library_public_display_banned`. Allowed for those who may manage the entry. `entry` is the entry's exact name (matched case-insensitively, surrounding spaces ignored), or its id with `byId: true`; a value that looks like an id is still taken as a name without `byId`.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `entry` is an entry id, not a name (CLI: --by-id). |
| category | string | – | The entry's new category (CLI: --category); kept when omitted. One of: programming, testing-qa, security, devops, design, productivity, other. |
| confirmPublic | boolean | – | Confirms turning public display on (CLI: --confirm-public); required with `publicDisplay: true`, no change by itself. Publishing makes the plugin's agents, skills, MCP servers, files and rules visibl… |
| description | string | – | The new description; "" clears it. |
| entry | string | yes | Library entry name, or its id with byId. |
| name | string | – | The entry's new name. |
| publicDisplay | boolean | – | Turns public display on (`true`, which needs `confirmPublic: true`) or off (`false`); omitted, the entry keeps its setting. Unlike `confirmPublic: false`, which equals an omitted one, `false` is a ch… |
No output schema declared.
No examples provided.
library_get Get library entry ~164
Get one library entry: its metadata, versions and the agents, skills (with their bundle files as `{path, isText}`; `isText: false` is a binary file), MCP servers and files of its latest version, without their texts (read those with library_item). Item ids change with every published version. `entry` is the entry's exact name (matched case-insensitively, surrounding spaces ignored), or its id with `byId: true`; a value that looks like an id is still taken as a name without `byId`.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `entry` is an entry id, not a name (CLI: --by-id). |
| entry | string | yes | Library entry name, or its id with byId. |
No output schema declared.
No examples provided.
library_item Get library entry item ~257
Read the content of one item of a library entry's latest version. `agent`, `skill` and `mcp-server` need `itemId` (from library_get, or a merge preview's `libraryItemId`); `file` needs `path`; `skill-file` needs `itemId` (the skill) and `path`, returns `{path, content}` and refuses a binary file; `rules` needs neither. Any other combination is refused. Items are not addressed by name: names are not unique inside an entry. `entry` is the entry's exact name (matched case-insensitively, surrounding spaces ignored), or its id with `byId: true`; a value that looks like an id is still taken as a name without `byId`.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `entry` is an entry id, not a name (CLI: --by-id). |
| entry | string | yes | Library entry name, or its id with byId. |
| itemId | string | – | Item id inside the entry (CLI: --item-id). |
| kind | string | yes | Item kind. |
| path | string | – | Path of the plugin file, or of the file inside the skill. |
No output schema declared.
No examples provided.
library_list List library entries ~161
List or search the public plugin library, one page at a time, most liked first. Returns `{items, nextCursor}` with no total; for the next page pass `nextCursor` as `cursor` with the same `query` and `category` (a cursor is invalid with other values). Readable with any project token.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only entries of this category (CLI: --category). One of: programming, testing-qa, security, devops, design, productivity, other. |
| cursor | string | – | The nextCursor of the previous page. |
| limit | integer | – | Page size, 1 to 100; 20 if omitted. |
| query | string | – | Search text (CLI: --query). |
No output schema declared.
No examples provided.
library_merge Merge library entry into plugin ~579
Merge a library entry's latest version into a plugin, in one transaction, and return what was added and replaced per kind. Without `decisions` (safe mode) it previews and applies in one call: every new item is added, nothing is replaced and the rules are kept. `decisions` is an object in the preview's shape: `entryVersion` and `fingerprint` from the preview, and per kind (`skills`, `agents`, `mcpServers`, `files`) the lists `add` and `replace` of `{name}` items (`{path}` for files). A kind without an `add` list adds everything new; a present `add` list, even an empty one, adds exactly its items. `replace` overwrites conflicting items of the plugin and needs `confirmReplace: true`. `rules` is `keep` (default), `append` or `replace`. A whole preview may be passed back as `decisions`: it adds every new item and replaces nothing. A `library_merge_stale` error means the plugin or the entry changed since the preview: repeat the preview and apply with its values. A refusal writes nothing. `decisions.entryId`, when present, must be this entry. `entry` is the entry's exact name (matched case-insensitively, surrounding spaces ignored), or its id with `byId: true`; a value that looks like an id is still taken as a name without `byId`. `plugin` is required and is the plugin's exact, case-sensitive name, or its id with `pluginById: true` (see plugins_list); the installed plugin is never assumed. When `plugin` is the installed plugin, it is then regenerated locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`); if that fails, the backend change is still saved and the tool returns an error. Any other plugin is changed on the server only.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `entry` is an entry id, not a name (CLI: --by-id). |
| decisions | object | – | Decisions in the preview's shape: {entryVersion, fingerprint, confirmReplace?, skills?, agents?, mcpServers?, files?, rules?}, each kind as {add?: [...], replace?: [...]} and rules one of keep | appe… |
| entry | string | yes | Library entry name, or its id with byId. |
| plugin | string | yes | Name of the plugin to act on, or its id with pluginById (CLI: --plugin). Required. |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
No output schema declared.
No examples provided.
library_merge_preview Preview library merge ~285
Preview merging a library entry's latest version into a plugin, changing nothing: per kind the items it would `add`, those in `conflict` with the plugin (and whether they are `replaceable`) and the `identical` ones, the state of the rules, and the `entryVersion` and `fingerprint` that library_merge needs with decisions. Compare both sides of a conflict with library_item and the plugin's own tools. `entry` is the entry's exact name (matched case-insensitively, surrounding spaces ignored), or its id with `byId: true`; a value that looks like an id is still taken as a name without `byId`. `plugin` is required and is the plugin's exact, case-sensitive name, or its id with `pluginById: true` (see plugins_list); the installed plugin is never assumed.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `entry` is an entry id, not a name (CLI: --by-id). |
| entry | string | yes | Library entry name, or its id with byId. |
| plugin | string | yes | Name of the plugin to act on, or its id with pluginById (CLI: --plugin). Required. |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
No output schema declared.
No examples provided.
library_publish Publish plugin to library ~948
Publish a plugin to the plugin library: a new entry, or a new version of the entry the plugin already has. Publishing makes the plugin's agents, skills, MCP servers, files and rules visible to every signed-in Athenode user and turns the entry's public display on, unless an administrator made public display unavailable for the entry. Public display shows the entry's name, description and category and the full content of its agents, skills with their bundle files, rules and plugin files on the open web, without an account, where search engines can index them. Its MCP server configuration is public too: anyone can install the entry, MCP servers included, without an account with `npx @athenode/cli use <slug>`, so MCP values must stay ${VAR} references. After it is turned off, the entry can stay on the public site for up to a day and longer in search engines' caches. So publishing needs the explicit `confirmPublic: true`, the one consent to both; ask the user before setting it, naming the open web, and there is no `publicDisplay` here (to turn public display off afterwards use library_edit). Without `confirmPublic: true` nothing is published: the result is `{published: false, preview, problem}` with a warning, and a second one when an administrator excluded the entry from the public site (`publicDisplayBanned: true`: it is then published to the in-app library only; tell the user before confirming); the preview lists the items as `{id, name}` / `{id, path}` objects, and `problem` (`{status, code, field, error}`, else `null`) is the first refusal the publish would get: an invalid name, description, note or category, a first publish without a category (`library_entry_category_required`), or a name another entry has (`library_entry_name_taken`), which a confirmed publish answers as an error. A first publish beyond the plan's library entry limit (3 entries on the Free plan) is such a refusal too: `problem` in the preview, an error when confirmed (402 `plan_limit_exceeded`, l…
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | The entry's category (CLI: --category): required for a new entry, kept by a new version when omitted. One of: programming, testing-qa, security, devops, design, productivity, other. |
| confirmPublic | boolean | – | Confirms what becomes visible, public display included (CLI: --confirm-public). Required to publish. Publishing makes the plugin's agents, skills, MCP servers, files and rules visible to every signed… |
| description | string | – | The entry's description. |
| name | string | – | The entry's name; the plugin's name (or the entry's current one) if omitted. |
| note | string | – | A note for the published version. |
| plugin | string | yes | Name of the plugin to act on, or its id with pluginById (CLI: --plugin). Required. |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
No output schema declared.
No examples provided.
library_unpublish Unpublish library entry ~139
Unpublish a library entry immediately, without confirmation: the entry and all its versions are removed from the library. Plugins already added from it are kept. Allowed for those who may manage the entry. `entry` is the entry's exact name (matched case-insensitively, surrounding spaces ignored), or its id with `byId: true`; a value that looks like an id is still taken as a name without `byId`.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `entry` is an entry id, not a name (CLI: --by-id). |
| entry | string | yes | Library entry name, or its id with byId. |
No output schema declared.
No examples provided.
library_update Update plugin from library ~500
Update a plugin that was added from the library to the latest version of its origin entry, in one transaction, and return what was added and replaced per kind; the plugin is then recorded at that version. Without `decisions` (safe mode) it previews and applies in one call: every new item is added, nothing is replaced and the rules are kept. `decisions` is an object in the preview's shape: `entryVersion` and `fingerprint` from the preview, and per kind (`skills`, `agents`, `mcpServers`, `files`) the lists `add` and `replace` of `{name}` items (`{path}` for files). A kind without an `add` list adds everything new; a present `add` list, even an empty one, adds exactly its items. `replace` overwrites conflicting items of the plugin and needs `confirmReplace: true`. `rules` is `keep` (default), `append` or `replace`. A whole preview may be passed back as `decisions`: it adds every new item and replaces nothing. A `library_merge_stale` error means the plugin or the entry changed since the preview: repeat the preview and apply with its values. A refusal writes nothing. Take the decisions' values from library_update_preview. `plugin` is required and is the plugin's exact, case-sensitive name, or its id with `pluginById: true` (see plugins_list); the installed plugin is never assumed. When `plugin` is the installed plugin, it is then regenerated locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`); if that fails, the backend change is still saved and the tool returns an error. Any other plugin is changed on the server only.
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | object | – | Decisions in the preview's shape: {entryVersion, fingerprint, confirmReplace?, skills?, agents?, mcpServers?, files?, rules?}, each kind as {add?: [...], replace?: [...]} and rules one of keep | appe… |
| plugin | string | yes | Name of the plugin to act on, or its id with pluginById (CLI: --plugin). Required. |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
No output schema declared.
No examples provided.
library_update_preview Preview library update ~179
Preview updating a plugin that was added from the library to the latest version of its origin entry, changing nothing: the same result as library_merge_preview for that entry. Refused with code `library_update_no_origin` for a plugin that has no origin entry and `library_update_not_available` for one already at the latest version (plugins_list shows `libraryOrigin.updateAvailable`). `plugin` is required and is the plugin's exact, case-sensitive name, or its id with `pluginById: true` (see plugins_list); the installed plugin is never assumed.
| Name | Type | Req | Description |
|---|---|---|---|
| plugin | string | yes | Name of the plugin to act on, or its id with pluginById (CLI: --plugin). Required. |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
No output schema declared.
No examples provided.
mcp_servers_create Create MCP server ~355
Create a plugin-level MCP server on the installed plugin: `command`, `args` and `env` for "stdio", `url` and `headers` for "http"/"sse" (the other transport's fields are ignored). Values may reference environment variables as ${VAR}. Then regenerates the installed plugin locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`, whose `pluginChanges` lists the tools whose plugin package or declaration was rewritten, with `suppressedIn` naming another tool's local settings file the plugin was switched off in; `missingEnvVars` is checked against the MCP server's environment, not your shell). If regeneration fails, the backend change is still saved and the tool returns an error. Requires an installed plugin (`npx @athenode/cli init`), unless `pluginId` names another plugin of the project: that one is changed on the server only, with no local regeneration.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Arguments of the command (stdio; CLI: --arg, repeatable). |
| command | string | – | Command to run (stdio). |
| env | object | – | Environment variables, as {KEY: value} (stdio; CLI: --env). |
| headers | object | – | HTTP headers, as {Name: value} (http/sse; CLI: --header). |
| name | string | yes | MCP server name. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
| transport | string | yes | MCP server transport. |
| url | string | – | Server URL (http/sse). |
No output schema declared.
No examples provided.
mcp_servers_list List MCP servers ~78
List the plugin-level MCP servers of the installed plugin. `pluginId` targets another plugin of the project instead of the installed one. Returns an array ({items} in structuredContent).
| Name | Type | Req | Description |
|---|---|---|---|
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
No output schema declared.
No examples provided.
mcp_servers_remove Remove MCP server ~256
Delete a plugin-level MCP server (by name, or id with `byId`) without confirmation, removing its entries from the local MCP config files. Then regenerates the installed plugin locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`, whose `pluginChanges` lists the tools whose plugin package or declaration was rewritten, with `suppressedIn` naming another tool's local settings file the plugin was switched off in; `missingEnvVars` is checked against the MCP server's environment, not your shell). If regeneration fails, the backend change is still saved and the tool returns an error. Requires an installed plugin (`npx @athenode/cli init`), unless `pluginId` names another plugin of the project: that one is changed on the server only, with no local regeneration.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `identifier` is a backend id, not a name (CLI: --by-id). |
| identifier | string | yes | MCP server name, or its backend id with byId. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
No output schema declared.
No examples provided.
mcp_servers_update Update MCP server ~383
Update a plugin-level MCP server (by name, or id with `byId`) in place. Omitted fields keep their value; a given `args`, `env` or `headers` replaces the whole value, so include every entry to keep. Switching the transport drops the old transport's fields. Then regenerates the installed plugin locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`, whose `pluginChanges` lists the tools whose plugin package or declaration was rewritten, with `suppressedIn` naming another tool's local settings file the plugin was switched off in; `missingEnvVars` is checked against the MCP server's environment, not your shell). If regeneration fails, the backend change is still saved and the tool returns an error. Requires an installed plugin (`npx @athenode/cli init`), unless `pluginId` names another plugin of the project: that one is changed on the server only, with no local regeneration.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | New arguments (stdio); replaces the current list. |
| byId | boolean | – | `identifier` is a backend id, not a name (CLI: --by-id). |
| command | string | – | New command (stdio). |
| env | object | – | New environment variables (stdio); replaces the current map. |
| headers | object | – | New HTTP headers (http/sse); replaces the current map. |
| identifier | string | yes | MCP server name, or its backend id with byId. |
| name | string | – | New MCP server name. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
| transport | string | – | New transport. |
| url | string | – | New URL (http/sse). |
No output schema declared.
No examples provided.
plugins_clone Clone plugin ~291
Clone a plugin under a new name in the project, keeping its description. The whole plugin is copied: agents and skills as independent copies, rules, files and the MCP servers with their stored `env`/`headers` values. It counts against the plan limits (plugins, and agents, skills and MCP servers per plugin); a breach creates nothing. `source` is a plugin name, or an id with `byId: true`. The installed plugin is not changed. Without `slug` the server derives one from the new name. A `slug` is refused, writing nothing, with code `plugin_slug_conflict` (409: another plugin of the project has it), `plugin_slug_forbidden` (a reserved slug), `plugin_slug_locked` (the slug of this plugin cannot be changed) or `plugin_slug_invalid` (not a valid slug).
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | The given value is a plugin id, not a name (CLI: --by-id <id>). |
| name | string | yes | The new cloned plugin's name, at most 200 characters. |
| slug | string | – | The new cloned plugin's slug (CLI: --slug). Unique in the project; it is the name of the plugin package and the prefix of its commands. |
| source | string | yes | Name (or, with byId, id) of the plugin to clone. |
No output schema declared.
No examples provided.
plugins_create Create plugin ~169
Create an empty plugin in the project. Without `slug` the server derives one from the name. A `slug` is refused, writing nothing, with code `plugin_slug_conflict` (409: another plugin of the project has it), `plugin_slug_forbidden` (a reserved slug), `plugin_slug_locked` (the slug of this plugin cannot be changed) or `plugin_slug_invalid` (not a valid slug).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | The new plugin's description, at most 25000 characters. |
| name | string | yes | The new plugin's name, at most 200 characters. |
| slug | string | – | The new plugin's slug (CLI: --slug). Unique in the project; it is the name of the plugin package and the prefix of its commands. |
No output schema declared.
No examples provided.
plugins_delete Delete plugin ~93
Delete a plugin immediately, without confirmation. `target` is a plugin name, or an id with `byId: true`. Deleting the installed plugin adds a warning.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | The given value is a plugin id, not a name (CLI: --by-id <id>). |
| target | string | yes | Name (or, with byId, id) of the plugin to delete. |
No output schema declared.
No examples provided.
plugins_external_import Import external plugin ~630
Import an external plugin. Without `plugin` into a new plugin, with `slug` and `name` or the proposed ones (nothing is regenerated); a package with several plugins needs `pick`. With `plugin` (its exact name, or its id with `pluginById`) it is merged into that plugin: without `decisions` (safe mode) every new item is added, nothing is replaced and the rules are kept; `decisions` is the merge preview's shape (`previewId`, `sourceFingerprint`, `fingerprint`, per kind `add`/`replace` of `{name}` items, `confirmReplace`, `rules` keep | append | replace for the external plugin's AGENTS.md). The plugin records the external plugin as a source (plugins_external_sources) for later updates. `source` is a public GitHub or GitLab repository URL (a tree URL picks a ref and a sub-folder), or the path of a local external plugin folder, resolved against the project root, which is zipped (without .git, node_modules and links) and uploaded. Formats: Agent Plugins (`plugin.json`), Claude Code plugins (`.claude-plugin/plugin.json`), marketplaces and `plugins/*` folders; skills, agents, MCP servers and the root `AGENTS.md` (as the rules) are imported, hooks, commands and the like are listed as ignored. A `slug` is refused, writing nothing, with code `plugin_slug_conflict` (409: another plugin of the project has it), `plugin_slug_forbidden` (a reserved slug), `plugin_slug_locked` (the slug of this plugin cannot be changed) or `plugin_slug_invalid` (not a valid slug). When `plugin` is the installed plugin, it is then regenerated locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`); if that fails, the backend change is still saved and the tool returns an error. Any other plugin is changed on the server only.
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | object | – | Decisions of a merge into `plugin`: {previewId?, sourceFingerprint, fingerprint, confirmReplace?, skills?, agents?, mcpServers?, rules?} (CLI: --decisions). Safe mode if omitted. |
| name | string | – | The new plugin's name, at most 200 characters. |
| pick | string | – | The external plugin to import of a package that offers several (a marketplace or a plugins/ folder) (CLI: --pick). |
| plugin | string | – | Name of the plugin, or its id with pluginById (CLI: --plugin). |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
| slug | string | – | The new plugin's slug (CLI: --slug). Unique in the project; it is the name of the plugin package and the prefix of its commands. |
| source | string | yes | Repository URL, or the path of a local external plugin folder. |
No output schema declared.
No examples provided.
plugins_external_import_preview Preview external plugin import ~349
Preview importing an external plugin, changing no plugin of the project: the plugins its package offers (`candidates`; `picked` is null while one must be chosen with `pick`), what the picked one brings (skills, agents, MCP servers, rules), its licence and attribution, `warnings`, `ignored` parts and the proposed slug and name of a new plugin. With `plugin` also the merge preview into that plugin (`merge`), whose `previewId`, `sourceFingerprint` and `fingerprint` plugins_external_import takes as decisions. A preview expires after an hour. `source` is a public GitHub or GitLab repository URL (a tree URL picks a ref and a sub-folder), or the path of a local external plugin folder, resolved against the project root, which is zipped (without .git, node_modules and links) and uploaded. Formats: Agent Plugins (`plugin.json`), Claude Code plugins (`.claude-plugin/plugin.json`), marketplaces and `plugins/*` folders; skills, agents, MCP servers and the root `AGENTS.md` (as the rules) are imported, hooks, commands and the like are listed as ignored.
| Name | Type | Req | Description |
|---|---|---|---|
| pick | string | – | The external plugin to import of a package that offers several (a marketplace or a plugins/ folder) (CLI: --pick). |
| plugin | string | – | Name of the plugin, or its id with pluginById (CLI: --plugin). |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
| source | string | yes | Repository URL, or the path of a local external plugin folder. |
No output schema declared.
No examples provided.
plugins_external_sources List external plugin sources ~113
List the external plugins a plugin was imported from: the URL and revision or the uploaded zip, the external plugin's name, licence class and the items it owns in the plugin. The installed plugin without `plugin`. Returns an array ({items} in structuredContent).
| Name | Type | Req | Description |
|---|---|---|---|
| plugin | string | – | Name of the plugin, or its id with pluginById (CLI: --plugin). |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
No output schema declared.
No examples provided.
plugins_external_update Update external plugin ~433
Update an external plugin source of a plugin to its new version. Without `decisions` (safe mode) it checks and applies: every new item is added, nothing is replaced or removed, the rules are kept and the source moves to the new version; an up-to-date source changes nothing. `decisions` is the update preview's shape: `previewId`, `sourceFingerprint`, `fingerprint`, per kind (`skills`, `agents`, `mcpServers`) the lists `add`, `replace`, `remove` (delete from the plugin) and `keep` (keep as the plugin's own) of `{name}` items, `confirmReplace` (required to replace or remove) and `rules` keep | append | replace. A `library_merge_stale` error means the plugin changed since the preview: repeat it. `plugin` is required. When `plugin` is the installed plugin, it is then regenerated locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`); if that fails, the backend change is still saved and the tool returns an error. Any other plugin is changed on the server only.
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | object | – | Decisions: {previewId, sourceFingerprint, fingerprint, confirmReplace?, skills?, agents?, mcpServers?, rules?}, each kind as {add?, replace?, remove?, keep?} (CLI: --decisions). Safe mode if omitted. |
| path | string | – | Folder of the new version of an uploaded external plugin, resolved against the project root (CLI: --path); an external plugin imported from a URL is checked by its URL. |
| plugin | string | yes | Name of the plugin, or its id with pluginById (CLI: --plugin). Required. |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
| pluginSource | string | yes | The external plugin source: its id, or its name when the plugin has one source of that name (see plugins_external_sources). |
No output schema declared.
No examples provided.
plugins_external_update_preview Preview external plugin update ~257
Check an external plugin source of a plugin for a new version and preview the update, changing no item: `upToDate`, else per kind the items to `add`, those that `change` (status changed, conflict, edited, other_source or unowned), the `unchanged` ones and those the new version no longer has (`remove`), with the `previewId`, `sourceFingerprint` and `fingerprint` plugins_external_update takes as decisions. An external plugin imported from a URL is checked by its URL; an uploaded one needs `path`. `plugin` is required.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Folder of the new version of an uploaded external plugin, resolved against the project root (CLI: --path); an external plugin imported from a URL is checked by its URL. |
| plugin | string | yes | Name of the plugin, or its id with pluginById (CLI: --plugin). Required. |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
| pluginSource | string | yes | The external plugin source: its id, or its name when the plugin has one source of that name (see plugins_external_sources). |
No output schema declared.
No examples provided.
plugins_files_create Create plugin file ~160
Create a file, or a directory with `dir: true`, in the installed plugin's file tree, creating missing parents. File content is inline, at most 50000 characters; directories have no content. `pluginId` targets another plugin of the project instead of the installed one.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The file's content (empty if omitted). |
| dir | boolean | – | Create a directory instead of a file (CLI: --dir). |
| path | string | yes | Path of the new file or directory. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
| summary | string | – | Short summary of the file or directory. |
No output schema declared.
No examples provided.
plugins_files_delete Delete plugin file ~115
Delete a file or empty directory, without confirmation; a non-empty directory needs `recursive: true` and is deleted with everything under it. `pluginId` targets another plugin of the project instead of the installed one.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Path of the file or directory. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
| recursive | boolean | – | Allow deleting a non-empty directory (CLI: --recursive). |
No output schema declared.
No examples provided.
plugins_files_get Get plugin file ~109
Get one file of the installed plugin's file tree by path, with its content and summary. Workflow settings are read this way, e.g. "settings/SETTINGS.md". `pluginId` targets another plugin of the project instead of the installed one.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | File path, e.g. "settings/testing.md". |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
No output schema declared.
No examples provided.
plugins_files_list List plugin files ~115
List the files and directories directly inside a directory of the installed plugin's file tree (the project's own plugin copy), or the root without `path`. `pluginId` targets another plugin of the project instead of the installed one. Returns an array ({items} in structuredContent).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Directory path, e.g. "settings"; root if omitted. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
No output schema declared.
No examples provided.
plugins_files_update Update plugin file ~127
Replace a file's content and/or summary; only given fields change. Content is inline, at most 50000 characters. Directories cannot be updated. `pluginId` targets another plugin of the project instead of the installed one.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The file's new content. |
| path | string | yes | Path of the file. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
| summary | string|null | – | The new summary; null or "" clears it. |
No output schema declared.
No examples provided.
plugins_list List plugins ~100
List all plugins in the project, each with its `slug` (unique in the project: the name of the plugin package and the prefix of its commands). A plugin added from the plugin library has a `libraryOrigin` (`null` otherwise) naming its origin entry, its `version`, the entry's `latestVersion` and whether an update is on offer (`updateAvailable`; see library_update_preview). Returns an array ({items} in structuredContent).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plugins_pull Pull plugin into plugin ~646
Pull another plugin of the project into a plugin, in one transaction, and return what was added and replaced per kind. It is a one-time copy: skills and agents become new, independent items of the plugin, nothing is ever deleted from it, nothing about the source is recorded and no update is offered later. Without `decisions` (safe mode) it previews and applies in one call: every new item is added, nothing is replaced and the rules are kept. `decisions` is an object in the preview's shape: `sourceFingerprint` and `fingerprint` from the preview, and per kind (`skills`, `agents`, `mcpServers`, `files`) the lists `add` and `replace` of `{name}` items (`{path}` for files). A kind without an `add` list adds everything new; a present `add` list, even an empty one, adds exactly its items. `replace` overwrites conflicting items of the plugin and needs `confirmReplace: true`. `rules` is `keep` (default), `append` (under a heading with the source plugin's name) or `replace`. A whole preview may be passed back as `decisions`: it adds every new item and replaces nothing. A `library_merge_stale` error means `plugin` or `source` changed since the preview: repeat plugins_pull_preview and apply with its values. A refusal writes nothing. `source` is the plugin the content is taken from and `plugin` the one that receives it: each is the plugin's exact, case-sensitive name, or its id with `sourceById: true` / `pluginById: true` (see plugins_list). Both are required, both are plugins of the project and they must differ; the installed plugin is never assumed. A plugin of another project cannot be the source (pulling across projects exists only in the web app); for a library entry use library_merge. When `plugin` is the installed plugin, it is then regenerated locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`); if that fails, the backend change is still saved and the tool returns an error. Any other plugin is changed on the server only.
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | object | – | Decisions in the preview's shape: {sourceFingerprint, fingerprint, confirmReplace?, skills?, agents?, mcpServers?, files?, rules?}, each kind as {add?: [...], replace?: [...]} and rules one of keep |… |
| plugin | string | yes | Name of the plugin that receives the content, or its id with pluginById (CLI: --plugin). Required. |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
| source | string | yes | Name of the plugin to pull from, or its id with sourceById. Required. |
| sourceById | boolean | – | `source` is a plugin id, not a name (CLI: --source-by-id). |
No output schema declared.
No examples provided.
plugins_pull_preview Preview plugin pull ~333
Preview pulling another plugin of the project into a plugin, changing nothing: per kind (skills, agents, MCP servers, files) the items it would `add`, those in `conflict` with the plugin (and whether they are `replaceable`) and the `identical` ones, the state of the rules, and the `sourceFingerprint` and `fingerprint` that plugins_pull needs with decisions. The source is read as it is now; an item's `libraryItemId` is the id of the source plugin's item. `source` is the plugin the content is taken from and `plugin` the one that receives it: each is the plugin's exact, case-sensitive name, or its id with `sourceById: true` / `pluginById: true` (see plugins_list). Both are required, both are plugins of the project and they must differ; the installed plugin is never assumed. A plugin of another project cannot be the source (pulling across projects exists only in the web app); for a library entry use library_merge.
| Name | Type | Req | Description |
|---|---|---|---|
| plugin | string | yes | Name of the plugin that receives the content, or its id with pluginById (CLI: --plugin). Required. |
| pluginById | boolean | – | `plugin` is a plugin id, not a name (CLI: --plugin-by-id). |
| source | string | yes | Name of the plugin to pull from, or its id with sourceById. Required. |
| sourceById | boolean | – | `source` is a plugin id, not a name (CLI: --source-by-id). |
No output schema declared.
No examples provided.
plugins_update Update plugin ~305
Change a plugin's name, description and/or slug (at least one); omitted fields keep their value. `target` is a plugin name, or an id with `byId: true`, never a slug. A changed slug renames the plugin package and its commands: the result then has a warning naming the old and the new slug. It does not regenerate the install, even for the installed plugin: the local install follows at the next `athenode init` or regeneration. A `slug` is refused, writing nothing, with code `plugin_slug_conflict` (409: another plugin of the project has it), `plugin_slug_forbidden` (a reserved slug), `plugin_slug_locked` (the slug of this plugin cannot be changed) or `plugin_slug_invalid` (not a valid slug).
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | The given value is a plugin id, not a name (CLI: --by-id <id>). |
| description | string | – | The plugin's new description, at most 25000 characters. |
| name | string | – | The plugin's new name, at most 200 characters. |
| slug | string | – | The plugin's new slug (CLI: --slug); the current one is kept if omitted. Unique in the project; it is the name of the plugin package and the prefix of its commands. |
| target | string | yes | Name (or, with byId, id) of the plugin to update. |
No output schema declared.
No examples provided.
rules_get Get rules ~71
Get the rules text of the installed plugin (null when none was ever set). `pluginId` targets another plugin of the project instead of the installed one.
| Name | Type | Req | Description |
|---|---|---|---|
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
No output schema declared.
No examples provided.
rules_update Update rules ~238
Replace the whole rules text of the installed plugin; an empty string empties it. The content is literal (a leading "@" is not a file reference); over 50000 characters it adds a warning and may be rejected. Then regenerates the installed plugin locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`, whose `pluginChanges` lists the tools whose plugin package or declaration was rewritten, with `suppressedIn` naming another tool's local settings file the plugin was switched off in; `missingEnvVars` is checked against the MCP server's environment, not your shell). If regeneration fails, the backend change is still saved and the tool returns an error. Requires an installed plugin (`npx @athenode/cli init`), unless `pluginId` names another plugin of the project: that one is changed on the server only, with no local regeneration.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The full rules text. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
No output schema declared.
No examples provided.
skills_create Create skill ~421
Create a skill and attach it to the installed plugin. `prompt` is the inline SKILL.md body; `description` is usually required metadata, and missing required metadata fails instead of prompting. Then regenerates the installed plugin locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`, whose `pluginChanges` lists the tools whose plugin package or declaration was rewritten, with `suppressedIn` naming another tool's local settings file the plugin was switched off in; `missingEnvVars` is checked against the MCP server's environment, not your shell). If regeneration fails, the backend change is still saved and the tool returns an error. Requires an installed plugin (`npx @athenode/cli init`), unless `pluginId` names another plugin of the project: that one is changed on the server only, with no local regeneration.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Skill description. |
| metadata | object | – | Metadata fields to set, as {key: value}; "<target>.<field>" sets a per-target field (target: claudecode, codexcli, cursor, copilot, copilotcli, opencode, antigravity-ide, antigravity-cli, devin, juni… |
| name | string | yes | Skill name. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
| prompt | string | – | Inline prompt content (CLI: --prompt). |
No output schema declared.
No examples provided.
skills_list List skills ~79
List the skills attached to the installed plugin (not the whole catalog). `pluginId` targets another plugin of the project instead of the installed one. Returns an array ({items} in structuredContent).
| Name | Type | Req | Description |
|---|---|---|---|
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
No output schema declared.
No examples provided.
skills_remove Remove skill ~272
Detach a skill (by name, or id with `byId`) from the installed plugin without confirmation, removing its generated files; the server deletes the row itself once no plugin links it any more (one another plugin still links is kept). Then regenerates the installed plugin locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`, whose `pluginChanges` lists the tools whose plugin package or declaration was rewritten, with `suppressedIn` naming another tool's local settings file the plugin was switched off in; `missingEnvVars` is checked against the MCP server's environment, not your shell). If regeneration fails, the backend change is still saved and the tool returns an error. Requires an installed plugin (`npx @athenode/cli init`), unless `pluginId` names another plugin of the project: that one is changed on the server only, with no local regeneration.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `identifier` is a backend id, not a name (CLI: --by-id). |
| identifier | string | yes | Skill name, or its backend id with byId. |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
No output schema declared.
No examples provided.
skills_update Update skill ~523
Fork-update a skill of the installed plugin (by name, or id with `byId`): a new backend row gets the changes, keeping unchanged fields and metadata, and replaces the old row in the plugin in the same request; the server deletes the old row unless another plugin still links it. A `rename` to the name of another one in the plugin is refused (409, code `skill_name_conflict`) and changes nothing. Then regenerates the installed plugin locally, like `athenode init` without confirmation (the result adds `install` and `regeneration`, whose `pluginChanges` lists the tools whose plugin package or declaration was rewritten, with `suppressedIn` naming another tool's local settings file the plugin was switched off in; `missingEnvVars` is checked against the MCP server's environment, not your shell). If regeneration fails, the backend change is still saved and the tool returns an error. Requires an installed plugin (`npx @athenode/cli init`), unless `pluginId` names another plugin of the project: that one is changed on the server only, with no local regeneration.
| Name | Type | Req | Description |
|---|---|---|---|
| byId | boolean | – | `identifier` is a backend id, not a name (CLI: --by-id). |
| description | string | – | New skill description. |
| identifier | string | yes | Skill name, or its backend id with byId. |
| metadata | object | – | Metadata fields to set, as {key: value}; "<target>.<field>" sets a per-target field (target: claudecode, codexcli, cursor, copilot, copilotcli, opencode, antigravity-ide, antigravity-cli, devin, juni… |
| pluginId | string | – | Id of the plugin to act on (see plugins_list); the installed plugin if omitted (CLI: --plugin-id). |
| prompt | string | – | New inline prompt content (CLI: --prompt). |
| rename | string | – | New name; the current one is kept if omitted. |
No output schema declared.
No examples provided.
specs_blockers_add Add blockers ~132
Mark `id` as blocked by each of `blockerIds`, returning the updated blocker list. Adding is all-or-nothing. A blocker that is missing, in another project, the spec itself, already completed, or an ancestor or descendant is rejected with 400; a link that already exists or would create a cycle with 409, so remove wrong links before adding new ones. Children inherit their ancestors' blockers. Returns an array ({items} in structuredContent).
| Name | Type | Req | Description |
|---|---|---|---|
| blockerIds | array | yes | Ids of the specs that must be completed first. |
| id | string | yes | Specification id. |
No output schema declared.
No examples provided.
specs_blockers_list List blockers ~46
List the specifications `id` is directly blocked by (not those inherited from ancestors). Returns an array ({items} in structuredContent).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Specification id. |
No output schema declared.
No examples provided.
specs_blockers_remove Remove blocker ~66
Remove the direct link that blocks `id` by `blockerId`; 404 when no such link exists. Blockers inherited from an ancestor must be removed on that ancestor.
| Name | Type | Req | Description |
|---|---|---|---|
| blockerId | string | yes | Blocker id. |
| id | string | yes | Specification id. |
No output schema declared.
No examples provided.
specs_create Create specification ~323
Create a specification (status draft | prepared | processing | completed; content inline). `blockedBy` lists specs that must be completed first; the spec and its blockers are created atomically. Adding is all-or-nothing. A blocker that is missing, in another project, the spec itself, already completed, or an ancestor or descendant is rejected with 400; a link that already exists or would create a cycle with 409, so remove wrong links before adding new ones. Children inherit their ancestors' blockers. `todoCardId` creates the spec from a ToDo card, linking the two in the same request.
| Name | Type | Req | Description |
|---|---|---|---|
| blockedBy | array | – | Blocker ids (CLI: --blocked-by, repeatable). |
| content | string | – | Full specification content (Markdown). |
| parentId | string | – | Parent specification id (CLI: --parent). |
| status | string | – | Initial status. |
| summary | string | – | Short summary. |
| title | string | yes | Specification title. |
| todoCardId | string | – | Id of the ToDo card the specification is created from (CLI: --todo-card). The backend records the new specification as the card's resulting specification in the same request. A missing card or a card… |
No output schema declared.
No examples provided.
specs_delete Delete specification ~74
Delete a specification and all its descendants, without confirmation. Refused, listing the dependents, while other specs are blocked by it or its descendants, unless `force` is true.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Delete even when other specs depend on it (CLI: --force). |
| id | string | yes | Specification id. |
No output schema declared.
No examples provided.
specs_get Get specification ~35
Get one specification by id, with its content, status, implementation plan and direct blockers.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Specification id. |
No output schema declared.
No examples provided.
specs_get_plan Get implementation plan ~32
Get the implementation plan of a specification (null when none is set).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Specification id. |
No output schema declared.
No examples provided.
specs_list List specifications ~136
List the project's specifications, optionally filtered by status (draft | prepared | processing | completed) and scoped to a parent (`parentId`, CLI --parent) or to the top level (`topLevel`, CLI --top-level); the two are mutually exclusive. To find specs by topic, use specs_tree with `query` instead of walking this list. Returns an array ({items} in structuredContent).
| Name | Type | Req | Description |
|---|---|---|---|
| parentId | string | – | Only direct children of this id (CLI: --parent). |
| status | string | – | Filter by status. |
| topLevel | boolean | – | Only specs without a parent (CLI: --top-level). |
No output schema declared.
No examples provided.
How do I install the Athenode MCP server?
Athenode runs locally as an npm package, launched with npx -y @athenode/cli mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @athenode/cli
claude mcp add com-athenode-cli -- npx -y @athenode/cli mcp
What is the Athenode MCP server?
Athenode is an MCP server listed in the public MCP registry as com.athenode/cli. Spec-driven development for AI coding agents: specs, skills, agents, rules and MCP servers. This page covers its npm package (@athenode/cli).
Is the Athenode MCP server safe to use?
Athenode scores 71 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Athenode MCP server expose?
Athenode exposes 63 tools: specs_list, specs_search, specs_tree, specs_get, specs_create, and 58 more. Their descriptions and schemas cost roughly 15,161 tokens of context every time the server is loaded.
Is the Athenode MCP server still maintained?
Athenode is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Athenode MCP server under?
Athenode declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Athenode MCP server?
VerifyMCP ran 15 checks on Athenode, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Athenode: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.