Serve the agent's workflow tools from a Texera MCP server

Abierto
#9,457 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
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Refactorización
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
scala
Área
ai, backend

Línea de trabajo

Start with the linked context: #5610 (the inline-tools decision being revisited), #9464 (moves the agent onto the shared workflow and is a prerequisite), and #8663 (aicam's prototype, the open question of whether to build on it). Locate where the agent service currently registers its workflow tools and operator lookup, then trace how the once-loaded private workflow copy is read. Done means one Texera MCP server exposing those tools and the operator lookup, authenticated with the user's token and editing the shared workflow, with the agent and outside assistants both calling it.

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

Descripción

Task Summary

Today the agent's tools run inside the agent service and edit a private copy of the workflow. That copy is loaded once, before the first prompt, so a change the user makes between prompts gets overwritten. #9464 fixes this by moving the agent onto the shared workflow.

This task moves the tools from #9481 onto one Texera MCP server, with the same names and inputs. The agent and outside assistants (#8663) call it, and its tools edit the shared workflow through #9464. This revisits the inline-tools decision in #5610.

  • The server holds no session: every tool takes the workflow id, so any copy of the server can answer, as the current MCP revision (2026-07-28) expects.
  • It is built on the official server SDK (@modelcontextprotocol/server, Apache-2.0), which runs on Bun like the agent service.
  • Each tool says whether it only reads (readOnlyHint), so a client can ask the person before a change.
  • From aicam's prototype in #8663, the shared client package and the test harness can be kept. Its workflow editing holds a session in the server's memory (workflow_open to workflow_save), which the shared session replaces.
  • The agent calls the server with the user's token, as its backend calls do today. The MCP specification, though, has a server accept only tokens issued for it, and today's Texera tokens name no audience. So an outside assistant can use a token the person pastes in, while signing in from an assistant needs an authorization server, which Texera does not have yet.

The dataset tools from #9377, which also cover #4588, will come later on the endpoints from #9395. Review mode (#9075) waits on #9464.

A change made between two prompts is lost After: one MCP server and one copy of the workflow
Task Type
  • Refactor / Cleanup
  • DevOps / Deployment / CI
  • Testing / QA
  • Documentation
  • Performance
  • Other
Lenguaje dominante
Scala
Estrellas
333
Forks
202
Merge medio
3 d 11 h
PR fusionados (30 d)
185

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 apache/texera

Todos los issues de apache/texera

Issues similares

Más issues de Scala

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.