apunkt/plano
1
0
Fork 0
mirror of https://github.com/katanemo/plano.git synced 2026-06-17 15:25:17 +02:00
Code Issues Projects Releases Packages Wiki Activity

fix reference to filter type

Browse source
This commit is contained in:
Adil Hafeez 2025-12-23 16:22:03 -08:00
parent c3ace314ce
commit e3f7ae1cbe
No known key found for this signature in database
GPG key ID: 9B18EF7691369645
2 changed files with 6 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/source/concepts/filter_chain.rst
View file

@ -52,9 +52,10 @@ Filter Chain Programming Model (HTTP and MCP)
Filters are implemented as simple RESTful endpoints reachable via HTTP. If you want to use the `Model Context Protocol (MCP) <https://modelcontextprotocol.io/>`_, you can configure that as well, which makes it easy to write filters in any language. However, you can also write a filter as a plain HTTP service.
When defining a filter in Plano configuration, the following fields are optional:
* ``type``: Controls the filter runtime (defaults to ``mcp``). You can also set this to ``rest`` for plain HTTP filters.
* ``type``: Controls the filter runtime. Use ``mcp`` for Model Context Protocol filters, or ``http`` for plain HTTP filters. Defaults to ``mcp``.
* ``transport``: Controls how Plano talks to the filter (defaults to ``streamable-http`` for efficient streaming interactions over HTTP). You can omit this for standard HTTP transport.
* ``tool``: Names the MCP tool Plano will invoke (by default, the filter ``id``). You can omit this if the tool name matches your filter id.