Agent Interfaces#

Choose how you reach the OSPREY agent besides the web terminal: from the command line, from an external event, or from a team chat room. It is the same agent on the same project each way. What differs is who or what starts a run, and how much of it a human sees while it happens. To give the agent new tools, see Add an MCP Server.

Run the Agent from the Command Line

osprey chat for an interactive session in your native terminal, and osprey query for a single headless prompt that exits with a meaningful code.

Run the Agent from the Command Line
Event Dispatch

Turn webhooks, cron ticks and EPICS channel crossings into headless agent runs: the dispatcher, the worker, the triggers you author, and the two bearer tokens that guard them.

Event Dispatch
Add an MCP Server

Give the agent new tools: declare an external server under mcp_servers: in your build profile, or – as a contribution to Osprey itself – write a framework server in Python.

Add an MCP Server
Chat Bridges

Let a team ask questions from Nextcloud Talk, Google Chat, Microsoft Teams or Slack and get the answer – plots and files included – back in the same conversation.

Chat Bridges