model-context-protocol · productivity · 0 triggers · 200 actions
Operate an Ambiguous workspace through its provider-hosted MCP server, including documents, spreadsheets, tasks, CRM, calendar, mail, chat, and administration. Uses the connected account’s workspace-scoped API key. Some tools send external messages, delete data, change access, or consume the workspace action allowance. Add Ambiguous MCP to your Stream Deck workflows with guided setup for the connection details it needs.
Add Ambiguous MCP to a workflow and pair it with a Stream Deck button to run it in one press — handy for model-context-protocol tasks. Combine it with OBS, your Elgato tools, or any other app you connect to build a routine that fits how you work.
Browse all templatesSteps your workflow can perform in Ambiguous MCP.
Acknowledge the Mentions & reactions inbox after it has been displayed. Marks the caller's unread chat mention notifications read and stamps users.mentions_acked_at, so the projector recomputes both chat.mentions and chat.reactions to 0 durably (the sidebar "Mentions & reactions" item un-bolds and stays cleared across re-fetch). Per-channel read cursors are untouched, so channel message unread counts are unaffected; a reaction that arrives after the ack re-bolds the item.
Acknowledge readable Threads inbox activity on entry without advancing personal read cursors or clearing explicit manual unread intent.
Add a conditional formatting rule to a spreadsheet. Provide one of booleanRule, gradientRule, iconSetRule, or dataBarRule. The server generates a unique ID for the rule.
Extend a flow: place a new node beside an existing element and connect them in one call — the server computes the position unless you pass drop_point. Use this instead of create_canvas_element + a manual connector when building a flowchart, product map, or swimlane step-by-step. Give source_element_id and a direction (n/s/e/w); the new node lands one standard gap on that side and is nudged clear of any overlap, and a connector is created pre-attached from the source to it. For a drag-to-empty gesture, supply optional drop_point: { x, y } to center the new node at that board-space point instead of automatic placement. Provide element for the new node's type (connector/frame/swimlane not allowed here), or omit it to duplicate the source. Coordinates: board units, top-left origin, +x right / +y down. Example: add_connected_element({ id: "<boardId>", source_element_id: "<elId>", direction: "e", element: { type: "shape", shape: "diamond" } }) → { element, connector }.
Add a line item to a deal. Either reference an existing product (via product_id) or create a custom line by providing name and unit_price. The deal amount is auto-recalculated.
Add a forwarding address (sends verification email).
Add (or update the role of) a user or team on a CRM pipeline. Provide either user_id or team_id, plus role (admin | member). Admins/owners and pipeline admins can manage members.
Add a member (manager-only).
Operate an Ambiguous workspace through its provider-hosted MCP server, including documents, spreadsheets, tasks, CRM, calendar, mail, chat, and administration. Uses the connected account’s workspace-scoped API key. Some tools send external messages, delete data, change access, or consume the workspace action allowance.
Create your Conductor Deck account: no credit card required.
Follow the setup prompts for Ambiguous MCP. Conductor Deck handles the app authorization or required connection details inside the workflow builder.
Add an Ambiguous MCP action to your visual workflow canvas. Configure the options you need, then connect it to other steps.
Sync your workflow to any Stream Deck button. Press once to trigger the entire sequence.
Sign up for free and start building Ambiguous MCP workflows in minutes.