ElectroHire for AI Agents

Public API, MCP server, agent skills, and SDKs for ElectroHire — the AI-powered electronics engineering marketplace. This repository is the open, agent-facing surface of ElectroHire: everything an AI agent (or a developer building one) needs to interact with ElectroHire programmatically.

Status: live beta. The API and MCP server run on the beta endpoints (https://api-beta.electrohire.com, https://mcp-beta.electrohire.com/mcp) against the invite-only ElectroHire beta platform: public read surfaces (content, FAQ, pricing, blog, events), the three estimator tools, and the action tools (Ellie analysis, newsletter subscribe, support ticket) behind personal API keys or OAuth 2.1. The ElectroHire website repository itself is private; this repo is public by design.

Components

Runtimes are TypeScript on Cloudflare Workers (free-tier-first). Python exists as an SDK for agent developers — see docs/architecture.md for the full component map, the event-driven "reactor" backend pattern, and the versioning policy.

Related MCP server: Parts Finder MCP

Quickstart

API

pnpm install
pnpm --filter @electrohire/api dev        # local Worker via wrangler
curl http://localhost:8787/v1/health
# {"status":"ok","version":"0.7.0"}
curl http://localhost:8787/openapi.json    # OpenAPI 3.1 document

MCP server

pnpm --filter @electrohire/mcp dev         # local Worker via wrangler

Then point any MCP client at the server's /mcp endpoint. The server ships 14 tools: content, FAQ, pricing and search; blog and events; the three estimator tools; and the action tools (Ellie session/analysis, newsletter subscribe, support ticket). See docs/connectors.md for the full list.

Python SDK

pip install -e sdk/python

from electrohire import ElectroHireClient

client = ElectroHireClient()               # defaults to https://api-beta.electrohire.com
print(client.health())                     # -> {"status": "ok", "version": "0.7.0"}

Feature parity

The API and MCP server stay in step with the ElectroHire website and platform by rule, not by cleanup pass: every feature added, changed, or removed carries an API/MCP parity assessment in the same change, recorded in parity-manifest.json — the checked-in source of truth, kept current by a CI drift check. On top of that, the coverage gate (tools/check-coverage.mjs, also in CI) enumerates the served OpenAPI operations, the MCP tools, and every tool/endpoint the skills, connector guides, docs, and SDK refer to — and fails the build when they diverge. The discipline, the parity states, and the deprecate-before-removal rule are in docs/FEATURE-PARITY.md.

Versioning

Every component is semantically versioned on its own. The API is additionally URL-versioned (/v1); MCP tools and skills carry their own versions. Releases are git tags (v*) with GitHub Releases and a CHANGELOG entry. Details: docs/architecture.md.

Security

Do not put API keys or secrets in issues or pull requests. To report a vulnerability, use GitHub's private vulnerability reporting for this repository — see SECURITY.md. API action tools act only as the user who authorized them; estimates returned by any surface carry their ranges and stated assumptions. No payments run through the API or MCP, in any phase.

Contributing

See CONTRIBUTING.md. This project is licensed under the MIT License — © ElectroHire Inc.