Install
$ agentstack add mcp-oaslananka-kicad-studio-kit ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
KiCad Studio Kit
KiCad Studio Kit is the VS Code extension repository. The MCP server is developed and released separately. This repository owns only the extension-side MCP discovery, configuration, compatibility metadata, and user experience — see [ADR 0009](docs/adr/0009-split-kicad-mcp-pro-into-separate-repository.md) and [repository structure](docs/architecture/repo-structure.md).
This repository contains:
- the KiCad Studio VS Code extension (
apps/vscode-extension) — the only released product here; - private shared test infrastructure (
packages/test-harness,packages/kicad-fixtures); - the extension-side MCP integration contract and compatibility metadata.
The KiCad MCP Pro server (kicad-mcp-pro) — its Python source, npm launcher, container image, and MCP Registry listing — lives in oaslananka/kicad-mcp.
Canonical repository: https://github.com/oaslananka/kicad-studio-kit Searchable documentation: https://oaslananka.github.io/kicad-studio-kit/
Version Baseline
This repository's local release surface is:
- VS Code extension:
oaslananka.kicadstudiokit(1.9.0)
The Python package kicad-mcp-pro, container image, and MCP Registry listing are released from oaslananka/kicad-mcp.
KiCad Compatibility
KiCad Studio Kit treats KiCad 10.0.x as the primary tested line, keeps KiCad 9.x as deprecated best-effort compatibility after upstream EOL, and keeps KiCad 8.x as deprecated file-level compatibility. The canonical matrix, tested patch versions, CI coverage level, and feature gates are maintained in [docs/support-matrix.md](docs/support-matrix.md) and compatibility.yaml.
Local Validation
corepack enable
corepack pnpm run dev:doctor
corepack pnpm install --frozen-lockfile
corepack pnpm run check:forbidden-refs
corepack pnpm run check:version
corepack pnpm --filter kicadstudiokit run check
corepack pnpm --filter kicadstudiokit run package
Product-scoped entrypoints are available from the root:
corepack pnpm run check:kicad-studio
corepack pnpm --dir packages/test-harness run check
corepack pnpm run check:protocol-schemas
corepack pnpm run check:compatibility-contract
corepack pnpm run check:dev-doctor
Python/MCP server checks run from the oaslananka/kicad-mcp repository.
For a reproducible VS Code Dev Containers or GitHub Codespaces environment, use the checked-in [devcontainer configuration](docs/devcontainer.md). The container sets up Node, pnpm, Python, uv, Playwright, shellcheck, actionlint, GitHub CLI, and best-effort KiCad CLI support for root checks and MCP tests.
Install
Install the extension from the Visual Studio Marketplace or Open VSX, or build it locally:
corepack enable
corepack pnpm install --frozen-lockfile
corepack pnpm run package:kicad-studio
Usage
Open a workspace containing a KiCad project and use the KiCad Studio activity bar views and commands. See [docs/getting-started.md](docs/getting-started.md) for the guided workflow and [docs/extension/commands.md](docs/extension/commands.md) for the command catalog.
Architecture
- Searchable documentation site
- [Repository structure](docs/architecture/repo-structure.md)
- [Product boundaries](docs/architecture/product-boundaries.md)
- [Release model](docs/architecture/release-model.md)
- [Testing strategy](docs/testing-strategy.md)
- [Dev container](docs/devcontainer.md)
- [KiCad fixture corpus](docs/kicad-fixture-corpus.md)
- [Integration model](docs/integration/kicad-studio-mcp.md)
- [Agent onboarding](docs/agents/index.md)
- [MCP client config examples](examples/mcp-clients/README.md)
- [VS Code MCP workspace example](.vscode/mcp.example.json)
Examples
- [Examples overview](examples/README.md)
- [LED Basic KiCad example](examples/led-basic/README.md)
- [MCP Workflow Demo](examples/mcp-demo/README.md)
Publishing
Publishing is handled by GitHub Actions workflows under .github/workflows. External setup for environments, marketplace secrets, and trusted publishers is documented in [docs/publishing.md](docs/publishing.md). The structured preview (beta) program and tester feedback loop for the stable 1.x line are documented in [docs/beta-program.md](docs/beta-program.md).
Maintenance
Dependency update policy, dashboard triage, and security-update handling are documented in [docs/dependency-lifecycle.md](docs/dependency-lifecycle.md). Compatibility support states and release gates are documented in [docs/support-matrix.md](docs/support-matrix.md). Canonical repository and portfolio workflow status are recorded in [CANONICAL.md](CANONICAL.md), [.repo-health.yaml](.repo-health.yaml), and [docs/reusable-workflows.md](docs/reusable-workflows.md). Telemetry and error reporting are opt-in, disabled by default, and documented in [docs/telemetry.md](docs/telemetry.md).
Contributing
Read [CONTRIBUTING.md](CONTRIBUTING.md) and run corepack pnpm run check before opening a pull request.
License
KiCad Studio Kit is available under the [MIT License](LICENSE).
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: oaslananka
- Source: oaslananka/kicad-studio-kit
- License: MIT
- Homepage: https://oaslananka.github.io/kicad-studio-kit/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.