mcp and custom models

Author: CamDavidsonPilon

developer-guide/11-custom_models.md

@@ -0,0 +1,27 @@
+---
+title: Custom bioreactor models
+slug: /custom-bioreactor-models
+---
+
+:::tip
+This feature is actively under development - let us know what else you would like to see!
+:::
+
+If you are building a novel bioreactor on top of our software, you can use the `~/.pioreactor/models` dir to add your own bioreactors. For example, add the following to `custom_100ml.yaml` in `~/.pioreactor/models`:
+
+```yaml
+model_name: custom_100ml
+model_version: "1.0"
+display_name: "Custom 100 mL, v1.0"
+reactor_capacity_ml: 100.0
+reactor_max_fill_volume_ml: 95.0
+reactor_diameter_mm: 50.0
+max_temp_to_reduce_heating: 80.0
+max_temp_to_disable_heating: 85.0
+max_temp_to_shutdown: 90.0
+```
+
+The UI's Inventory page should now show a this option in the model-selection dropdowns. 
+
+These values can be accessed throughout our software via `pioreactor.whoami.get_pioreactor_model()`.
+

user-guide/30-Advanced/10-MCP.md

@@ -0,0 +1,26 @@
+---
+title: MCP and AI integrations
+slug: /mcp
+---
+
+:::danger
+
+Heads up! Giving AI agents control of your bioreactor is a big risk!
+
+:::
+
+The Pioreactor has the ability to allow authorized AI agents to control your cluster. This is possible because the Pioreactor has an MCP server running on it. The MCP server tells the AI agent what tools are available (running jobs, updating jobs, finding data, etc), and the the Agent uses those tools to help it accomplish their goals.
+
+The MCP server's SSE endpoint url is
+
+  ```
+  http://<leader-address>/mcp/
+  ```
+
+If running the Agent locally, you may need to use a tool like mcp-proxy to bridge between HTTP and STDIO.
+
+:::tip
+
+This is very new! Let us know if you have any questions, ideas, or issues!
+
+:::