GitHub Copilot
Supported in the current product flow.
Use MoodLens as a connected workspace tool source inside Copilot-driven workflows.
The MoodLens MCP server turns assistant clients into workspace-aware operators. Instead of working in isolation, Copilot, VS Code, Cursor, Windsurf, Claude, and future ChatGPT flows can work with real tasks, docs, boards, meetings, and workspace context inside MoodLens.
Supported in the current product flow.
Use MoodLens as a connected workspace tool source inside Copilot-driven workflows.
Supported host environment.
Pair the MCP server with VS Code setups where workspace-aware assistance belongs close to code and docs.
Supported in the current product flow.
Bring MoodLens tasks, docs, meetings, boards, and workspace context into Cursor-based sessions.
Supported in the current product flow.
Let Windsurf work with your workspace context instead of acting like an isolated coding assistant.
Supported in the current product flow.
Connect Claude Desktop so it can search, create, update, and organize work directly in MoodLens.
Marked coming soon in the current product notes.
The current product notes say ChatGPT Desktop still supports only remote MCP servers, so this local setup remains a future lane.
Connected assistant clients can read the context that already lives in MoodLens, including tasks, documents, boards, sprints, meetings, integrations, and team structures.
The MCP tool surface is not read-only. It can create, update, archive, comment, and move work so the LLM can do more than summarize.
The setup flow creates a dedicated API key with the right scopes, and many tools accept workspaceId so people can target the correct workspace explicitly.
Install Node.js before starting the MCP setup flow.
Run the MoodLens MCP installer and choose the assistant client you want to configure.
Let the installer generate the dedicated API key and write the client config automatically.
Restart the target assistant app so it reloads the new MCP server connection.
The MCP server exposes MoodLens as an actionable workspace layer instead of a plain chat integration. That means connected clients can work across: