Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
AI testing harness with Jay: risk-based checks, bug investigation, and local evidence reports.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
CARBON_ANALYTICS, DO_NOT_TRACK필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"carbon": {
"command": "npx",
"args": [
"-y",
"@testers-ai/carbon-mcp"
],
"env": {
"CARBON_ANALYTICS": "your-value",
"DO_NOT_TRACK": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add carbon --env CARBON_ANALYTICS=your-value --env DO_NOT_TRACK=your-value -- npx -y @testers-ai/carbon-mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"carbon": {
"command": "npx",
"args": [
"-y",
"@testers-ai/carbon-mcp"
],
"env": {
"CARBON_ANALYTICS": "your-value",
"DO_NOT_TRACK": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"carbon": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@testers-ai/carbon-mcp"
],
"env": {
"CARBON_ANALYTICS": "your-value",
"DO_NOT_TRACK": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
CARBON_ANALYTICS envDO_NOT_TRACK env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 jarbon 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.32.22-free.17)은 16일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Georgia 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.
An MCP server for Georgian public data, read from the organizations that publish it.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Your AI test manager agent. Jay examines your project and changes, prioritizes risk, coordinates software testing and turns findings into visual evidence. Use CARBON Core for QA, bug finding, accessibility testing, regression-test planning and evidence-backed quality reports. Free under the MIT license.
Start with `/carbon:carbon` in Claude or `/carbon` in Codex. Watch a compact execution plan, the current check and recorded screenshots as the investigation progresses. Reports distinguish executed tests, proposed work and untested gaps.
Website and guide · Command reference · Download releases · Codex edition · Report an issue
The product name is CARBON Core. The repository and technical plugin name remain carbon-free and carbon so existing installations keep receiving updates.
The free, MIT-licensed runtime with Jay is also packaged as @testers-ai/carbon-mcp. Requires Node.js 22+; demo and full-workflow helpers also require Python 3.10+.
Use the npm setup guide and verified release artifacts for MCP installation. The source distribution version is not a claim of npm publication.
See the npm setup guide for the 13 MCP workflow prompts, eight tools, host requirements, and privacy boundaries. npm analytics defaults off; npm installation alone does not register native agent hooks or supply model access. The npm release procedure documents source and package checks.
Cursor source candidate: CARBON Core 1.32.23-cursor.5 · Cursor-specific privacy. Bounded native HTTP smoke passed; marketplace review remains pending.
Grok Bot source prerelease: CARBON Core 1.0.2 · Grok-specific privacy. Local protocol tests passed; native Grok testing and marketplace review remain pending.
Use the model access you already have. In Claude Code, Codex, and other coding agents, CARBON's default testing workflows use the host's configured model access. When the host uses an eligible subscription, CARBON uses that allowance—no separate CARBON model API key is required. If the host uses API credentials or a company LLM proxy, that billing and data policy apply instead. Plan limits and extra-usage charges still apply; CARBON Pro licensing is separate.
Local execution and local reports—not a promise that no data leaves your machine. For local runs, project files, test evidence, and reports are stored in your local workspace. Your coding agent can send selected code, screenshots, prompts, and other context to its configured model provider. Local CARBON is not automatically offline or air-gapped. Cloud runs, external integrations, and optional direct-model checks have separate data flows and may have separate costs. Command-usage analytics vary by edition; review that edition's privacy policy and settings.
To confirm your billing route, check /status in Claude Code or codex login status in Codex. A configured API key can select API billing instead of subscription usage. Standalone MCP clients must supply their own model access and execution tools; installing an MCP server does not include a model subscription.
Free and open source. AI software testing and quality assurance inside Claude.
AI testing inside your coding agent. Built by testers.ai.
CARBON gives your coding agent risk-based testing instructions and a local evidence runtime. The agent inspects your authorized project, runs checks using its available browser, terminal or API tools, and records findings in a live report. CARBON's MCP server does not independently run the investigation or manufacture results.
Four compact report views help you move from a decision to its evidence:
Zoom screenshots, keep the full record one click away, and export portable HTML/JSON. Live reports retain their last good snapshot and quietly reconnect after interruption. Unknown and deferred checks remain distinct from passing checks.
Jay, the AI test manager, now introduces the assessment and appears in reports. Specialist profiles use role-based names and new light/dark icon identities rather than human names and photographs. They remain AI perspectives, not human reviewers. See the AI testing team, visual profile gallery, command guide, and MCP tool reference. Role names describe AI testing perspectives, not independent human review.
| Skill | Purpose |
|---|---|
carbon | Bounded risk-based assessment, including business value and persona journeys |
carbon-demo | Create a disposable sample project, then assess it |
carbon-test | Test one named behavior, feature or change |
carbon-issues | Bug hunt with at least half the budget for stateful and persona exploration |
carbon-accessibility | Focused accessibility investigation with evidence and limitations |
carbon-map | Explore screenshots, checks and findings from the current assessment |
carbon-help | Choose an appropriate Free workflow |
carbon-settings | Change local planning defaults and analytics preference |
jay | Talk to your AI test manager; j is an alias |
full | Run a comprehensive, resumable campaign using Core capabilities |
carbon-background | Control bounded local quick checks in supported hosts |
carbon-pro | Explore the separate Pro edition without starting checkout |
Twelve distinct commands, with thirteen skill entrypoints including the j alias. Host prefixes differ; Claude normally uses /carbon:command.
All recorded findings, persona journeys, HTML/JSON exports and current-run maps are included. No CARBON account, payment or finding unlock is required. Your coding-agent subscription or API usage is separate. The usual 20-minute/20-check planning default is adjustable, not a coverage guarantee or hard run quota.
Requirements: Node.js 22 or later; Python 3.10 or later for the optional demo creator. No npm install is needed for the MCP runtime. Browser automation depends on the tools your coding agent has available. Optional demo tests have their own documented dependencies.
git clone https://github.com/jarbon/carbon-free.git
claude --plugin-dir /absolute/path/to/carbon-free
Replace the path with your checkout. Claude Code normally prefixes plugin skills with the plugin name. Try these three examples:
/carbon:carbon — assess the current project. If the folder is empty or the target is unclear, Jay asks what to test: a URL, folder/repository, API, app/feature, or requirements. With a clear target, he runs a broad assessment and reports findings, evidence-qualified confidence, gaps, and next steps./carbon:carbon-issues ./my-app — investigate bugs, including state transitions and multi-step journeys, in an authorized project./carbon:carbon-accessibility http://localhost:3000 — test an app you control; report actual evidence and untested criteria separately.Use /carbon:carbon-map for the latest assessment or /carbon:carbon-settings to adjust defaults. Names and embedded-browser support can vary by host/version; use the host's skill picker. Install one CARBON edition at a time because editions share the carbon namespace. This repository is not a claim of Anthropic approval or listing.
The bundle also contains a Codex manifest. Other MCP hosts may launch node /absolute/path/to/carbon-free/server/index.mjs, then expose the bundled skills through their supported mechanism. A chat host without local process/browser access cannot provide the same runtime behavior. Test the surface you intend to use.
server/index.mjs, using Node standard libraries.runtime/carbon/scripts/carbon_demo.py via Python. Fixtures are synthetic examples, some intentionally imperfect; never deploy them as production apps..carbon/free/. Existing reports are retained. Uninstalling does not erase evidence.127.0.0.1 and use random access tokens. The agent opens them with its own browser/panel tool where supported. Saved HTML remains usable after the runtime stops. Review exports before sharing.https://cdn.usefathom.com/. It does not send prompts, source, target URLs, screenshots, findings, credentials or a stable user identifier. Network metadata is visible to that service. Set CARBON_ANALYTICS=off before startup or disable analytics in settings. No telemetry is sent merely by importing the module..config/carbon/ in your user home. Project evidence has no automatic expiration; you control retention.See the privacy policy for data handling, retention and contact details. There is no private benchmark fetch, reviewer service, remote MCP backend or Pro unlock code in this bundle.
Only recorded evidence is displayed. Unexecuted tests remain blocked or deferred; suspected issues are distinguished from demonstrated failures. Confidence is scoped engineering judgment, not a calibrated probability that the whole product is correct. AI persona feedback is simulated, not human research. Accessibility results are not a certification or legal opinion. This Free runtime does not generate formal DOCX conformance documents or run continuous automatic repair.
node --version, reload the plugin and inspect the host's MCP connection status. Run claude plugin validate . from the checkout.carbon_report or open its saved HTML.python3 --version and the selected fixture's README.Product/security support: jason@testers.ai. Reproducible non-sensitive problems: GitHub issues.
From the repository root, run node tests/smoke.mjs .. The checks use temporary synthetic projects and disable analytics. They exercise the MCP interface, demo copying, report lifecycle, evidence exports, settings persistence, authentication, cross-origin rejection and symlink protection. They do not certify accessibility, security, or performance of an application under test.
Open source under the MIT Licens
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요