INDIVIDUAL MCP TOOL

preflight_recurring_workflow

Start here when a user describes recurring operational friction in plain language.

quietstance.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://quietstance.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for preflight_recurring_workflow and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

quietstance.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.quiet-stance-workflow-assays-and-bottleneck-diag]
url = "https://quietstance.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "quiet-stance-workflow-assays-and-bottleneck-diag": {
      "type": "http",
      "url": "https://quietstance.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: quiet-stance-workflow-assays-and-bottleneck-diag
Remote MCP URL: https://quietstance.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "quiet-stance-workflow-assays-and-bottleneck-diag": {
      "url": "https://quietstance.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "quiet-stance-workflow-assays-and-bottleneck-diag": {
      "type": "http",
      "url": "https://quietstance.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "quiet-stance-workflow-assays-and-bottleneck-diag",
  "transport": "streamable-http",
  "url": "https://quietstance.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

get_workflow_assays — Use when an agent already has a user's operational problem and wants a pre-shaped test instead of starting from a blank page.
preview_reference_workflow_assay — Use to evaluate how Quiet Stance works without supplying customer data.
get_workflow_assessment_guidance — Use when a user describes a recurring workflow bottleneck: manual handoffs, repeated rework, waiting or approval delay, exception chasing, copying data between systems, unclear ownership, or uncertainty about whether automation or AI is justified.
diagnose_workflow_bottleneck — Use for evidence-first manual process analysis of a specific recurring workflow before automation or AI: handoffs, approval delays, ownership stalls, rework, duplicate entry, exceptions or evidence gaps.
submit_workflow_inquiry — Submit a sanitized inquiry only after the user has explicitly authorized sending it to Quiet Stance.