vrr/SurfSense
2
0
Fork 0
mirror of https://github.com/MODSetter/SurfSense.git synced 2026-10-29 18:09:09 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
SurfSense/backend/plugins
History
Exact
github-actions[bot] a89f6e86b4 chore(registry): sign the plugin list
2026-10-24 09:32:16 +00:00
..
bundles refactor(backend): move plugins/ into backend/, run by server/ 2026-10-23 17:49:08 +02:00
host feat(backend): serve the license portal from backend/license/ 2026-10-23 17:49:08 +02:00
mcp_server refactor(backend): move plugins/ into backend/, run by server/ 2026-10-23 17:49:08 +02:00
proprietary refactor(backend): move plugins/ into backend/, run by server/ 2026-10-23 17:49:08 +02:00
registry chore(registry): sign the plugin list 2026-10-24 09:32:16 +00:00
README.md refactor(backend): move plugins/ into backend/, run by server/ 2026-10-23 17:49:08 +02:00

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
host/, mcp_server/, proprietary/ SurfSense's own plugins and the plugin host that runs them, in the one backend. Maintainers only for 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.