Integrations
Connect Losi With Integrations, API, and MCP
Use Integrations, the Losi Spaces API, and authenticated MCP access to connect Losi with other tools where enabled.
Review connected tools in the dashboard.
Losi includes a private dashboard Integrations area and public Spaces API documentation. The MCP server is implemented as an authenticated API endpoint for external clients that can list and call Losi Spaces tools.
Because API and MCP access can depend on workspace settings, credentials, and rollout state, treat this guide as a starting map. Use the in-product Integrations area and API docs for the source of truth before building an automation.
Use Integrations first
Open the Integrations area in the dashboard when you want Losi to work with other apps. Connect only the tools you trust, and check each integration for the actions it supports.
Use the Losi Spaces API for structured work
The public Spaces API docs cover common developer actions such as listing Spaces, creating Spaces, creating tasks, listing tasks, and creating notes. That makes it useful when another system needs to create or update structured work in Losi.
Developer API usage requires valid Losi API credentials and the permissions for the workspace or Space being updated.
Use MCP for external LLM clients where configured
The MCP endpoint is authenticated with Losi API keys or OAuth tokens and exposes Losi Spaces tools through MCP tools/list and tools/call. Use it for developer workflows where an external client needs controlled access to Spaces actions.
The older Nexus MCP dashboard page contains mock data, so this article describes the implemented API endpoint rather than promising that mock UI as a production feature.
Screenshots to add
These are intentional placeholders for real product captures.
Screenshot placeholder: Integrations page
Show the private dashboard Integrations directory with real connected-tool state.
Screenshot placeholder: Connected app or tool
Show a connected integration with non-sensitive credentials hidden.
Screenshot placeholder: API or MCP docs area
Show the public Spaces API docs or an authenticated MCP setup screen if available.
Screenshot placeholder: Space updated from external tool
Show a real task or note created in a Space from an external system.