Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

App -> Agent explicit integration/manifest?

Abierto
  • ¿Algo no está bien?
#242 4 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
javascript, web-dev
Área
api, design

Línea de trabajo

Start by reading the WebMCP proposal and discussion around registering tools and how agents invoke them; the issue does not name specific files or tests. Identify whether browser UI for choosing an agent provider and a way for pages to detect available handlers belong in scope. Done means the scope and expected integration flow are clearly decided.

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

Descripción

As best as I can tell, most of WebMCP is around the plumbing of exposing in-page capabilities through an API to Agent(s) (either external, browser-supplied or in-page).

Is the page->agent triggering flow in-scope (or did I miss it)?

I "built" a CVE analysis tool with built in LLM for exploring CVE data (mostly because I had some questions I wanted to answer, I had tokens to burn and it felt like a fun exercise). Instead of building out a complicated UI for filtering the data and running the queries, I thought it would be a lot easier to just use a LLM to do all of that and just use a chat box.

Right now the built-in LLM runs on a single consumer GPU in my house and runs a pretty small Qwen model (tested best for generating the SQL queries) but I also have subscriptions to most of the AI providers, browser extensions installed for a lot of them and the "Ask Gemini" browser-provided UI for my Gemini subscription. Any one of these would be orders-of-magnitude better than the LLM I provide directly.

I can expose a WebMCP endpoint for everything the app-provided LLM uses and it should have 100% access to run the analysis engine but it doesn't feel like there are plans for how to make that a seamless experience for the user.

Optimally, registering the WebMCP tools would be able to trigger some sort of browser UI that lets the user pick a provider to use (extension or browser native UI) but it would be cleanest if I could know that the current user's browser had some way to handle that so I could offer UI to steer them to click a button to use their own LLM and hide the built-in chat window when the external chat is being used.

Lenguaje dominante
Bikeshed
Estrellas
4.7k
Forks
328
Merge medio
2 d 15 h
PR fusionados (30 d)
16

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 webmachinelearning/webmcp

Todos los issues de webmachinelearning/webmcp

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.