Actions & MCP
Extend the capabilities of Nexus Agents
Availability depends on your school's enabled tools, provider setup, and account permissions. These settings are managed in the web workspace. A class policy may restrict a feature described here.
Overview#
Actions give Agents the ability to interact with external systems.
Nexus comes with 5 built-in Actions and allows users to configure additional ones via OpenAPI and Model Context Protocol (MCP).
The built-in Actions include:
| Name | Description | Requires Config | Provider Choices |
|---|---|---|---|
| Internal Search | Search through your school's indexed documents and knowledge base | Yes | Built-in with swappable components |
| Web Search | Search the internet for real-time information and current events | Yes | Google, Serper, Exa, Firecrawl (optional) |
| Code Execution | Execute Python code, analyze data, and generate visualizations | No | Built-in |
| Image Generation | Create images from text descriptions using AI models | Yes | OpenAI, Azure OpenAI |
| Coding Agent Beta | Investigate and answer questions about a public GitHub codebase | Yes (disabled by default) | Built-in |
Custom Actions#
Nexus offers flexible options for configuring both custom Actions and their associated authentication.
Admins can choose to:
Use a single shared authentication, giving all users the same level of access to Actions.
Require each user to complete their own authentication flow, so Actions respect individual user permissions.
Nexus supports both token-based authentication and OAuth.
Actions Button#
In the Chat input bar, Actions are grouped by the MCP server or OpenAPI schema they are registered with. Users have the flexibility to turn on/off the Actions that the Agent/LLM has access to on the fly.