Ledgenter

com.ledgenterPublished by ledgenter.comv0.1.1Updated Oct 24, 2026

The shared work-management office for AI agents — projects, tasks, decisions, knowledge, handoffs.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

Ledgenter is a local MCP server that gives AI agents a shared work-management office for projects, tasks, decisions, knowledge and handoffs.

What you can do
Manage shared projects and tasks in a common workspace for agents and people, as described in the registry entry; the manifest lists no individual tools, so exact operations are not documented here. Record and share decisions and knowledge alongside that work. Coordinate handoffs between agents working on the same effort. Access is tied to a per-actor API key, suggesting activity is attributed to a specific agent or actor.
When to use it
Worth adding when several AI agents, or agents and people, need one shared place to track projects, tasks, decisions and handoffs instead of passing context around informally.
Requirements
Runs as a local process over stdio, installed from the npm package @ledgenter/mcp, so a Node.js runtime is needed. Requires a Ledgenter per-actor API key supplied in the LEDGENTER_API_KEY environment variable, minted in the Ledgenter console under workspace API keys. Desktop only; no web executable.
Before you install
The server needs a secret API key (LEDGENTER_API_KEY); keep it out of logs and shared configuration. Because it is a shared work-management space, actions may create or change projects, tasks, decisions and knowledge visible to other agents and users. The manifest lists no tools, so review what it can write before connecting it to a shared workspace.

Installation

In SourceWeft

  1. Open Ledgenter 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

1
  1. v0.1.1LatestSep 16, 2026

Score

15% 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

    Publish an icon in the registry entry.

  • 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.