AI Business System Advisor

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Find the safest first AI workflow before investing in AI agents or automation.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "AI Business System Advisor": {
      "url": "https://mcp.prodxsolution.com/ai-business-system-advisor/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (9)

• analyze_business_context read-only

  Summarizes the supplied business context, including customer, offer, workflow, goals, constraints, readiness signals, missing information, and confidence.

  Parameters:

  • notes — string — Any additional context the user wants considered in the review.
  • offer — string — Core product, service, package, or outcome the business sells.
  • aiIdea — string — AI or automation idea the user is considering.
  • teamSize — string — Approximate team size and key roles involved in the workflow.
  • goal90Days — string — Desired business or workflow outcome over the next 90 days.
  • constraints — array — Known constraints such as budget, team capacity, tools, timeline, compliance needs, or data access.
  • currentGoal — string — Current business goal the user wants the review to support.
  • businessType — string — Type of business, such as ecommerce, SaaS, consulting, agency, local service, or solo business.
  • revenueModel — string — How the business earns revenue, such as projects, retainers, subscriptions, services, or products.
  • riskConcerns — string — Concerns related to customer trust, brand reputation, legal exposure, sensitive data, or quality control.
  • currentProblem — string — Main business or workflow problem the user wants to solve.
  • targetCustomer — string — Primary customer segment or buyer the business serves.
  • currentWorkflow — string — How the relevant workflow currently works, including manual steps, tools, handoffs, and review points.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• map_customer_touchpoints read-only

  Maps customer-facing workflow stages, trust-sensitive moments, automation-safe areas, human-critical areas, missing information, and confidence.

  Parameters:

  • aiIdea — string — AI or automation idea that may affect customer touchpoints.
  • touchpoints — array — Specific customer-facing moments, handoffs, or interactions to review.
  • businessType — string — Type of business being reviewed.
  • riskConcerns — string — Concerns about trust, customer experience, brand reputation, privacy, or quality control.
  • salesProcess — string — How leads are qualified, sold, and converted before delivery begins.
  • currentProblem — string — Main customer journey or workflow problem the user wants to solve.
  • supportProcess — string — How customer questions, issues, tickets, or requests are handled.
  • currentWorkflow — string — Current workflow steps, tools, owners, and handoffs.
  • customerJourney — array — Known customer journey stages from first contact through retention.
  • deliveryProcess — string — How the business delivers the offer or service after onboarding.
  • recoveryProcess — string — How complaints, refunds, exceptions, or service recovery are handled.
  • retentionProcess — string — How renewals, repeat purchases, referrals, or ongoing customer value are managed.
  • onboardingProcess — string — How new customers are welcomed, scoped, educated, or set up.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• identify_bottlenecks read-only

  Identifies likely revenue, operations, customer experience, and trust/control bottlenecks from the supplied business context and returns a public-safe summary.

  Parameters:

  • aiIdea — string — Optional AI or automation idea the user is considering.
  • metrics — string — Known metrics such as response time, conversion, close rate, cycle time, churn, cost, or error rate.
  • businessType — string — Type of business being reviewed.
  • riskConcerns — string — Concerns about customer trust, brand risk, money, privacy, compliance, or quality control.
  • currentProblem — string — Main problem or bottleneck the user suspects.
  • teamPainPoints — string — Internal pain points such as repetitive work, slow handoffs, rework, or unclear ownership.
  • businessContext — string — Short description of the business model, customers, offer, team, and operating context.
  • currentWorkflow — string — Current workflow steps, handoffs, tools, and review points.
  • customerComplaints — string — Known customer complaints, friction points, refunds, or support issues.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• evaluate_ai_opportunities read-only

  Evaluates candidate AI workflow ideas for business value, implementation readiness, repeatability, trust/control risk, warnings, and missing information.

  Parameters:

  • aiIdea — string — Specific AI or automation idea the user wants evaluated.
  • businessType — string — Type of business being reviewed.
  • riskConcerns — string — Concerns about customer trust, brand risk, money, privacy, compliance, or quality control.
  • currentProblem — string — Main problem the AI opportunities should help solve.
  • businessContext — string — Short description of the business, customers, offer, and current operating context.
  • currentWorkflow — string — Current workflow before AI or automation.
  • candidateUseCases — array — Candidate AI workflow ideas to evaluate.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• assess_trust_control_risks read-only

  Reviews a proposed AI workflow for human review needs, data boundaries, quality controls, escalation triggers, unsafe automation risks, and confidence.

  Parameters:

  • aiIdea — string — Specific AI or automation idea the user is considering.
  • businessType — string — Type of business being reviewed.
  • riskConcerns — string — Known concerns about customer trust, brand risk, compliance, money, privacy, or quality control.
  • workflowIdea — string — AI workflow or agent idea to assess for trust and control risk.
  • canAffectMoney — boolean — Whether the workflow can influence pricing, refunds, payments, scope, or financial decisions.
  • currentProblem — string — Main business or workflow problem the user wants to solve.
  • customerFacing — boolean — Whether the workflow directly affects customers or customer-facing messages.
  • currentControls — string — Existing review, approval, QA, escalation, or monitoring controls.
  • currentWorkflow — string — Current workflow before AI or automation.
  • proposedWorkflow — string — Proposed workflow design, including what AI would do and what humans would review.
  • usesSensitiveData — boolean — Whether the workflow may use private, regulated, or sensitive business/customer data.
  • canAffectBrandTrust — boolean — Whether the workflow can affect brand reputation, customer expectations, or public trust.
  • requiresExpertJudgment — boolean — Whether the workflow needs professional, strategic, legal, financial, HR, or domain judgment.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• recommend_first_workflow read-only

  Recommends the safest narrow AI-human workflow to implement first, including roles, review rules, escalation rules, success metrics, and missing information.

  Parameters:

  • notes — string — Any additional context the user wants considered in the review.
  • offer — string — Core product, service, package, or outcome the business sells.
  • risks — array — Known risks or control concerns that should shape the workflow design.
  • aiIdea — string — AI or automation idea the user is considering.
  • teamSize — string — Approximate team size and key roles involved in the workflow.
  • goal90Days — string — Desired business or workflow outcome over the next 90 days.
  • bottlenecks — array — Known or suspected bottlenecks the first workflow should address.
  • constraints — array — Known constraints such as budget, team capacity, tools, timeline, compliance needs, or data access.
  • currentGoal — string — Current business goal the user wants the review to support.
  • businessType — string — Type of business, such as ecommerce, SaaS, consulting, agency, local service, or solo business.
  • revenueModel — string — How the business earns revenue, such as projects, retainers, subscriptions, services, or products.
  • riskConcerns — string — Concerns related to customer trust, brand reputation, legal exposure, sensitive data, or quality control.
  • opportunities — array — AI opportunities already identified or under consideration.
  • currentProblem — string — Main business or workflow problem the user wants to solve.
  • targetCustomer — string — Primary customer segment or buyer the business serves.
  • currentWorkflow — string — How the relevant workflow currently works, including manual steps, tools, handoffs, and review points.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• generate_mini_report read-only

  Generates a public-safe mini business system review with snapshot, bottlenecks, opportunities, risks, first workflow, next step, missing information, and confidence.

  Parameters:

  • notes — string — Any additional context the user wants considered in the review.
  • offer — string — Core product, service, package, or outcome the business sells.
  • risks — array — Known trust, control, customer, or implementation risks to include.
  • aiIdea — string — AI or automation idea the user is considering.
  • nextStep — string — Existing next-step recommendation to include or refine.
  • teamSize — string — Approximate team size and key roles involved in the workflow.
  • confidence — string — Optional confidence level to carry into the report.
  • goal90Days — string — Desired business or workflow outcome over the next 90 days.
  • bottlenecks — array — Known bottlenecks to include in the mini review.
  • constraints — array — Known constraints such as budget, team capacity, tools, timeline, compliance needs, or data access.
  • currentGoal — string — Current business goal the user wants the review to support.
  • businessType — string — Type of business, such as ecommerce, SaaS, consulting, agency, local service, or solo business.
  • revenueModel — string — How the business earns revenue, such as projects, retainers, subscriptions, services, or products.
  • riskConcerns — string — Concerns related to customer trust, brand reputation, legal exposure, sensitive data, or quality control.
  • opportunities — array — Known AI opportunities to include in the mini review.
  • currentProblem — string — Main business or workflow problem the user wants to solve.
  • targetCustomer — string — Primary customer segment or buyer the business serves.
  • currentWorkflow — string — How the relevant workflow currently works, including manual steps, tools, handoffs, and review points.
  • businessSnapshot — string — Existing business snapshot to include or refine in the mini review.
  • preferredNextStep — string — User preference for self-guided, diagnostic, documentation, build, or review support.
  • recommendedWorkflow — string — Existing first workflow recommendation to include or refine.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• recommend_next_step read-only

  Recommends a practical next-step category based on business goal, workflow complexity, implementation readiness, risk level, preferences, and missing information.

  Parameters:

  • notes — string — Any additional context the user wants considered in the review.
  • offer — string — Core product, service, package, or outcome the business sells.
  • aiIdea — string — AI or automation idea the user is considering.
  • teamSize — string — Approximate team size and key roles involved in the workflow.
  • timeline — string — Desired timeline for review, documentation, pilot, or implementation.
  • userGoal — string — Goal the user wants the next step to support.
  • readiness — string — Simplified readiness level if already known.
  • riskLevel — string — Estimated risk level or uncertainty for the workflow.
  • goal90Days — string — Desired business or workflow outcome over the next 90 days.
  • preference — string — User's preferred support style.
  • constraints — array — Known constraints such as budget, team capacity, tools, timeline, compliance needs, or data access.
  • currentGoal — string — Current business goal the user wants the review to support.
  • businessType — string — Type of business, such as ecommerce, SaaS, consulting, agency, local service, or solo business.
  • revenueModel — string — How the business earns revenue, such as projects, retainers, subscriptions, services, or products.
  • riskConcerns — string — Concerns related to customer trust, brand reputation, legal exposure, sensitive data, or quality control.
  • currentProblem — string — Main business or workflow problem the user wants to solve.
  • targetCustomer — string — Primary customer segment or buyer the business serves.
  • currentWorkflow — string — How the relevant workflow currently works, including manual steps, tools, handoffs, and review points.
  • wantsDoneForYou — boolean — Whether the user prefers implementation support rather than self-guided work.
  • wantsSelfGuided — boolean — Whether the user prefers self-guided resources or templates.
  • problemComplexity — string — Estimated complexity of the business or workflow problem.
  • hasExistingAutomation — boolean — Whether the business already has automation or AI workflows in place.
  • implementationReadiness — string — How ready the business appears for implementation.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• export_intake_packet read-only

  Creates a structured public-safe markdown and JSON intake packet with business context, findings, risks, recommended workflow, missing information, and confidence.

  Parameters:

  • notes — string — Any additional context the user wants considered in the review.
  • offer — string — Core product, service, package, or outcome the business sells.
  • aiIdea — string — AI or automation idea the user is considering.
  • teamSize — string — Approximate team size and key roles involved in the workflow.
  • userNotes — string — Additional notes the user wants included in the intake packet.
  • goal90Days — string — Desired business or workflow outcome over the next 90 days.
  • constraints — array — Known constraints such as budget, team capacity, tools, timeline, compliance needs, or data access.
  • currentGoal — string — Current business goal the user wants the review to support.
  • riskSummary — object — Structured trust and control risk findings from a prior tool result.
  • businessType — string — Type of business, such as ecommerce, SaaS, consulting, agency, local service, or solo business.
  • revenueModel — string — How the business earns revenue, such as projects, retainers, subscriptions, services, or products.
  • riskConcerns — string — Concerns related to customer trust, brand reputation, legal exposure, sensitive data, or quality control.
  • touchpointMap — object — Structured customer touchpoint map from a prior tool result.
  • currentProblem — string — Main business or workflow problem the user wants to solve.
  • targetCustomer — string — Primary customer segment or buyer the business serves.
  • businessContext — object — Structured business context from a prior tool result or user notes.
  • currentWorkflow — string — How the relevant workflow currently works, including manual steps, tools, handoffs, and review points.
  • bottleneckSummary — object — Structured bottleneck findings from a prior tool result.
  • preferredNextStep — string — Preferred next-step category or support style to include in the packet.
  • opportunitySummary — object — Structured AI opportunity findings from a prior tool result.
  • recommendedNextStep — object — Structured next-step recommendation from a prior tool result.
  • recommendedWorkflow — object — Structured first workflow recommendation from a prior tool result.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.