Skip to main content

    Filter by idea status

    Filter by product

    1220 Ideas

    samujala
    samujalaEmployee

    MCP Workspace7.0 Duplicate

    Connect Any MCP Server to Your Moveworks AI Assistant!Release Type: Net New capabilitySummary: If a system has an MCP server, you will be able to connect it to your Moveworks AI Assistant -- no custom integration work of plugin development required). Point it at your endpoint, configure auth, and your assistant can start calling its tools. For many of the apps you're already using like Linear, Notion, Slack, we're shipping preconfigured servers so setup takes seconds and your employees will be able lookup data and take actions immediately. For example: "Create a Linear issue and link it to this Notion doc" "Find all unread Slack threads where I'm mentioned and summarize them" "Draft a Notion page from my meeting notes and assign follow-ups in Linear"What problem does this solve? Every new tool integration used to require a custom build. MCP eliminates that — if a system has an MCP server, your assistant can call its tools with just an endpoint and auth config.How does it work?Navigate to MCP Workspace in Agent Studio Select a preconfigured server or add a custom one via endpoint URL + auth Your assistant discovers available tools automatically Users can immediately invoke those tools in conversationKnown Limitations: TBDDocsite Link: TBDMedia: TBDAdditional Detail:Preconfigured servers on launch will be:• Asana• Atlassian• Linear• Intercom• Monday• Notion• Sentry• ZapierYou can connect any MCP server (including Snowflake, Slack and ServiceNow), not just those on the pre-configured server list. The "pre-configured" apps above just support Dynamic Client Registration (DCR) which automates the setup.

    dhorvathCommunity Manager

    MCP Workspace5. Controlled Availability

    Connect Any MCP Server to Your Moveworks AI Assistant!Only selected customers will have access during Controlled AvailabilityRelease Type: Net New capabilitySummary: If a system has an MCP server, you will be able to connect it to your Moveworks AI Assistant -- no custom integration work of plugin development required). Point it at your endpoint, configure auth, and your assistant can start calling its tools. For many of the apps you're already using like Linear, Notion, Slack, we're shipping preconfigured servers so setup takes seconds and your employees will be able lookup data and take actions immediately. For example: "Create a Linear issue and link it to this Notion doc" "Find all unread Slack threads where I'm mentioned and summarize them" "Draft a Notion page from my meeting notes and assign follow-ups in Linear"What problem does this solve? Every new tool integration used to require a custom build. MCP eliminates that — if a system has an MCP server, your assistant can call its tools with just an endpoint and auth config.How does it work?Navigate to MCP Workspace in Agent Studio Select a preconfigured server or add a custom one via endpoint URL + auth Your assistant discovers available tools automatically Users can immediately invoke those tools in conversationKnown Limitations: https://docs.moveworks.com/agent-studio/mcp-workspace/limitations-and-troubleshootingDocsite Link: https://docs.moveworks.com/agent-studio/mcp-workspace/overviewMedia: TBDAdditional Detail:Preconfigured servers on launch will be:• Asana• Atlassian• Linear• Intercom• Monday• Notion• Sentry• ZapierYou can connect any MCP server (including Snowflake, Slack and ServiceNow), not just those on the pre-configured server list. The "pre-configured" apps above just support Dynamic Client Registration (DCR) which automates the setup.

    Bartosz FijolNew Participant

    AI Powered Context Chat Handover1. New

    Current experienceWhen a user requests a chat with a live agent through the AI conversational layer, Moveworks transfers the last ~20 chatbot messages to the chat-handling platform (Salesforce in this case) and asks the user to provide a chat description. However, the transferred conversation may be outdated, unrelated to the current issue, and often lengthy without any summarization. This can create confusion for advisors, who must spend time determining whether the chat history is relevant and if it aligns with the user's description.Proposed enhancementBefore transferring a chat, use AI to assess the recency and relevance of previous conversations.If a related conversation is detected, provide a concise AI-generated summary of the issue and key discussion points instead of the raw transcript. Ideally, if sufficient context is available, the user should not be required to enter a separate description. If the previous conversation is not relevant (e.g., a different topic or several months old), do not transfer it as context. If no relevant conversation history exists, prompt the user to provide description as the primary context for the advisor.BenefitsFaster advisor ramp-up and reduced handling time Elimination of misleading or outdated context Better alignment between transferred context and the employee's current issue Improved employee and advisor experience More intelligent and seamless AI-to-human handovers