vrr/SurfSense
2
0
Fork 0
mirror of https://github.com/MODSetter/SurfSense.git synced 2026-10-21 13:52:01 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
SurfSense/plugins
History
Exact
Anish Sarkar 807045fabd docs(registry): simpler plugin submission form 
Say what servers the registry supports, drop the Inspector paragraph,
shorten the no-secrets box, and word the access choices as Free and Paid,
so a free account no longer reads as needing one sold by the publisher.
The intake's FREE and PAID match the new choices.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 16:36:12 +05:30
..
bundles refactor(plugins): move the bundle tooling under plugins/bundles 2026-10-10 20:19:47 +05:30
registry docs(registry): simpler plugin submission form 2026-10-21 16:36:12 +05:30
remote fix(plugins): review fixes before merge 2026-10-14 15:01:56 -07:00
README.md docs(plugins): a guide to listing a plugin, for publishers and agents 2026-10-14 14:00:02 +05:30

README.md

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.