Content Tools
dbenarrativepro.com
An MCP server that guides users through a DBE personal narrative interview, generates compliance-oriented narrative documents, and handles checkout and delivery of the finished package.
ENDPOINT 1
https://dbenarrativepro.com/api/mcp
MCP server metadata
- Name
- dbe-narrative-pro
- Version
- 1.0.0
DBE Narrative Pro writes 2025-IFR-compliant DBE (Disadvantaged Business Enterprise) personal narratives for 49 CFR Part 26 certification. Flow: 1) call get_intake_schema and interview the user one question at a time; 2) call generate_narrative for a free preview; 3) call start_checkout and give the user the payment link; 4) after they pay, call get_documents with the claim_token to deliver the finished Word documents. Never include race, sex, or ethnicity in any answer or narrative content — the October 2025 rule requires describing actions and impacts instead.
Known tools 4
get_intake_schemaGet the consultant-grade interview for writing a DBE personal narrative (49 CFR Part 26, October 2025 Interim Final Rule): the ordered questions, answer options, required fields, compliance guardrails, and the formData shape to pass to generate_narrative.
Inferred read-onlygenerate_narrativeGenerate the DBE personal narrative package from completed interview answers.
Inferred read-onlystart_checkoutCreate a secure Lemon Squeezy checkout link for a DBE Narrative Pro product: "narrative" ($79 complete package — requires submission_id from generate_narrative), "review" ($49 scorecard of an existing narrative — requires narrative_text), or "template" ($25 Word template).
Potential side effectsget_documentsRedeem a paid purchase and deliver the goods: for "narrative" purchases, download links for all 4 finished Word documents plus the full narrative text; for "review" purchases, the complete AI scorecard; for "template" purchases, the template download link.
Potential side effectsCONNECT 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.dbe-narrative-pro]
url = "https://dbenarrativepro.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dbe-narrative-pro": {
"type": "http",
"url": "https://dbenarrativepro.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dbe-narrative-pro
Remote MCP URL: https://dbenarrativepro.com/api/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": {
"dbe-narrative-pro": {
"url": "https://dbenarrativepro.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dbe-narrative-pro": {
"type": "http",
"url": "https://dbenarrativepro.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dbe-narrative-pro",
"transport": "streamable-http",
"url": "https://dbenarrativepro.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.