Athenode

com.athenodePublished by athenode.comv0.10.7Updated Oct 24, 2026

Spec-driven development for AI coding agents: specs, skills, agents, rules and MCP servers.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Athenode is a local stdio MCP server for spec-driven development, giving AI coding agents access to a project's specs, skills, agents, rules and MCP servers.

What you can do
  • Connect an AI coding agent to an Athenode project's spec-driven development setup.
  • Work with the project's specs, skills, agents, rules and MCP server definitions.
  • Run locally over stdio from the project root, using the configuration created by the Athenode init command.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth adding when you use Athenode to organize specs, skills, agents and rules for AI coding agents and want the assistant to work with that project context directly. It is a desktop-only local server, so it suits local development rather than hosted or browser use.
Requirements
Runs as a local process via npx from the npm package @athenode/cli (Node.js required). The project root must contain .athenode/config.json, created by running the Athenode init command there. ATHENODE_PROJECT_DIR sets the project root and defaults to the working directory or the client's first root. A project token is stored by init or supplied through the ATHENODE_TOKEN environment variable.
Before you install
The server uses a project token, which can be passed in the ATHENODE_TOKEN environment variable; treat it as a secret and avoid exposing it in shared configuration. It reads and may act on project files under the configured project root, so point ATHENODE_PROJECT_DIR only at the intended project. No tool list is published, so review what it can change before enabling it in a working repository.

Installation

In SourceWeft

  1. Open Athenode in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v0.10.7LatestOct 17, 2026
  2. v0.10.1Oct 16, 2026
  3. v0.9.2Oct 12, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.