Serve the agent's workflow tools from a Texera MCP server
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
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_opentoworkflow_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.
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
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/texera
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
addOperator returns an error but still adds the operatorPosiblemente ocupada @sunny-kavixo la tomó hace 5 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
apache/texera#9121 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Failed tool calls are marked as succeeded (isError is always false)Posiblemente ocupada @oliarmak-web la tomó hace 14 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
apache/texera#9120 · 8 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
apache/texera#8682 · 5 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de apache/texera
Issues similares
-
? - Needs Triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
NVIDIA/cudf-spark#16937 ·
Los mantenedores suelen responder en 1 día
-
LFST not-issued-store count truncation can incorrectly clear strictShouldWaitPosiblemente ocupada @weidingliu la tomó hoy. Abiertomodule: memory type: bug/reported
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
OpenXiangShan/XiangShan#6974 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 3 días
-
bug indigo
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
PurpleKingdomGames/indigoengine#300 · 1 comentario ·
-
JavaReservoirSampleOperator returns the whole input when the dataset size is unknownPosiblemente ocupada @sasmith-14 la tomó hace 2 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
apache/wayang#884 · 3 comentarios ·
Los mantenedores suelen responder en 2 días
-
AI Generated CI/CD ⚒️ Flaky-tests 🐦 python 🐍
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
valkey-io/valkey-glide#7722 ·
Los mantenedores suelen responder en 1 día