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

Host-controlled WebMCP access between iframes

Abierto
  • ¿Algo no está bien?
#317 1 comentario 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
html
Área
api

Línea de trabajo

Start by reading the WebMCP permission model, especially how exposedTo and fromOrigins currently govern cross-origin tools; the issue does not name specific files or tests. Decide whether hosts should be able to delegate separate provider and consumer capabilities, and define how providers opt into host-authorised exposure. Done means the permission and provider opt-in model supports the described iframe topology without requiring apps to know the agent origin.

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

Descripción

enhancement

Consider a host application that composes several cross-origin applications in iframes, with one iframe containing an agent:

Host
├── Agent iframe
├── App A iframe
├── App B iframe
└── App C iframe

Apps A–C may expose WebMCP tools. The host wants the agent to use those tools, but does not necessarily want the apps to discover or invoke tools exposed by other frames.

The host therefore wants to define a topology like:

Frame Expose tools Use tools
Agent no yes
App A yes no
App B yes no
App C yes no

The current model seems awkward for this use case because cross-origin access relies on providers and consumers knowing each other's origins through exposedTo and fromOrigins.

In a composed application, the embedded apps may not know or care which agent implementation the host uses. The host is the component that knows the intended relationship between the frames.

Would it make sense to separate the current tools permission into two independently delegatable capabilities, conceptually:

<iframe src="https://app.example"
        allow="tools-provide">

<iframe src="https://agent.example"
        allow="tools-consume">

This would let the embedding host decide which frames may expose WebMCP capabilities and which frames may consume them.

There would probably also need to be a way for a provider to opt into host-authorised exposure, rather than having to enumerate every possible consuming agent origin.

This seems particularly useful for host applications that compose independent first- and third-party web applications alongside an embedded agent.

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.