An MCP server that MCP clients can connect to (read-only first)

Abierto
  • ¿Algo no está bien?
#1,607 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
api, backend, devtools

Línea de trabajo

Start with docs/mcp-server.md and the manifest served at GET /api/v1/mcp/manifest, then the REST endpoints under /api/v1/ai/. The issue is design-gated: the language, package, authentication and tool list must go through plan and review before any code. Done means a plan approved by maintainers, then a stdio server that reads flags and experiments with the caller's credentials.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Today the platform serves an MCP manifest at GET /api/v1/mcp/manifest (five tools described) and REST endpoints under /api/v1/ai/, but it does not run an MCP server: an MCP client such as Claude Code or Cursor cannot connect to it, as docs/mcp-server.md says. Six of the eight competitors in the 31 October research have one (GrowthBook on every tier, LaunchDarkly, Datadog, PostHog among them).

Wanted before launch (founder, 2026-11-02): a real MCP server that an MCP client can connect to.

  • First version read-only, over the existing API, with the caller's own credentials, so it can do nothing the caller's role cannot: list and read flags, evaluate a flag for a user, list experiments and read their results. Write tools (toggle a flag, create an experiment) come after, under the same role checks as the API.
  • Runs locally next to the client (stdio), pointed at the user's own Controlvar instance; no hosted service.
  • A small tool set, each tool's description and inputs pinned by a test, and the existing manifest either replaced by it or kept true.
  • Docs: docs/mcp-server.md rewritten to say how to connect a client.

Publishing the package to a registry is a separate step that waits for the founder at that moment.

The design (language, package, authentication, tool list) goes through the usual plan and review before any code.

Lenguaje dominante
Python
Estrellas
0
Forks
4
Merge medio
5 h 19 min
PR fusionados (30 d)
503

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Controlvar/controlvar

Todos los issues de Controlvar/controlvar

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.