Seamless

MCP文档知识

提供方 未标注

文档知识 未标注 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code

本地优先的共享内存与任务协调,专为AI编码代理设计。一个Go二进制文件、MCP服务器、以及您拥有的Markdown文件。支持Claude Code和Codex CLI(及其桌面应用)的钩子。

一句话选型结论

按资料字段整理

Seamless 属于文档知识类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Seamless当前 未标注 未标注 未标注 无 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.5 KB
来自项目仓库与上游目录的原文,未做删改

Seamless

An AI coding agent rediscovers the same constraint every session, because
nothing it learns survives the context window. Run two agents against the same
backlog and they pick the same step and build it twice. And the products that
promise to fix this keep your project's memory in someone else's database.

Seamless is a local-first memory and coordination substrate for AI coding
agents. Works with Claude Code, Codex CLI, and any MCP client. It also works
from chats in the Claude desktop app, for long-running work that isn't code:
see Seamless in the Claude app.

It gives a fleet of agents a shared, durable memory and a way to divide work
without colliding: memories with a supersession lifecycle, hybrid recall, a
dependency-aware task queue with lease-based claiming, captured plans, and
research trials. Durable knowledge is stored as markdown files on disk; the
seamlessd daemon indexes it, serves it over MCP, and renders a web console,
while the companion seam CLI gives headless agents a direct interface.

Full documentation: thereisnospoon.org/docs/
· Website: thereisnospoon.org (source in
docs/)

Developed and published by Arctop. MIT licensed.

Design principles

  • Built for a fleet, not a lone agent. Real coordination primitives: a
    dependency-aware ready-queue, atomic lease-based task claiming, and plans
    composed of notes and steps, so agents divide labor instead of colliding.
  • Files are the source of truth. Every memory and note is a markdown file
    with YAML frontmatter under ~/.seamless -- git-diffable, greppable,
    hand-editable. SQLite indexes those files and also stores operational state
    such as sessions, tasks, trials, and events, so back up the whole data
    directory.
  • Curation proposes, humans dispose. Every gardener pass -- from
    deduplicating and archiving to flagging dead weight and knowledge gaps --
    only proposes; applying is an explicit action. Supersession preserves
    provenance, so nothing is silently rewritten.
  • Small, self-contained runtime. A static Go daemon and CLI, no CGO,
    pure-Go SQLite, no Node, no separate vector engine, no cloud account.

How it compares

The agent-memory space splits into a few recognizable categories. By category,
because categories do not go stale:

Seamless Cloud memory APIs Built-in agent memory Knowledge-graph servers
Storage format Markdown files on your disk; SQLite indexes them and stores operational state Their database, reached by API key Vendor-managed store inside one product A graph database, often a separate server
Runs where Your machine, localhost only Their cloud The vendor's product Your machine or theirs
Account required No Yes The vendor's Usually no
Multi-agent coordination Task queue, lease-based claiming, shared plans None None -- one agent, one store Shared reads at best
Forgetting policy Supersession with provenance; a gardener proposes, a human disposes Automatic summarization you do not control Vendor-defined Manual
Runtime Static Go daemon and CLI HTTP SDK against their service None (built in) Node or Python, plus the database

For the version with product names and receipts, see
the full comparison.

Real transcripts

Four pairs of real, unedited Claude Code sessions -- identical prompt,
identical repo, with and without Seamless:

  • Cold start -- one
    session continues yesterday's plan from an injected briefing; the other
    re-derives the work from a TODO and re-ships a bug the project had already
    fixed once.
  • Constraint violation --
    a security scanner demands SameSite=Strict, which the team already learned
    breaks external-link logins. One session ships the regression anyway; one
    refuses and cites the recorded constraint.
  • Token safety --
    told to persist refresh tokens, one agent mirrors the in-memory map into a
    raw-token SQL column; the other reads a recorded rule first and stores only
    SHA-256 hashes.
  • Task collision --
    two live agents race for the same plan step. One claim wins, the other
    bounces with the holder's name and pivots to the next ready step.

What Seamless is not

Not a hosted team knowledge base, not a RAG framework, not a benchmark winner:
it is memory and coordination for one owner's fleet of agents, on that owner's
machine.

Quick start```bash

curl -fsSL https://thereisnospoon.org/install | sh


On Windows, the same install in PowerShell:```powershell
irm https://thereisnospoon.org/install.ps1 | iex

That is the whole install. It needs curl and tar and nothing else -- no Go,
no CGO toolchain, no database, no Node. It fetches the checksum-verified release
archive for your platform (macOS, Linux, and Windows; amd64 and arm64), installs
seamlessd and seam into ~/.local/bin, generates the bearer key, installs
hooks, MCP, and skills for the detected Claude Code/Codex local hosts, and runs
the daemon as a per-user service -- launchd on macOS, systemd --user on Linux, an
at-logon Scheduled Task on Windows. It keeps itself up to date: from v0.7.0 it
installs each new release by itself, a day after it is published and at a moment
no agent is using it -- backed up, and rolled back if the new release does not
come up. To update right now, run seamlessd update (--check reports
installed vs latest): your config and ~/.seamless are preserved.

> Early days, frequent releases. Seamless is early in its development
> cycle, and releases with improvements and bug fixes land often. An installer
> install updates itself from v0.7.0 on; on v0.6.0 or older, run
> seamlessd update once. See
> Update & uninstall.

(Why seam? The CLI keeps the short name of Seam v1, the decommissioned
private predecessor Seamless was rebuilt from the ground up to replace.)

Then just start the selected client in a git repo. There is no project to create
and no repo to register: the session-start hook resolves your cwd to its git
root, derives a project from the repo's directory name, and records the mapping
on the spot, so agents inherit project scope without passing it on every call.
Reach for seamlessd map-repo --path ~/code/myrepo --project myrepo only to
override the derived slug.

It is one shell script and piping a stranger's script into a
shell deserves a read first. Prefer the pieces one at a time - Homebrew,
go install, prebuilt archives - or want the override knobs? Every route is
on Install & deploy, and the
Quickstart tailors each step to
your OS and client.

Then: Quickstart ·
Claude Code setup ·
Claude app chat setup ·
Codex local setup ·
Install & deploy

Documentation

The full docs are at
thereisnospoon.org/docs/ (sources in
docs-src/, generated by cmd/docsgen).

Concepts · Memory & notes, sessions & briefings, recall, tasks & plans, projects & scope, the gardener
Guides · Integrating an agent, writing memories that get recalled, coordinating a fleet, troubleshooting
Reference · Every MCP tool, both CLIs, every config key, the hooks, and the file formats
Internals · Architecture, contributing, domain invariants

This README is deliberately short. Anything that can drift from the code -- tool
counts, config keys, CLI flags -- lives in the docs site, where the reference
pages are generated from the code itself and make check fails if they go stale.

Development```

make build # ./bin/seamlessd + ./bin/seam
make test # unit tests
make test-race # unit tests under the race detector
make bench # hot-path benchmarks (recall, briefing, matcher, event fan-out)
make lint # golangci-lint
make check # the full gate: build + vet + cross-check + fmt-check +
# docs-check + installer-check + site-check + lint +
# vulncheck + test-race
make doctor # config + database self-checks
make run # serve on 127.0.0.1:8081

make docs # regenerate the docs site (docs-src/ -> docs/docs/, committed)
make docs-serve # regenerate + serve the site at 127.0.0.1:8899/docs/
```

Tests are table-driven with testify/require against fresh or in-memory SQLite.
Use make fmt rather than gofmt -w .: the Make target scopes formatting to
git-tracked files, while a bare gofmt walk also rewrites dot-directories that
Go's ./... pattern excludes.

The docs site's output under docs/docs/ is committed, and make check runs
docs-check, so a change to docs-src/ -- or to the tool surface or config keys
the reference generates from -- must be followed by make docs in the same
change. See SITE.md.

Conventions live in AGENTS.md; read it before writing code.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Seamless 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Seamless 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Seamless 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Seamless 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Seamless 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Seamless 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。