vrr/SurfSense
2
0
Fork 0
mirror of https://github.com/MODSetter/SurfSense.git synced 2026-10-22 06:10:57 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
SurfSense/plugins/README.md
Anish Sarkar 8ddefbc373 docs(plugins): a guide to listing a plugin, for publishers and agents 
plugins/registry/README.md explains that a plugin is an MCP server and walks
from getting the server ready to the pull request, with every field, how
Verified is proven, what review checks, and a checklist for coding agents.
plugins/README.md and CONTRIBUTING.md point to it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 14:00:02 +05:30

1 KiB
Raw Permalink Blame History

Plugins

A plugin is a remote MCP server that gives SurfSense's agent tools. Its publisher hosts the server; SurfSense lists it, asks the user before connecting, and calls it. Any MCP server that works in other MCP clients works here unchanged. How SurfSense handles plugins is in plugins.

Folder What it holds
registry/ The list of third-party plugins, their icons, the check every entry passes, and the container that serves them
remote/ SurfSense's own plugins and the plugin host that runs them. Maintainers only for remote/proprietary/
bundles/ Deferred. The earlier, local design's SDK and tooling, kept for plugins that run on the user's machine

Want to add your plugin? Read Add your plugin to SurfSense: what a plugin is, how to get your MCP server ready, try it in the app, and list it with one pull request. It is written for coding agents as well as people.