Listspace MCP server
2026년 11월 12일 커밋AI agent이 Listspace 보드를 프로젝트 메모리로 사용하여 작업 보드를 읽고 최신 상태로 유지할 수 있습니다.
다른 이름 listspace/agent, agent
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 2.0.0
- 마지막 커밋
- 2026년 11월 12일
- 라이선스
- MIT
Listspace MCP란?
Listspace은(는) MCP server입니다. AI agent이 Listspace 보드를 프로젝트 메모리로 사용하여 작업 보드를 읽고 최신 상태로 유지할 수 있습니다.
프로젝트 README에서 생성된 요약
Listspace MCP server 정보
Listspace는 AI 코딩 agent가 Listspace 보드를 지속 가능한 프로젝트 메모리로 사용할 수 있는 방법을 제공합니다. 이를 통해 agent는 작업 보드를 읽고 코드베이스를 작업하는 동안 보드를 최신 상태로 유지할 수 있습니다. 이 시스템은 Claude Code 또는 Agent Skills 형식을 지원하는 모든 agent를 사용하는 개발자를 위해 설계되었습니다. mcp.listspace.app의 원격 MCP server 또는 로컬 Node CLI를 통해 통합할 수 있습니다.
server를 설정하려면 Listspace 설정에서 발급받은 개인 API token을 사용하여 로그인해야 합니다. 구현체에는 보드 컨텍스트 관리를 자동화하는 Claude Code 플러그인이 포함되어 있으며, agent가 중요한 의사 결정을 기록하고 작업 진행 상황을 업데이트하도록 보장하는 전용 hook 기능이 있습니다. 이러한 hook은 파일 수정, git commit 또는 pull request merge와 같은 활동을 모니터링하여 agent가 보드의 항목을 이동하도록 유도합니다. CLI와 플러그인은 Node.js 환경을 위해 구축되었으며 세션 및 보드 상호 작용을 관리하는 다양한 방법을 제공합니다.
활용 사례
- 1중요한 프로젝트 의사 결정 기록시스템이 agent에게 향후 개발 작업에 영향을 미치는 선택 사항을 문서화하도록 요청할 수 있습니다.
- 2agent skill 설치 자동화개발자는 단일 명령어를 사용하여 agent에 Listspace 기능을 빠르게 추가할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Listspace MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Listspace MCP 설치
$ claude mcp add --transport http agent https://mcp.listspace.app/Cursor에 Listspace MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"agent": {
"url": "https://mcp.listspace.app/"
}
}
}VS Code에 Listspace MCP 설치
.vscode/mcp.json
{
"servers": {
"agent": {
"type": "http",
"url": "https://mcp.listspace.app/"
}
}
}VS Code CLI에 Listspace MCP 설치
$ code --add-mcp '{"name":"agent","type":"http","url":"https://mcp.listspace.app/"}'Codex에 Listspace MCP 설치
$ codex mcp add agent --url https://mcp.listspace.app/Codex config.toml에 Listspace MCP 설치
~/.codex/config.toml
[mcp_servers.agent] url = "https://mcp.listspace.app/"
Gemini CLI에 Listspace MCP 설치
$ gemini mcp add -s user --transport http agent https://mcp.listspace.app/Gemini settings.json에 Listspace MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"agent": {
"url": "https://mcp.listspace.app/",
"type": "http"
}
}
}자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능listspace/agent is public and reachablegithub.com/listspace/agent ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-12github.com/listspace/agent ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답HTTPS endpoint answered 401 (sign-in required)통과
README
GitHub에서 보기Listspace for coding agents
The pieces that let an agent use a Listspace board as its project memory. This folder is public as github.com/listspace/agent, and the CLI is on npm as listspace. Install and sign in with:
npx listspace login # paste a personal token from Listspace: Settings > Your AI > API tokens
npx listspace boards
| Path | What it is |
|---|---|
skills/listspace/ |
The skill: SKILL.md (the work loop) plus reference/ (tools, agent access, CLI), loaded only when needed. Follows the Agent Skills format, so npx skills add can install it. This is the source copy. |
cli/ |
listspace, a small Node CLI for agents without the MCP server: short commands over the REST API (https://api.listspace.app/v1), and call for every MCP tool through the MCP server (https://mcp.listspace.app). TypeScript bundled into one ESM file, no runtime dependencies, Node 20 or later. |
claude-code-plugin/ |
A Claude Code plugin: the skill (a copied file set) and .mcp.json, which registers the remote MCP server https://mcp.listspace.app. |
.claude-plugin/marketplace.json |
A marketplace file listing the plugin, so this folder can be added as a local marketplace now and as a GitHub one later. |
AGENTS.md.snippet |
Lines a user pastes into a repo's AGENTS.md or CLAUDE.md to point agents at the right board. |
scripts/ |
sync-skill.mjs copies the skill into the plugin; check-agent.mjs (in CI) checks the copy, the frontmatter, the versions and the MCP entry. |
The MCP server is also listed in the MCP Registry as app.listspace/listspace and on Smithery.
Editing the skill
Edit skills/listspace/ only, then run:
node agent/scripts/sync-skill.mjs
node agent/scripts/check-agent.mjs
The plugin gets a real copy, not a symlink, so the plugin folder still works when it is copied or downloaded on its own. CI fails when the two differ. Keep SKILL.md short: steps and rules there, detail in reference/.
One version runs through cli/package.json, cli/src/version.ts, plugin.json and the skill's metadata.version; the check fails when they differ.
Try it locally
The CLI
cd agent/cli
npm ci
npm run build
node dist/listspace.mjs login # paste a token from Listspace: Settings > Your AI > API tokens
node dist/listspace.mjs whoami
node dist/listspace.mjs session "<board title or id>"
node dist/listspace.mjs add "<board>" ideas "Try dark mode" --description "Seen in **settings**"
npm link in agent/cli puts listspace on the PATH. LISTSPACE_TOKEN overrides the saved token for one run, and LISTSPACE_API_URL and LISTSPACE_MCP_URL point the CLI at another server. Every command takes --json. The token is saved in the OS config directory (%APPDATA%\listspace on Windows, ~/Library/Application Support/listspace on macOS, ~/.config/listspace elsewhere) as credentials.json, mode 600.
Tests: npm test (node:test with a fake fetch, no network). npm run typecheck runs the strict type check.
The skill on its own
Any agent that reads Agent Skills:
npx skills add ./agent -s listspace # the skills CLI reads skills/ in a local folder
or copy agent/skills/listspace to ~/.claude/skills/listspace for Claude Code. Connect the MCP server separately (claude mcp add --transport http listspace https://mcp.listspace.app), or use the CLI above.
The Claude Code plugin
For one session:
claude --plugin-dir ./agent/claude-code-plugin
Or as a local marketplace, which keeps it installed:
claude plugin marketplace add ./agent
claude plugin install listspace@listspace
Then run /mcp, pick the listspace server and sign in (OAuth through Listspace). The skill shows up as /listspace:listspace and Claude loads it on its own when the project has a board. claude plugin validate ./agent/claude-code-plugin checks the manifest.
If you already added the Listspace MCP server yourself, Claude Code may show both; remove one.
The decision check
The plugin also has a small check that runs at the end of each of Claude's turns (hooks/hooks.json, hooks/decision-check.mjs). When the user picks an option, says yes to a proposal or corrects a fact, and Claude records no decision in that turn, Claude is sent back once with one line: if it was a decision that affects future work, record it with record_decision as Proposed; otherwise end the turn without comment.
The rules lean to silence. A yes to an offer to act ("Want me to commit?" "yes"), a maybe, and a bug report or a place in the code ("no, it's still failing", "the bug is in the parser") are not decisions. A yes counts only when Claude's last message offered a choice or made a proposal (recommend, suggest, propose, options, which one, a lettered list).
- It does nothing in a session that has not used a Listspace tool, and never blocks twice in a turn (
stop_hook_active), so it cannot loop. - It is plain rules on the user's words, with no model call and no network, so it costs nothing and answers in milliseconds (timeout 5 seconds).
- It needs Node.js 18 or later on the computer (Windows, macOS or Linux). Each command ends in
; exit 0, so without Node.js the check does nothing and Claude Code shows no hook error (sh, Git Bash and PowerShell). - It keeps a few small files per session in the plugin's data folder (
CLAUDE_PLUGIN_DATA, readable only by the user) and removes them after a week. An ordinary prompt writes nothing. A prompt that reads like a decision leaves its first line, cut at 80 characters, for that turn only. Of Claude's last message it keeps only whether it offered a choice. Without the data folder the check does nothing. - Tests:
node --test agent/scripts/decision-check.test.mjs.check-agent.mjscheckshooks.json.
The progress check
A second check at the end of each turn (hooks/progress-check.mjs) keeps the board in step with the work. When a turn changed files (Edit, Write, MultiEdit, NotebookEdit), committed, pushed or merged with git, opened or merged a pull request with gh, or deployed, and Claude made no Listspace write after that work, Claude is sent back once with one line: "Update the Listspace board: what did you start or finish this turn? Move the item, add a short comment."
- It does nothing in a session that has not used a Listspace tool, and never blocks twice in a row (
stop_hook_active), so it cannot loop. - After a nudge it waits at least 3 turns before the next one, and only nudges again for new work, so it does not nag.
- Any Listspace write counts as the update (
move_item,add_comment,complete_item,record_decision,captureand the rest); reads do not. - It keeps only the facts (work done, board updated, the turn of the last nudge) in the plugin's data folder, never a command or a file name, and removes them after a week. Same Node.js and
; exit 0rules as the decision check. - Tests:
node --test agent/scripts/progress-check.test.mjs.
Board context
The board rules arrive with the Listspace server's instructions at the start of a session, and a long session, most of all one whose conversation was compacted, can lose them. hooks/board-hooks.mjs adds them back to Claude's context at the moments that matter. It only adds context: it never blocks anything and never changes a command or its output.
- Session start (SessionStart: startup, resume, clear): one line that names the project's board and says to start with
get_accountandstart_session, update the items inunfinished_from_last_sessionsfirst, and keep the board current. - After a compaction (SessionStart with source
compact): the board rule, and to callget_account(orstart_session) before going on, sinceclaimed_by_youandstarted_by_youlist the items Claude was working on. - After a pull request or a deploy (PostToolUse on Bash and PowerShell): after
gh pr create,gh pr mergeor a deploy command that worked, one line says to move the matching item (to Doing for a new pull request, to Done after a merge or a deploy) and add a short comment. - It does this only in a project whose CLAUDE.md or AGENTS.md has a
Listspace board:line (in the folder or one above it, up to the repository root), or in a session that used a Listspace tool (the progress check's note). From the file it takes only a link to a Listspace board, never other text. - It writes nothing and makes no network call. Same Node.js and
; exit 0rules as the decision check. - Tests:
node --test agent/scripts/board-hooks.test.mjs.
What is left out, and why
- Device pairing for
login: the API has it (POST /auth/device), but the CLI does not use it yet.loginalready separates "how the token is obtained" from saving it; a TODO incli/src/cli.tsmarks where pairing goes.--tokenand a piped token stay for scripts. - A token in the plugin:
.mcp.jsonhas no headers on purpose. A token would ship to every user; sign-in through/mcpis per user. The check script refuses headers there. - The CLI inside the plugin (
bin/): left out, because claude.ai and Cowork do not install plugins with a top-levelbin/and the MCP server covers Claude Code.
Publishing
- Skill via
npx skills add: published. The public repositorylistspace/agentholds this folder at its root, sonpx skills add listspace/agentworks. - CLI on npm: published as the unscoped
listspace(0.6.0). To release a new version: bump the one version (see "Editing the skill"), check the package contents withnpm pack --dry-run, thennpm publishfromagent/cliwith an npm account with 2FA.prepublishOnlyruns the type check, tests and build. - Claude Code plugin: the public repo doubles as a marketplace (
.claude-plugin/marketplace.json), so users run/plugin marketplace add listspace/agentand/plugin install listspace@listspace. Listing in Anthropic's plugin directory is a separate submission; the owner decides on it, with privacy policy and terms URLs for that listing.
Sources: Claude Code plugin manifest reference (https://code.claude.com/docs/en/plugins-reference), plugin loading and --plugin-dir (https://code.claude.com/docs/en/plugins/loading), marketplace reference (https://code.claude.com/docs/en/plugins/marketplace-reference), skills (https://code.claude.com/docs/en/skills), Agent Skills specification (https://agentskills.io/specification), the skills CLI (https://github.com/vercel-labs/skills), and Postiz's agent repo as the model (https://github.com/gitroomhq/postiz-agent).
Listspace MCP 질문
Listspace MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http agent https://mcp.listspace.app/를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Listspace MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Claude Code에서 Listspace를 사용할 수 있나요?
네, 원격 MCP server를 등록하고 의사 결정 및 진행 상황 추적을 위한 전용 hook을 포함하는 Claude Code 플러그인이 제공됩니다.
진행 상황 확인은 어떻게 작동하나요?
진행 상황 확인 기능은 agent가 Listspace 보드를 업데이트하지 않고 파일 수정이나 git commit 등의 작업을 수행하는지 모니터링하며, 업데이트를 기록하도록 agent에게 알림을 보냅니다.