Thinking Frameworks
Product, engineering, risk, strategy, and agent workflow operating cards.
AI Workflow MCP includes a framework corpus for routing ambiguous operational decisions into explicit operating cards.
Default Behavior
Framework search and routing prefer published cards. Candidate cards are available only when explicitly requested with include_candidates=true.
Endpoints
curl -fsS "https://api.aiworkflowmcp.com/v1/frameworks/search?q=riskiest%20assumption%20test&limit=3"
curl -fsS "https://api.aiworkflowmcp.com/v1/frameworks/route?q=preflight%20risky%20launch%20decision"MCP Tools
search_frameworks: find framework cards by query and optional domain.route_framework: choose the best operating framework for a task.get_framework: retrieve a framework card by id.
REST Parameters
include_candidates=true includes candidate cards that are still below the published threshold. Leave it false for production user-facing answers.
include_prompt=true includes the full prompt contract where available. Use it only when the agent needs to execute the framework, not for lightweight routing.
domain narrows routing when the user intent is clear. Leave it blank when the task is ambiguous and the router should compare across product, engineering, risk, strategy, and agent workflow cards.
Quality Rule
Framework routing should use general ranking, source metadata, and framework fields. Do not hard-code individual query phrases to specific framework names.