Skip to content
Back to search

mcp-superassistant

Brings MCP to ChatGPT, DeepSeek, Perplexity, Grok, Gemini, Google AI Studio, OpenRouter, DeepSeek, T3 Chat and more...

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/srbhptl39/mcp-superassistant with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/srbhptl39/mcp-superassistant'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/srbhptl39--mcp-superassistant/badge.svg)](/listings/srbhptl39--mcp-superassistant)

HTML

<a href="/listings/srbhptl39--mcp-superassistant"><img src="/api/listings/srbhptl39--mcp-superassistant/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 345 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. <!-- <img src="chrome-extension/public/icon-34.png" alt="MCP SuperAssistant Logo" width="100" height="100"> -->
  3. <h1>MCP SuperAssistant Chrome Extension</h1>
  4. </div>
  5. <p align="center">
  6. Brings MCP to ChatGPT, Perplexity, Grok, Gemini, Google AI Studio, OpenRouter, Kimi, Github Copilot, Mistral and more...
  7. </p>
  8. <p align="center">
  9. <a href="https://mcpsuperassistant.ai/" target="_blank"><strong>🌐 Visit Official Website</strong></a>
  10. </p>
  11. <!-- ![MCP SuperAssistant](chrome-extension/public/Cover3.jpg) -->
  12. <div align="center">
  13. <img src="chrome-extension/public/Cover5.jpg" alt="MCP SuperAssistant Cover" width="800">
  14. </div>
  15. <div align="center">
  16. ![Latest Release](https://img.shields.io/github/v/release/srbhptl39/MCP-SuperAssistant?style=flat-square&label=Latest%20Release&color=brightgreen)
  17. ![GitHub Stars](https://img.shields.io/github/stars/srbhptl39/MCP-SuperAssistant?style=flat-square&label=Stars)
  18. ![License](https://img.shields.io/badge/License-MIT-blue?style=flat-square)
  19. ![Chrome Users](https://img.shields.io/chrome-web-store/users/kngiafgkdnlkgmefdafaibkibegkcaef?style=flat-square&label=Chrome%20Users)
  20. ![Firefox Users](https://img.shields.io/amo/users/mcp-superassistant?style=flat-square&label=Firefox%20Users)
  21. ![Build Status](https://img.shields.io/badge/Status-Active-success?style=flat-square)
  22. </div>
  23. ## Installation
  24. <div align="center" style="display: flex; justify-content: center; gap: 20px; align-items: center;">
  25. <a href="https://chromewebstore.google.com/detail/mcp-superassistant/kngiafgkdnlkgmefdafaibkibegkcaef?hl=en"><img src="https://developer.chrome.com/static/docs/webstore/branding/image/HRs9MPufa1J1h5glNhut.png" alt="Chrome Web Store" width="200" height="auto" style="vertical-align: middle;" /></a>
  26. <a href="https://addons.mozilla.org/en-US/firefox/addon/mcp-superassistant/"><img src="https://blog.mozilla.org/addons/files/2015/11/get-the-addon.png" alt="Firefox Add-ons" width="200" height="auto" style="vertical-align: middle;" /></a>
  27. </div>
  28. <br>
  29. ## Overview
  30. MCP SuperAssistant is a Chrome and Firefox extension that brings Model Context Protocol (MCP) tools to the AI chat sites you already use, such as ChatGPT, Claude, Gemini, Perplexity and Grok. Tool calls written by the AI show up as compact cards you can run with one click, and the results go back into the conversation.
  31. ## Currently Supported Platforms
  32. - [ChatGPT](https://chatgpt.com/) (signed in or signed out)
  33. - [Claude](https://claude.ai/)
  34. - [Google Gemini](https://gemini.google.com/)
  35. - [Perplexity](https://perplexity.ai/)
  36. - [Grok](https://grok.com/) and [Grok on X](https://x.com/i/grok)
  37. - [Google AI Studio](https://aistudio.google.com/)
  38. - [OpenRouter Chat](https://openrouter.ai/chat)
  39. - [DeepSeek](https://chat.deepseek.com/)
  40. - [T3 Chat](https://t3.chat/)
  41. - [GitHub Copilot](https://github.com/copilot)
  42. - [Mistral AI](https://chat.mistral.ai/)
  43. - [Kimi](https://kimi.com/) ([kimi.ai](https://www.kimi.ai/))
  44. - [Qwen Chat](https://chat.qwen.ai/)
  45. - [Z Chat](https://chat.z.ai/)
  46. ## Demo Video
  47. Kimi.com
  48. [![MCP SuperAssistant Demo](https://img.youtube.com/vi/jnBPh2jzunM/0.jpg)](https://www.youtube.com/watch?v=jnBPh2jzunM)
  49. ChatGPT
  50. [![MCP SuperAssistant Demo](https://img.youtube.com/vi/PY0SKjtmy4E/0.jpg)](https://www.youtube.com/watch?v=PY0SKjtmy4E)
  51. Watch the demo to see MCP SuperAssistant in action!
  52. [MCP SuperAssistant Demo Playlist](https://www.youtube.com/playlist?list=PLOK1DBnkeaJFzxC4M-z7TU7_j04SShX_w)
  53. ## Setup Tutorial
  54. [![Setup Tutorial](https://img.youtube.com/vi/h9f_GX1Ef20/0.jpg)](https://www.youtube.com/watch?v=h9f_GX1Ef20&pp=ygUTbWNwIHN1cGVyIGFzc2lzdGFudA%3D%3D)
  55. **New to MCP SuperAssistant?** Watch this complete setup guide to get started in minutes!
  56. [View Setup Tutorial](https://www.youtube.com/watch?v=h9f_GX1Ef20&pp=ygUTbWNwIHN1cGVyIGFzc2lzdGFudA%3D%3D)
  57. ## What is MCP?
  58. The Model Context Protocol (MCP) is an open standard developed by Anthropic that connects AI assistants to systems where data actually lives, including content repositories, business tools, and development environments. It serves as a universal protocol that enables AI systems to securely and dynamically interact with data sources in real time.
  59. ## Key Features
  60. - **Multiple AI Platform Support**: Works with every site in the list above, in Chrome and Firefox
  61. - **Compact tool cards**: Each tool call renders as one quiet row (name, description, Run). Parameters, the raw call, run history and results stay folded until you open them
  62. - **Instruction chips**: The MCP instructions sit in a small chip in the chat bar instead of filling your message; your own text stays readable in the sent message
  63. - **Flicker-free rendering**: Cards replace the raw tool-call text before the page paints, so reloading a chat shows no raw JSON
  64. - **Tool Execution**: Execute MCP tools with a single click
  65. - **Tool Result Integration**: Seamlessly insert tool execution results back into the AI conversation
  66. - **Tab & page context**: Attach open tabs or capture the current page into the chat (optional; asks for browser access in a small window first)
  67. - **Browser tools** (optional): Let the AI read and, if you allow it, control your tabs, with a block list for sensitive sites
  68. - **Auto-Execute Mode**: Automatically execute detected tools
  69. - **Auto-Submit Mode**: Automatically submit chat input after result insertion
  70. - **Push Content Mode**: Option to push page content instead of overlaying
  71. - **Preferences Persistence**: Remembers sidebar position, size, and settings
  72. - **Dark/Light Mode Support**: Adapts to the AI platform's theme
  73. ```mermaid
  74. flowchart TD
  75. A[AI Chat Interface] -->|Generate| B[Tool Calls]
  76. B -->|Detect| C[Extension Detects Tool Calls]
  77. C -->|Send via SSE| D[MCP Local Proxy Server]
  78. D -->|Forward| E[Actual MCP Server]
  79. E -->|Return Results| D
  80. D -->|Return Results| C
  81. C -->|Insert| F[Add Results Back to Chat]
  82. ```
  83. ### Connecting to Local Proxy Server
  84. To connect the Chrome extension to a local server for proxying connections:
  85. #### Run MCP SuperAssistant Proxy via npx:
  86. 1. Create a `config.json` file with your MCP server details. For example, to use the [Desktop Commander](https://github.com/wonderwhy-er/DesktopCommanderMCP):
  87. **Example config.json:**
  88. ```json
  89. {
  90. "mcpServers": {
  91. "desktop-commander": {
  92. "command": "npx",
  93. "args": [
  94. "-y",
  95. "@wonderwhy-er/desktop-commander"
  96. ]
  97. }
  98. }
  99. }
  100. ```
  101. config.json also support other MCP server configurations like remote MCP server URLs.
  102. Try composio mcp, zappier mcp, or smithery or any other remote MCP server.
  103. **Or use existing config file location from Cursor or other tools:**
  104. ```
  105. macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  106. Windows: %APPDATA%\Claude\claude_desktop_config.json
  107. ```
  108. 2. Start the MCP SuperAssistant Proxy server using one of the following commands:
  109. ```bash
  110. npx -y @srbhptl39/mcp-superassistant-proxy@latest --config ./config.json --outputTransport sse
  111. ```
  112. or
  113. ```bash
  114. npx -y @srbhptl39/mcp-superassistant-proxy --config ./config.json --outputTransport streamableHttp
  115. ```
  116. or
  117. ```bash
  118. npx -y @srbhptl39/mcp-superassistant-proxy --config ./config.json --outputTransport ws
  119. ```
  120. **View all available options:**
  121. ```bash
  122. npx -y @srbhptl39/mcp-superassistant-proxy@latest --help
  123. ```
  124. This is useful for:
  125. - Proxying remote MCP servers
  126. - Adding CORS support to remote servers
  127. - Providing health endpoints for monitoring
  128. #### Connection Steps:
  129. 1. Start the proxy server using one of the commands above
  130. 2. Open the MCP SuperAssistant sidebar in one of the supported AI platforms, this should show the sidebar UI
  131. 3. Click on the server status indicator (usually showing as "Disconnected")
  132. 4. Enter the local server URL (default: `http://localhost:3006/sse`)
  133. URL format depends on the --outputTransport method used:
  134. - For SSE: `http://localhost:3006/sse`
  135. - For Streamable HTTP: `http://localhost:3006/mcp`
  136. - For WebSocket: `ws://localhost:3006/message`
  137. - Choose the appropriate transport method (SSE or Streamable HTTP or WebSocket)
  138. - You can add any remote MCP server URL here as well, if it supports CORS or is proxied via this local proxy server. Try [Composio mcp](https://mcp.composio.dev/), [Zappier mcp](https://zapier.com/mcp), or [smithery](https://smithery.ai/) or any other remote MCP server.
  139. 5. Click "Connect" to establish the connection
  140. 6. The status indicator should change to "Connected" if successful
  141. ## Usage
  142. Example Workflow:
  143. 1. Navigate to a supported AI platform example chatgpt.
  144. 2. The MCP SuperAssistant sidebar will appear on the right side of the page
  145. 3. Configure your MCP Tools to enable and disable the tools you want to use.
  146. 4. In the message prompt area, hover the 'MCP' button to see the available tools and their descriptions.
  147. 5. MCP SuperAssistant requires to add an MCP working instructions prompt to the chat, to give details of its new capabilities and how to use the tools. Use the 'Insert' or attach button to add the instructions prompt. It appears as a small "MCP Instructions" chip in the chat bar and is sent along with your next message.
  148. 6. Once the instructions prompt is added, Now you can ask it to read files or any related MCP tool operations.
  149. 7. When AI wants to use any tool it will show a compact tool call card with the tool name; open it with the chevron to see the parameters.
  150. 8. User can manually execute the tool call by clicking on the "RUN" button on the tool call card, or if Auto-Execute mode is enabled, it will execute automatically.
  151. 9. Automation can be achieved by enabling Auto-Execute and Auto-Submit modes, by clicking on the 'MCP' button and configuring the Auto modes.
  152. ## Tips & Tricks
  153. 1. **Turn off search mode** (chatgpt, perplexity) in AI chat interfaces for better tool call prompt experience and to prevent MCP SuperAssistant from getting derail.
  154. 2. **Turn on Reasoning mode** (chatgpt, perplexity, grok) in AI chat interfaces, which will help the AI to understand the context better and generate the correct tool calls.
  155. 3. Use newer high-end models as they are better at understanding the context and generating the correct tool calls.
  156. 4. Copy the MCP instructions prompt and paste it in the AI chat system prompt (Google AI Studio).
  157. 5. Mention the specific tools you want to use in your conversation.
  158. 6. Use the MCP Auto toggles to control the tool execution.
  159. ## Common Issues with MCP SuperAssistant
  160. This page covers the most common issues users encounter with MCP SuperAssistant and provides solutions to resolve them.
  161. ### 1. Extension Not Detecting Tool Calls
  162. - Make sure the extension is enabled in your browser.
  163. - Make sure the **mcp prompt instructions are properly attached or inserted** in the chat, before starting any chat.
  164. - Check that your AI platform supports tool calls and that the feature is enabled.
  165. - Refresh the page or restart your browser if the issue persists.
  166. ### 2. Tool Execution Fails
  167. - Ensure your proxy server is running and the URL is correct in the sidebar server settings.
  168. - check your config.json file for any errors or formatting issues.
  169. - Check your network connectivity and firewall settings.
  170. ### 3. Connection Issues
  171. - Ensure that your MCP server is running and accessible.
  172. - Check the server URL in the extension settings.
  173. - First start the npx mcp-SuperAssistant-proxy server and then reload/restart the extension from chrome://extensions/ page.
  174. - Check the proxy server logs for any errors or issues.
  175. - Ensure that your firewall or antivirus software is not blocking the connection.
  176. - Make sure the server shows the proper connected status and exposes the `/sse` endpoint.
  177. ### 4. Incorrect tool call format
  178. - There are times model does not generate correct tool call format as requested, this makes the tool detection to fail.
  179. In such cases, use better models which are meant for tool calling or have better tool calling capabilities.
  180. - Use the custom instructions prompt, which can be found in the MCP SuperAssistant sidebar.
  181. - Ask explicitily to use the tools by mentioning them in the prompt.
  182. - This Below is an example of correct MCP function call format, which is rendered by MCP SuperAssistant extension:
  183. ```
  184. ```jsonl
  185. {"type": "function_call_start", "name": "function_name", "call_id": 1}
  186. {"type": "description", "text": "Short 1 line of what this function does"}
  187. {"type": "parameter", "key": "parameter_1", "value": "value_1"}
  188. {"type": "parameter", "key": "parameter_2", "value": "value_2"}
  189. {"type": "function_call_end", "call_id": 1}
  190. ```
  191. ```
  192. ### Manual Installation (Development)
  193. #### Release Version
  194. 1. Download the latest release from [Releases](https://github.com/srbhptl39/MCP-SuperAssistant/releases)
  195. 2. Unzip the downloaded file
  196. 3. Navigate to `chrome://extensions/` in Chrome
  197. 4. Enable "Developer mode"
  198. 5. Click "Load unpacked" and select the unzipped directory
  199. 6. Follow [Connecting to Local Proxy Server](#connecting-to-local-proxy-server) to connect to your MCP server
  200. ## Development
  201. ### Prerequisites
  202. - Node.js 22.12+
  203. - pnpm 9.15.1 (`corepack enable`)
  204. ### Setup
  205. ```bash
  206. # Install dependencies
  207. pnpm install
  208. # Start development server
  209. pnpm dev
  210. # Build for production
  211. pnpm build
  212. # Create zip package for distribution
  213. pnpm zip
  214. # Firefox build and package
  215. pnpm build:firefox
  216. pnpm zip:firefox
  217. ```
  218. Settings (MCP server, browser access, page capture and usage statistics) live on the extension's options page.
  219. Usage statistics are sent only when `CEB_POSTHOG_KEY` (PostHog) and/or `CEB_GA_MEASUREMENT_ID` + `CEB_GA_API_SECRET` (Google Analytics 4) are set in `.env`, so local builds and forks send nothing by default. Unpacked installs also stay silent unless you run `chrome.storage.local.set({ telemetryDebug: true })` in the service worker console.
  220. ## Privacy
  221. **Usage statistics.** MCP SuperAssistant sends anonymous usage statistics to PostHog (EU region) and/or Google Analytics 4, depending on the release. Each install has a random id that is not linked to you, your accounts or your device. We send: the extension version, browser and operating system; which supported AI site was used; daily counts of feature use (tool runs, auto-execute, browser tools, tab attach, page capture, input chips, sidebar); whether the local MCP proxy connected; and coded error types. We never send chat content, page content, URLs, page titles, tool names, tool arguments or results. PostHog events are sent with IP-based geolocation disabled. You can turn this off in the extension's options under "Usage statistics". Firefox users can also turn it off under Permissions and data in about:addons.
  222. **Remote configuration.** The extension fetches feature flags and notices from Firebase Remote Config, which uses its own random installation id to do so.
  223. ## Contributing
  224. Contributions are welcome! Please feel free to submit a Pull Request.
  225. 1. Fork the repository
  226. 2. Create your feature branch (`git checkout -b feature/amazing-feature`)
  227. 3. Commit your changes (`git commit -m 'Add some amazing feature'`)
  228. 4. Push to the branch (`git push origin feature/amazing-feature`)
  229. 5. Open a Pull Request
  230. ## Author
  231. ### [Saurabh Patel](https://github.com/srbhptl39)
  232. ## Sponsor & Support
  233. This project is developed entirely in my spare time, driven by a passion for AI and the Model Context Protocol (MCP). As a full-time professional, balancing work commitments with open-source development makes it challenging to contribute regularly and maintain the pace of updates.
  234. Your support helps me dedicate more time to:
  235. - 🐛 Fixing bugs and addressing issues
  236. - ✨ Adding new features and platform support
  237. - 📚 Improving documentation and tutorials
  238. - 🔄 Keeping dependencies up-to-date
  239. - 💬 Responding to community requests
  240. **Support this project:**
  241. - ⭐ Star the repository to show your appreciation
  242. - 💖 [Sponsor on GitHub](https://github.com/sponsors/srbhptl39) to help sustain development
  243. - 🐦 Follow me on [Twitter](https://twitter.com/srbhptl39) (@srbhptl39) for updates
  244. - 📧 For private support or custom implementations, reach out via [Twitter](https://twitter.com/srbhptl39)
  245. Every contribution, big or small, helps keep this project alive and thriving! 🙏
  246. ## License
  247. This project is licensed under the MIT License - see the LICENSE file for details.
  248. ## Acknowledgments
  249. - Inspired by the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) by Anthropic
  250. - Thanks to [Cline](https://github.com/cline/cline) for idea inspiration
  251. - Built with [Chrome Extension Boilerplate with React + Vite](https://github.com/Jonghakseo/chrome-extension-boilerplate-react-vite)
  252. ## Star History
  253. [![Star History Chart](https://api.star-history.com/svg?repos=srbhptl39/MCP-SuperAssistant&type=Date)](https://www.star-history.com/#srbhptl39/MCP-SuperAssistant&Date)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.