@whatic/mcp
# @whatic/mcp
Local stdio MCP proxy for the [whatic.io](https://whatic.io) IC-discovery
MCP server.
whatic.io runs a remote MCP server (streamable-http) at
`https://whatic.io/mcp` exposing IC-discovery tools (`find_parts`,
`get_specs`, `compare_parts`, `search`, `lookup`, `get`, `get_image`). Many
MCP clients only support launching a local process over stdio. This package
is that local process: it forwards everything to the remote server. It
contains no tool logic of its own.
## Usage
Once published, add to your MCP client config:
```json
{
"mcpServers": {
"whatic": {
"command": "npx",
"args": ["-y", "@whatic/mcp"]
}
}
}
```
For Claude Code:
```bash
claude mcp add whatic -- npx -y @whatic/mcp
```
Until published to npm, run from a local checkout instead:
```bash
git clone https://github.com/pitkonst/whatic-mcp.git
cd whatic-mcp
npm install
npm run build
node dist/index.js
```
and point your client's `command`/`args` at `node` / `["<path-to-repo>/dist/index.js"]`.
## Configuration
- `WHATIC_MCP_URL` — override the remote MCP server URL (defaults to
`https://whatic.io/mcp`). Useful for pointing at a local or staging
what-ic server during development.
## Development
```bash
npm install
npm run build # compile TypeScript to dist/
npm run smoke # verify the live remote server end-to-end
```
There is no unit test suite: this package has no business logic beyond
forwarding requests to the remote server, so `npm run smoke` (a real
round-trip against the live endpoint) is the meaningful check.
TDQS
Scored across 7 tools
find_parts, get_specs, compare_parts, and get_image are clearly distinct, while search, lookup, and get_segments overlap in the retrieval workflow but have explicit descriptions that differentiate triage, fused retrieval, and ref expansion. Minor boundary ambiguity remains between get_specs and lookup, but the descriptions provide enough guidance.
Most tools follow a predictable verb_noun pattern: find_parts, get_specs, compare_parts, get_segments, get_image. The bare-verb names search and lookup are minor deviations that remain readable and do not obscure their purpose.
Seven tools form a well-scoped toolkit for IC parametric discovery and datasheet retrieval. Each tool earns its place by covering a distinct step in the workflow without unnecessary duplication or bloat.
The toolset covers the full read-only datasheet research lifecycle: parametric discovery, normalized spec lookup, distributor comparison, corpus search, full segment retrieval, and figure extraction. There are no obvious dead ends or missing operations for the stated domain.