Plugins

Extend pREST with OS shared libraries (.so) for custom middleware and endpoints. Plugins load beside the built-in REST and MCP surfaces — they do not replace them.

Here is a discussion of how we arrived at this architecture.

Write a shared library and configure pREST to load it at server start. pREST uses the Go plugin system; on platforms where Go plugins are unavailable (notably Windows), plugin endpoints will not load.

Set the library directory with PREST_PLUGINPATH (default ./lib) or TOML:

pluginpath = "./lib"

Extension-supported modules

• Endpoint

• Middleware

Process of building

The first plugin builder targets Go source under ./lib. The runtime can still load .so libraries produced by other toolchains; the automatic Go constructor is the documented path today.

Related

• Configuring pREST

• API Reference

• MCP over HTTP

• Acronyms · REST · MCP