# Listspace [Health: Active]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://github.com/listspace/agent  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/listspace

## Description
Project memory for AI agents: read and keep the user's Listspace boards up to date.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "listspace": {
    "command": "npx",
    "args": ["-y","listspace"]
  }
}
```

## Documentation

## What Listspace MCP server does

Listspace MCP server connects an AI coding agent to a user's Listspace boards. The board can hold project context that an agent reads during work and updates as tasks progress. This makes Listspace suitable for teams or individuals who want decisions, plans, and current work status to remain available across sessions.

The repository includes the MCP registration used by the Claude Code plugin, along with an Agent Skills package that describes the intended work loop. The skill is loaded when needed and points the agent toward the relevant board and operations.

## How it works

The hosted MCP endpoint is `https://mcp.listspace.app`. In Claude Code, the plugin registers that endpoint and the user signs in through the `/mcp` interface using Listspace OAuth. The plugin does not include a shared token or hard-coded authorization header; authentication is performed per user.

The MCP connection provides board access for both reading and writing. Known write operations include `move_item`, `add_comment`, `complete_item`, `record_decision`, and `capture`. A decision check can remind Claude Code to record a future-relevant decision after the user chooses an option or accepts a proposal. A separate progress check can prompt an update after file changes, Git activity, pull requests, or deployment work when no Listspace write occurred.

These checks run locally in Claude Code. They use plain rules rather than model calls, store limited session facts in the plugin data directory, and remove those files after a week. They do not act in sessions that have not used a Listspace tool.

## Setup and configuration

For Claude Code, use the repository as a plugin for a single session:

```bash
claude --plugin-dir ./agent/claude-code-plugin
```

Alternatively, add the repository as a local marketplace and install `listspace@listspace`. After installation, open `/mcp`, select `listspace`, and complete the Listspace sign-in flow. The associated skill appears as `/listspace:listspace` and is loaded when the project has a board.

The MCP server can also be registered directly with Claude Code:

```bash
claude mcp add --transport http listspace https://mcp.listspace.app
```

If the plugin and a manually configured server are both present, Claude Code may show duplicate Listspace entries. Remove one registration. The repository also provides a separate `listspace` Node.js CLI for agents that do not use MCP, but that CLI is an alternative access path rather than a configuration requirement for the hosted server.

## Tools and capabilities

Listspace MCP server supports the board-centered work loop documented in the repository. Supported capabilities include:

- Reading project information from Listspace boards.
- Moving items as work changes state.
- Adding comments about progress.
- Marking items complete.
- Recording decisions, including proposed decisions.
- Capturing information for later use.
- Nudging an agent to keep the board synchronized with coding work.

The repository identifies additional Listspace writes as available to the progress check, but does not provide a complete MCP tool catalog in the supplied material.

## Limitations and notes

The MCP endpoint is hosted remotely and requires Listspace authentication. The plugin intentionally does not ship a token. The decision and progress hooks are Claude Code-specific and require Node.js 18 or newer; they do nothing when their data directory is unavailable. The repository's standalone CLI requires Node.js 20 or newer and has a different feature boundary: for example, its documentation notes that comments are available through the API and MCP but not yet through the CLI.

The board synchronization prompts are limited safeguards rather than a guarantee that every coding action is recorded. The progress check waits at least three turns after a nudge and only reacts to specified work events. Listspace MCP server is therefore most appropriate when the agent can use the hosted MCP connection and the project team is willing to treat the board as maintained project context.

_Full upstream README: https://allmcps.com/mcp/listspace/readme_