3 ms·

This is an interesting take since web developers could add mcp tools into their apps rather than having browser agents having to figure out how to perform actio

This is an interesting take since web developers could add mcp tools into their apps rather than having browser agents having to figure out how to perform actions manually. Is the extension itself open source? Or only the extension-tools? In theory I should be able to write a chrome extension for any website to expose my own custom tools on that site right (with some reverse engineering of their APIs I assume)?

miguelspizza 1y ago
The extension should be open source. I had it as a private submodule until today. Let me figure out my it's not showing up and get back to you. The extension itself is a MCP server which can be connected to by other extension over cross extension messaging. Since the extension is part of the protocol, I'd like for the community to pull from the same important parts of the extension (MCPHub, content script) so they are consistent across extension implementations.
miguelspizza 1y ago
Ok it's open source now
- Flux159 1y ago
  Thanks! Took a very quick look. It seems like the extension exposes tools for all domains that support mcp-b looking at DomainToolManager - does this mean if I have two tabs for a single domain you'll have duplicate tools per tab? Haven't had enough time to look through all the code there - interesting problem I guess since a single domain could have multiple accounts connected (ex: gmail w/ account 0 vs account 1 in different tabs) or just a single account (ex: HN).
  - miguelspizza 1y ago
    No there is built in tool de-duping. I'm not sure how to handle domains with different url states though. Like you said there are some edge cases where two tabs of the same website expose different tool sets or have tools of the same name but would result in different outcomes when called. Curios if you have any thoughts on how to handle this
    - t1amat 1y ago
      The user should be able to enable/disable tools or an entire tab’s toolset. Some keep open hundreds of tabs and that’s simply too many potential tools to expose. Deduping doesn’t make sense for the reasons you say, and that one logical task could lead to a series of operations missequenced across a range of tabs.

miguelspizza 1y ago

The extension should be open source. I had it as a private submodule until today. Let me figure out my it's not showing up and get back to you. The extension itself is a MCP server which can be connected to by other extension over cross extension messaging. Since the extension is part of the protocol, I'd like for the community to pull from the same important parts of the extension (MCPHub, content script) so they are consistent across extension implementations.

miguelspizza 1y ago

Ok it's open source now

Flux159 1y ago
Thanks! Took a very quick look. It seems like the extension exposes tools for all domains that support mcp-b looking at DomainToolManager - does this mean if I have two tabs for a single domain you'll have duplicate tools per tab? Haven't had enough time to look through all the code there - interesting problem I guess since a single domain could have multiple accounts connected (ex: gmail w/ account 0 vs account 1 in different tabs) or just a single account (ex: HN).
- miguelspizza 1y ago
  No there is built in tool de-duping. I'm not sure how to handle domains with different url states though. Like you said there are some edge cases where two tabs of the same website expose different tool sets or have tools of the same name but would result in different outcomes when called. Curios if you have any thoughts on how to handle this
  - t1amat 1y ago
    The user should be able to enable/disable tools or an entire tab’s toolset. Some keep open hundreds of tabs and that’s simply too many potential tools to expose. Deduping doesn’t make sense for the reasons you say, and that one logical task could lead to a series of operations missequenced across a range of tabs.