Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Your why agent, the infra agent for your fleet. Your agents work from what you decided, and why.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.unlimitless.ai/mcp在终端中运行这条命令
claude mcp add --transport http unl https://api.unlimitless.ai/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"unl": {
"url": "https://api.unlimitless.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"unl": {
"type": "http",
"url": "https://api.unlimitless.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.unlimitless.ai/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 unlimitless.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.2.3)于25天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, ProAgentStore
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP-first control plane for ProAgentStore agents and private instances.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Unl, your why agent. Your AI already knows how to reason. Unl gives it your reason.
See it work in two minutes, no account: node demo/changed-decision.mjs
You decide things while you work with AI: what to build, what to leave out, and why. Unl keeps those decisions with their reasons. When you or one of your agents is about to act, Unl hands over the ones that bear on the task, so Claude Code, Cursor, ChatGPT, Codex and the agents you build all start from the same why. You never re-brief them.
Open, in this repository, under MIT: everything that runs on your side. The unl command, the AI SDK package, the Cursor plugin, a working example for each agent framework, and the decision format with a conformance check you can run on your own code. Read them to see exactly what leaves your machine.
Also open: the status checks, which test Unl from outside its own infrastructure.
Hosted: Unl itself, the service that keeps your decisions with their reasons and chooses which ones bear on a task, runs at api.unlimitless.ai. Its code is not in this repository.
With the agent you already use, tell it:
Read unlimitless.ai/start.md, set up Unl, and show me the decisions you find.
In Claude Code or Cursor:
npm install -g unlimitless
unl # sign in once, then the Unl terminal opens unl init # in your project, for Claude Code (add --cursor for Cursor)
Then ask your agent what you are working on.
In any MCP client (ChatGPT, Claude, Codex, VS Code, Grok Bot, Lovable): add the server https://api.unlimitless.ai/mcp and sign in when it asks.
In an agent you build: make a key at unlimitless.ai/portal/keys, set it as UNL_KEY, and pick your framework below.
Every tool uses the same address, https://api.unlimitless.ai/mcp, and signs in with OAuth once. There is no key to paste: a personal key is only for the API, never for connecting a tool.
Claude and Claude Desktop. Open Settings, then Connectors, and choose Add custom connector. Name it Unl, paste https://api.unlimitless.ai/mcp, and add it.
Claude Code. In your project, unl init signs you in and wires the hook that brings Unl into every turn. To add only the server:
claude mcp add --transport http unl https://api.unlimitless.ai/mcp
then run /mcp, choose unl and pick Authenticate.
ChatGPT. In Settings, open Plugins and switch on Developer mode. Choose New Plugin, name it Unl, paste https://api.unlimitless.ai/mcp as the server URL, set authentication to OAuth and keep Dynamic Client Registration. Then open Advanced OAuth settings and untick OIDC enabled: left on, ChatGPT asks for a scope Unl does not register and the connection is refused.
Cursor. Add the URL to .cursor/mcp.json, no key and no header, or install the Cursor plugin in this repository:
{ "mcpServers": { "unl": { "url": "https://api.unlimitless.ai/mcp" } } }
Everything else (Codex, VS Code, Antigravity, Grok Bot, Lovable, Viktor and more): step-by-step for each, kept current, at unlimitless.ai/connect.
| Folder | What it is |
|---|---|
cli/ | The unl command. unl init adds Unl to a Claude Code or Cursor project, and unl on its own opens the Unl terminal: each turn, the decisions Unl handed your agent with their reasons, and the ones it held back. |
packages/ai-sdk/ | @unlimitless/ai-sdk. Wrap any Vercel AI SDK model with withUnl and every call carries the part of your decisions that bears on it. |
examples/ | One small working example per framework: Mastra, OpenAI Agents SDK, Google ADK, LangChain, Pydantic AI, LiteLLM, Cloudflare Agents, Netlify, TanStack AI, Composio, E2B, Browser Use and a GitHub Copilot custom agent. |
examples/vercel-ai-sdk-chat/ | A chat app on the AI SDK you can deploy to Vercel with Unl already added. |
.cursor-plugin/ and mcp.json | The Cursor plugin: Unl's MCP server, with sign-in discovered from the server. No key in the repository. |
decision-format/ | The open format for a kept decision: what it holds, how its address is computed and checked, a conformance check you can run on your own implementation, and reference code in Node and Python. MIT, and it runs without Unl. |
git clone https://github.com/Unlimitless-Inc/unl.git
cd unl/packages/ai-sdk npm install npm test
These tests use synthetic responses. They test the client contract without an account or a model call, and do not prove hosted retrieval or model performance. The planner and writer example is the next step for trying a real changed decision in your own test project.
For example, you first choose synchronous exports because the files are small. Later you choose a queue because larger files exceed the request timeout. The job is for a fresh writer to receive the new choice and its reason, then produce a change that follows it. Compare with an equally updated file as well as stale or absent context. A maintained file may work just as well.
Two ways in, and most examples show both:
Unl ships changes every day, and the changelog says in plain words what each one did. To follow along, star this repository.
Bug reports and small fixes are welcome: see CONTRIBUTING.md. To report a security problem, follow SECURITY.md and do not open a public issue.
MIT. See LICENSE.