mcporter and opik-mcp
These are **ecosystem siblings**: mcporter provides the foundational TypeScript framework for calling any MCP server (including opik-mcp), while opik-mcp is a specialized MCP server implementation that users would invoke through mcporter or similar MCP clients.
About mcporter
steipete/mcporter
Call MCPs via TypeScript, masquerading as simple TypeScript API. Or package them as cli.
Supports zero-config MCP discovery across Cursor, Claude Desktop, Codex, and Windsurf with automatic transport pooling and environment variable expansion. Generates typed TypeScript clients (`.d.ts` or runnable wrappers), single-command CLIs with optional bundling, and provides ergonomic camelCase APIs with built-in OAuth caching, JSON-schema validation, and content helpers (`.text()`, `.markdown()`, `.json()`, `.images()`). Handles stdio, HTTP, and SSE transports uniformly with ad-hoc endpoint support and auto-detected OAuth promotion for hosted MCPs.
About opik-mcp
comet-ml/opik-mcp
Model Context Protocol (MCP) implementation for Opik enabling seamless IDE integration and unified access to prompts, projects, traces, and metrics.
Supports both stdio and streamable-http transports, enabling local IDE integration and remote self-hosted deployments with configurable authentication and workspace resolution. Exposes MCP resources, resource templates, and prompts for metadata-aware workflows, plus modular toolsets (core, integration, expert-prompts, metrics) that can be selectively enabled via CLI or environment configuration.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work