Advanced Developer Guide

Stop treating requirements as text. Treat them as data. This guide covers how to use ProdMoh MCP to automate architecture decisions.

hub Under the Hood: Architecture

Unlike standard REST APIs where your IDE polls for data, ProdMoh MCP utilizes Server-Sent Events (SSE) for a persistent, unidirectional stream.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "resources/list",
  "params": {}
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "resources": [
      {
        "uri": "prodmoh://prd/102/checkout-flow",
        "name": "PRD: Checkout Flow V2",
        "mimeType": "text/markdown",
        "description": "Updated requirements for stripe integration"
      }
    ]
  }
}

settings Configuration

Add this configuration to your global or project-level settings file.

File Path: ~/.cursor/mcp.json or ~/.vscode/mcp.json

{
  "mcpServers": {
    "prodmoh": {
      "type": "sse",
      "url": "https://prodmoh.com/sse",
      "headers": {
        "x-prodmoh-token": "YOUR_TOKEN_HERE"
      }
    }
  }
}

smart_toy ChatGPT Custom GPT Integration

Connect ProdMoh to your Custom GPT in the ChatGPT GPT Store. This allows ChatGPT to access your PRDs, user stories, and product context during conversations.

https://prodmoh.com

Available Actions for ChatGPT

Once connected, your Custom GPT can:

• list_prds — Get all your PRDs
• list_userstories — Get all user stories
• get_prd_context — Read a specific PRD with full details
• get_userstory_context — Read a specific user story
• generate_coding_prompt — Generate AI coding prompts from requirements
• analyze_customer_feedback — Analyze feedback files (CSV, JSON, PDF)

directions_run Step-by-Step: Connect ProdMoh MCP to Your IDE

This guide walks you through installing, configuring, and verifying your MCP connection so your IDE can fetch PRDs, user stories, and acceptance criteria in real-time.

~/.cursor/mcp.json
# or
~/.vscode/mcp.json

{
  "mcpServers": {
    "prodmoh": {
      "type": "sse",
      "url": "https://prodmoh.com/sse",
      "headers": {
        "x-prodmoh-token": "YOUR_TOKEN_HERE"
      }
    }
  }
}

Connected to ProdMoh MCP (SSE)
Resources Loaded:  ✓ PRDs, ✓ User Stories, ✓ Research Docs

// Generate a Zod schema
@ProdMoh Read the Signup PRD. Build a Zod schema for POST /register.

// Generate a DB model
@ProdMoh Analyze "Data Requirements" section. Create a Prisma model for Order.

// Improve tests
@ProdMoh Audit my test file payment.test.ts using PRD 145.

storage Advanced: Generating DB Schemas

One of the highest-leverage uses of MCP is translating business data requirements directly into database models. This reduces the risk of field mismatch.

The Workflow

1. Ensure your PRD contains a section on "Data Requirements" or "User Attributes".

2. Use the following prompt pattern:

The Output (Example):

model User {
  id        String   @id @default(uuid())
  email     String   @unique // Derived from PRD Req #2.1
  role      Role     @default(USER)
  // PRD Req #2.4: "Users must have a bio, max 500 chars"
  bio       String?  @db.VarChar(500) 
  createdAt DateTime @default(now())
}

api Advanced: API Contracts

Prevent frontend-backend desync by generating Zod schemas or TypeScript interfaces directly from the acceptance criteria.

Prompt Engineering for Zod

The MCP server will retrieve the specific regex rules for passwords defined by your PM and enforce them in the generated code:

const RegisterSchema = z.object({
  email: z.string().email(),
  // Rules pulled from ProdMoh Doc #102
  password: z.string()
    .min(12, "Password must be 12 chars per Sec-Req-01")
    .regex(/[A-Z]/, "Must contain uppercase per Sec-Req-02"),
});

science Advanced TDD & Mocking

Moving beyond simple unit tests, ProdMoh MCP can orchestrate complex testing scenarios by understanding the intent behind your requirements.

1. The "QA Critic" Workflow

Before you commit, ask the MCP agent to audit your test suite against the PRD. It acts as an automated QA engineer.

Common catch: "You tested for successful payments, but the PRD Section 4.2 specifies that a '402 Payment Required' error must occur if the card balance is below $10. Your test suite misses this."

2. Generating Realistic Mock Data

Hardcoding test data is brittle. Use MCP to generate Mock Data Factories that strictly adhere to your data validation rules.

// Prompt: "@ProdMoh Generate a Faker.js factory for the 'Order' object based on PRD constraints."

export const createMockOrder = () => ({
  id: faker.string.uuid(),
  // PRD Req: "Order total cannot be negative"
  total: faker.number.float({ min: 0.01, max: 9999 }), 
  // PRD Req: "Status must be PENDING, SHIPPED, or DELIVERED"
  status: faker.helpers.arrayElement(['PENDING', 'SHIPPED', 'DELIVERED']),
  items: []
});

3. Integration Test Scenarios

For end-to-end (E2E) testing with tools like Playwright or Cypress, you can generate the entire user journey script.

security Security & Token Management

Your ProdMoh MCP token is a sensitive credential. It grants read access to your organization's internal product documentation. Treat it like an API Key.

Best Practices

• Do not commit to Git Your mcp.json is often in your global home directory (~/.cursor/), which is safe. If you use a project-level config (.vscode/mcp.json), ensure it is added to your .gitignore file immediately.
• Read-Only Architecture The MCP token currently provides Read-Only access. The AI agent in your IDE cannot modify, delete, or overwrite your official requirements documents.

Revoking Access

If a token is compromised or a developer leaves the team, you can secure your data instantly:

build Troubleshooting