Agent Tools by oaslananka

Engineering, EDA, PCB, and developer-automation tools for AI agents.

This repository is the central catalog, documentation hub, and distribution entry point for agent-facing tools built around MCP servers, plugins, skills, and repeatable engineering workflows.

Purpose

agent-tools is not a monorepo for every MCP server. It is the public hub that helps agents and developers discover the right tool, understand compatibility, copy templates, and install supported plugins once their source repositories contain valid manifests.

Project-specific plugins and skills should live inside their own source repositories so their instructions stay synchronized with the actual tools, commands, schemas, and releases.

agent-tools         = marketplace / catalog / templates / shared docs
kicad-mcp           = KiCad MCP server + KiCad-specific plugin + KiCad skills
easyeda-mcp-pro     = EasyEDA MCP server + EasyEDA-specific plugin + EasyEDA skills
zaptrace            = product repository + product-specific plugin and skills
a2amesh             = product repository + product-specific plugin and skills

Current status

Tool	Repository	Status	Notes
KiCad MCP	oaslananka/kicad-mcp	Active	Product-level plugin manifest and KiCad-specific skills are available in the source repository.
EasyEDA MCP Pro	oaslananka/easyeda-mcp-pro	Active	Product-level plugin manifest and EasyEDA-specific skills are available in the source repository.
SSH MCP Pro	oaslananka/ssh-mcp-pro	Active	Runtime package available.
Infra Lens MCP	oaslananka/infra-lens-mcp	Active	Runtime package available.
Debug Recorder MCP	oaslananka/debug-recorder-mcp	Active	Runtime package available.
Health Monitor MCP	oaslananka/health-monitor-mcp	Active	Runtime package available.
Zaptrace	oaslananka/zaptrace	Future	Should be published as its own product-level plugin when ready.
A2A Mesh	oaslananka/a2amesh	Active	Published @a2amesh/mcp server, product plugin, bounded skills, and runtime configurations are available.

The marketplace file now exposes active entries for product repositories that contain validated product-level manifests and runtime configuration. Future products remain under planned_plugins until their source repositories are ready.

Recommended repository model

agent-tools/
├── README.md
├── .claude-plugin/
│   └── marketplace.json
├── docs/
│   ├── install.md
│   ├── plugins.md
│   ├── skills.md
│   ├── supported-agents.md
│   ├── publishing.md
│   ├── agent-install-matrix.md
│   └── chatgpt-apps-remote-mcp-plan.md
├── templates/
│   ├── plugin.json
│   ├── SKILL.md
│   ├── README-plugin-section.md
│   └── agent-runtime/
│       ├── codex-config.example.toml
│       ├── vscode-mcp.example.json
│       └── opencode.example.jsonc
├── examples/
│   ├── kicad.md
│   ├── easyeda.md
│   └── multi-agent-eda.md
└── skills/
    └── generic/
        └── pcb-design-principles/
            └── SKILL.md

Install concept

This repository is the marketplace entry point for active product plugins:

/plugin marketplace add oaslananka/agent-tools

Then individual plugins can be installed from the marketplace according to the agent runtime being used.

Use each product repository as the source of truth for runtime behavior and this repository for discovery, templates, publication rules, and shared agent workflow documentation.

What belongs here

• Marketplace metadata and catalog entries
• Product discovery documentation
• Installation and publishing guides
• Shared plugin and skill templates
• Agent compatibility notes
• OpenCode runtime template and install matrix
• Publish readiness matrix: docs/publish-readiness-matrix.md
• Generic, product-independent engineering skills
• Examples for multi-agent engineering workflows

What does not belong here

• MCP server source code
• Product-specific tool schemas
• KiCad-specific or EasyEDA-specific operational skills
• Release-sensitive tool documentation
• Product-specific tests and fixtures
• Anything that must change in lockstep with a specific MCP server release

Publication rule

A plugin should only be listed as active in .claude-plugin/marketplace.json when its source repository contains a valid .claude-plugin/plugin.json file and the plugin has at least one tested installation path.

Commercial direction

This hub is designed to support a professional agent-tool ecosystem around engineering automation. It can grow into a public catalog for:

• MCP server distribution
• Agent skills for EDA and hardware workflows
• Paid consulting and integration work
• Sponsored workflow examples
• Enterprise-ready installation documentation
• Community contributions around agent-native engineering automation

Next milestones

1. Keep active plugin install paths verified against their product releases.
2. Track ChatGPT/OpenAI Apps remote MCP readiness separately from local MCP packaging.
3. Record tested and untested runtime support accurately.
4. Publish the next catalog release after the active-entry matrix is verified.