MCP Clients
Model Context Protocol integration for Claude Code and AI agents.
Overview
MCP (Model Context Protocol) clients let Claude Code and AI agents interact with UluOps directly — no SDK, no boilerplate. Same APIs, stdio/JSON-RPC transport.
Design Philosophy — Both MCP clients follow the thin client pattern — zero business logic lives in the client. All validation, storage, and analytics are handled by the backend. The client's only job is protocol translation between MCP's stdio-based JSON-RPC and the REST API.
Available Clients
uluops-ops-mcp
48 tools across 6 tool groups. Save runs, manage issues, analytics, taxonomy, analysis records. Backed by the Platform API.
npm install @uluops/ops-mcpuluops-registry-mcp
44 tools across 8 tool groups. Browse, publish, fork definitions, track effectiveness and health, manage models and languages. Backed by the Registry API.
npm install @uluops/registry-mcpChoosing: SDK vs MCP
| Use Case | SDK | MCP |
|---|---|---|
| CI/CD pipeline integration | Recommended | — |
| Claude Code agent workflows | — | Recommended |
| Custom application with full type safety | Yes | — |
| Interactive analysis with an AI agent | — | Yes |
| Browser/frontend integration | Yes (registry-sdk) | — |