Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Connect goals, reconcile commitments, and keep work moving with Veloci.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://veloci.arcticrex.com/mcp/veloci터미널에서 이 명령어를 실행하세요
claude mcp add --transport http veloci https://veloci.arcticrex.com/mcp/veloci프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"veloci": {
"url": "https://veloci.arcticrex.com/mcp/veloci"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"veloci": {
"type": "http",
"url": "https://veloci.arcticrex.com/mcp/veloci"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://veloci.arcticrex.com/mcp/veloci메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 도메인 arcticrex.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.3.2)은 28일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Tools MCP
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ 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.
Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Connect your agent to your Veloci workspace: set and review goals, reconcile commitments from your notes, and keep progress tied to the work that matters. The plugin also loads the shared work-tracking instructions when a supported agentic session starts.
Try “Show my goals and open commitments so we can decide what matters next,” or “Reconcile these notes with my existing commitments.” Tools depend on your workspace's available capabilities. Plan your week, connect goals to commitments, and review progress with Veloci.
Beta for existing Veloci accounts on veloci.arcticrex.com. This source is maintained by ArcticRex. It is not an official vendor directory listing or a verified badge. Installation does not grant workspace access. The Claude Code and Cowork listing is submitted and pending review. ChatGPT Work verification is pending.
Public beta marketplace. Install from the ArcticRex repository using the steps below. If Veloci is already installed, check its endpoint, enabled components, authentication, trust, and fresh-session behavior before reinstalling.
If your existing Veloci connection uses a different gateway, do not install this test beta or switch your account. Use a package explicitly configured for your gateway.
If a fresh task ignores Veloci, open Settings → Cowork → Global instructions and add the following once, preserving your existing instructions. Save, then start a fresh task. This setting supplies the reminder when the plugin alone does not load it.
Use Veloci for substantive work; status questions need no task.
Reuse the bound task for related follow-ups, clarification, testing, evaluation, and repairs. If completed work resumes, call reopen_task then start_task on that same ID. Create a new task under the relevant goal only for a distinct objective with no matching task. At the start, call start_task and announce the title and ID once, then keep that ID bound.
Update the task only at the start and when the tracked work is actually complete, unless the user asks for an update.
When the tracked work is actually complete — ships, merges, or lands — call complete_task and report the result.
Run these commands inside Claude Code:
/plugin marketplace add ArcticRexOrg/veloci-plugins
/plugin install veloci@arcticrex
Choose user scope. Sign in to Veloci when prompted. Reload plugins if the installation summary requests it, start a new session, and invoke the plugin’s init skill once using the host’s supported presentation. A literal /init command is not guaranteed and does not replace the host’s built-in initialization.
Register the marketplace in a local terminal:
codex plugin marketplace add ArcticRexOrg/veloci-plugins
Restart the desktop app. In Plugins Directory, select ArcticRex, install Veloci by ArcticRex, and connect your account. Review and trust its current hook definition where prompted (/hooks in Codex CLI). Start a new local task and ask “Run Veloci init to check automatic task tracking.” A web installation does not deploy scripts to a separate hosted environment.
Init is a one-time check, not a command to repeat before every session. After setup, start ordinary work in a fresh session without mentioning tracking. Your agent should start the matching task, announce its title and ID once, keep that ID on continuation, and complete it when the tracked work actually finishes. Unfinished work stays in progress. Progress updates are available when requested; automatic tracking does not require repeated updates or readbacks.
The check reports connection, installation, trust, and observed instruction delivery separately. If it cannot prove instructions loaded, it reports that. Installation alone is not verification. Remote control of the same computer uses that computer's setup; a separate agent or execution environment needs its own setup.
The plugin connects to https://veloci.arcticrex.com/mcp/veloci using your own account. Its startup script only prints the Veloci task instructions; it performs no network request and changes no files. The agent uses Veloci tools under the permissions you grant. No arcrex binary or edits to AGENTS.md/CLAUDE.md are required.
The removal-only scripts/remove-legacy-hooks.py helper requires explicit --remove; the scripts/check.py --migrate flow calls it. No standalone installer is bundled. The optional migration removes only recognized old standalone task hooks when you explicitly request migration after the plugin is enabled and trusted. It preserves unrelated hooks. Do not enable duplicate standalone and plugin task hooks. Use the host connection UI to remove an obsolete duplicate MCP connection after verifying the replacement.
Use your host's plugin manager to update or uninstall Veloci. Updated hook definitions may require renewed trust. After installing or updating in Codex desktop, quit and reopen the app, then start a fresh task. In Codex CLI, start a new session to verify the update. Uninstalling does not restore a standalone hook removed during migration or delete your Veloci tasks. If you added the Cowork global instruction above, remove that paragraph to disable its reminder.
ArcticRex · Contact
Report installation issues through this repository's issues. Include host/version and which setup step failed; do not post tokens, private tasks, or account data.
GitHub Actions validates and builds a ZIP on every push and pull request. Download veloci-release from the workflow run to test an unpublished build. ZIPs are not committed to this repository.
To publish, update both plugin manifest versions in a reviewed commit, merge it, then push the matching tag (for example, v0.2.2). The same workflow validates the tag against both manifests, packages only the committed plugins/veloci/ files, and attaches veloci-0.2.2.zip and veloci-0.2.2.zip.sha256 to a GitHub Release. Hidden manifests sit at the ZIP root and executable permissions are preserved. A failed validation or version mismatch prevents publication. Existing releases are not overwritten; use a new version for changes.
Marketplace installation continues to use this repository directly. The ZIP is for manual plugin uploads and downloads. No separate publishing secret is needed; the release job uses the repository's GitHub Actions token.