Skip to content

External MCP Client API / Permissions #23

@jasonjmcghee

Description

@jasonjmcghee

I haven't yet seen discussions around external MCP clients (outside of the browser context).

(Please let me know if I missed something in the current specification or subsequent discussions)

I could imagine users wanting to use their normal mcp client, like Claude Desktop / Code, Copilot, Cursor, etc. to interface with WebMCP.

The security model is clearly different than self-contained and prone to all the same attack vectors like prompt injection etc, and likely more dangerous due to potentially pre-approved commands etc.

All that being said, external permissions, e.g. webcam, microphone, etc are not unheard of in the browser.

Just wanted to bring this up- is this a goal or anti-goal of the proposal in its current form?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions