Enterprise MCP Kit

A reusable foundation for secure, job-oriented enterprise MCP connectors.

First reference integration: NetBox device lookup

The first tool answers one bounded question: what does NetBox know about this device? It will retrieve a small, explainable inventory summary by device name or ID. It will not create, update, delete, or expose a generic NetBox API surface.

AI client -> get_device_context -> NetBox REST API (read-only) -> evidence-bounded device summary

Related MCP server: netbox-mcp

Implemented adapter contract

• Input: exactly one device name or numeric id.

• Output: device identity, status, site, role, device type, primary IP, and source record reference.

• Boundaries: no writes, no bulk enumeration, no arbitrary filters, and no secret values in tool output.

• Authentication: a least-privilege NetBox API token supplied only at runtime in the adapter options.

• Transport: GET only, with a configurable base URL and a five-second default timeout.

• Base URL: HTTP and HTTPS are accepted for local labs; production deployment policy must require HTTPS. Embedded URL credentials are rejected.

• Name lookup: queries the NetBox device endpoint, then accepts exactly one exact-name result.

• Errors: validation and HTTP failures are stable and never include tokens or raw response bodies.

Repository layout

docs/
  netbox-device-lookup.md
src/
  netbox-client.ts
test/
  netbox-client.test.ts

Status

The NetBox adapter and mocked MCP protocol tests are implemented. Run the local stdio server with NETBOX_BASE_URL, NETBOX_TOKEN, and optionally NETBOX_TIMEOUT_MS; live NetBox compatibility remains unverified.

Local commands

npm install
npm run build
npm run typecheck
npm test
npm run validate

References

• MCP TypeScript SDK

• NetBox REST API documentation

License

Licensed under the Apache License 2.0.