Skip to content

Commit 1ac2105

Browse files
authored
FAQ (#27)
* Update FAQ section in MCPay component for clarity and expanded information - Revised questions and answers to better reflect the functionalities and benefits of MCPay. - Enhanced user guidance on consuming and monetizing MCPs, emphasizing ease of use and accessibility. - Improved overall structure and readability of the FAQ content for a better user experience. * Update FAQ section in FAQ component to enhance clarity and add new information - Corrected HTML entity for apostrophe in the answer about consuming paid MCPs for better rendering. - Added a new FAQ entry regarding the absence of an official $MCPAY token, providing users with important information and directing them to official channels for updates. * upgrade next to 15.4.8 * upgrade next in docs * Update FAQ section styles for improved readability and consistency - Changed link colors in the FAQ answers to enhance visibility and user experience. - Adjusted font weight in the FAQ question display for better emphasis and clarity.
1 parent 552ee4e commit 1ac2105

4 files changed

Lines changed: 197 additions & 169 deletions

File tree

apps/app/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@
4949
"lucide-react": "^0.525.0",
5050
"mcpay": "workspace:*",
5151
"motion": "^12.23.22",
52-
"next": "15.4.1",
52+
"next": "15.4.8",
5353
"next-themes": "^0.4.6",
5454
"pino-pretty": "^13.1.1",
5555
"prismjs": "^1.30.0",

apps/app/src/components/custom-ui/faq-section.tsx

Lines changed: 44 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -17,36 +17,64 @@ interface FAQItem {
1717

1818
const faqData: FAQItem[] = [
1919
{
20-
question: "What is MCPay?",
20+
question: "What is MCPay and who is it for?",
2121
answer: (
2222
<>
23-
MCPay is a <strong>payment layer for MCP servers and plain HTTP APIs</strong>. It uses <code>HTTP 402 Payment Required</code> with the <strong>x402</strong> flow so clients (apps/agents/browsers) can pay per call and automatically retry to get the result. <strong>No subscriptions, no OAuth, no manual API keys.</strong>
23+
MCPay is payment and access infrastructure for MCP servers. We offer solution for both ends:
24+
<div className="mt-3 space-y-2">
25+
<div><strong>A) People who want to use paid MCP tools:</strong> Sign up, find a server and start using paid tools across clients like ChatGPT. No crypto or technical setup required.</div>
26+
<div><strong>B) Developers who want to monetize MCP Servers or APIs:</strong> Use our open-source SDK or no-code UI to monetize your tools. Get access to a new range of developers and get ready for the agentic future.</div>
27+
</div>
2428
</>
2529
)
2630
},
2731
{
28-
question: "Do I have to use MCP?",
32+
question: "Why would I want to consume paid MCPs?",
2933
answer: (
3034
<>
31-
No. MCPay works great for <strong>plain HTTP</strong> endpoints. Using MCP adds niceties like <strong>tool discovery and pricing metadata</strong> for agent ecosystems.
35+
Instead of paying for expensive B2B/Enterprise subscriptions you can consume only the tools calls you want and pay cents per use.
3236
</>
3337
)
3438
},
3539
{
36-
question: "Who is MCPay for?",
40+
question: "How do I consume paid MCPs?",
3741
answer: (
38-
<div className="space-y-2">
39-
<div><strong>Providers</strong> (API/MCP owners) who want to <strong>price and monetize</strong> specific tools or routes.</div>
40-
<div><strong>Integrators/Agents</strong> who need <strong>programmatic, per-call payments</strong> without human sign-ups.</div>
41-
<div><strong>Builders</strong> who want the <strong>fastest path</strong> to ship paid MCP servers.</div>
42-
</div>
42+
<>
43+
Sign in, add funds to your account (no crypto needed), and <Link href="/servers" className="text-teal-700 dark:text-teal-200 hover:underline hover:decoration-dotted hover:underline-offset-2 transition-all duration-300">browse</Link> available MCP servers. You can run tools directly inside MCPay or connect them to clients like ChatGPT, where they&apos;ll execute automatically when needed.
44+
</>
45+
)
46+
},
47+
{
48+
question: "How much do I pay?",
49+
answer: (
50+
<>
51+
Each MCP tool sets its own price, typically a few cents (e.g., $0.05). We do not charge any fees on top of that.
52+
</>
53+
)
54+
},
55+
{
56+
question: "Why would I want to monetize MCPs?",
57+
answer: (
58+
<>
59+
If you manage an API that normally requires subscriptions or API keys, converting it to an MCP server gives you exposure to a growing new audience: individual developers, LLMs, agents, and MCP-compatible clients.
60+
</>
61+
)
62+
},
63+
{
64+
question: "How do I monetize my API or MCP Server?",
65+
answer: (
66+
<>
67+
Use our open-source SDK to add payments in a few lines of code.
68+
<br /><br />
69+
Or, if you prefer no-code, you can configure pricing directly through our UI.
70+
</>
4371
)
4472
},
4573
{
46-
question: "What's the MCPay Registry?",
74+
question: "Does this project have a token?",
4775
answer: (
4876
<>
49-
A machine-readable catalog of MCP servers and their priced tools (analytics, recent payments, integration snippets). Browse the Registry at <Link href="/servers" className="text-foreground hover:text-teal-600 underline decoration-dotted underline-offset-2 transition-all duration-300 font-semibold">Servers</Link>.
77+
There is no official $MCPAY token, be careful with impersonators. Trust only official announcement on <Link href="https://t.me/mcpay_tech" target="_blank" rel="noopener noreferrer" className="text-teal-700 dark:text-teal-200 hover:underline hover:decoration-dotted hover:underline-offset-2 transition-all duration-300">Telegram</Link> or <Link href="https://x.com/mcpaytech" target="_blank" rel="noopener noreferrer" className="text-teal-700 dark:text-teal-200 hover:underline hover:decoration-dotted hover:underline-offset-2 transition-all duration-300">X</Link>.
5078
</>
5179
)
5280
}
@@ -73,15 +101,16 @@ export default function FAQSection() {
73101
value={`item-${index}`}
74102
className={cn(
75103
"border border-transparent rounded-[2px] bg-card mb-4 last:mb-0",
76-
"hover:shadow-lg hover:border-teal-700 dark:hover:border-teal-200",
104+
"hover:shadow-lg",
77105
"transition-all duration-300 cursor-pointer"
78106
)}
79107
>
80108
<AccordionTrigger className={cn(
81109
"text-left hover:no-underline group cursor-pointer px-4",
82-
"data-[state=closed]:py-3 data-[state=open]:py-4"
110+
"data-[state=closed]:py-3 data-[state=open]:py-4",
111+
"[&[data-state=open]_span]:text-foreground"
83112
)}>
84-
<span className="text-sm sm:text-[15px] leading-relaxed font-mono uppercase text-foreground group-hover:text-teal-700 dark:group-hover:text-teal-200 transition-all duration-300">
113+
<span className="text-sm sm:text-[15px] leading-relaxed font-mono font-normal uppercase text-muted-foreground group-hover:text-foreground group-hover:underline group-hover:decoration-dotted group-hover:underline-offset-2 transition-all duration-300">
85114
{item.question}
86115
</span>
87116
</AccordionTrigger>

apps/docs/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717
"fumadocs-ui": "15.8.0",
1818
"lucide-react": "^0.541.0",
1919
"mermaid": "^11.12.0",
20-
"next": "15.5.0",
20+
"next": "15.5.7",
2121
"next-themes": "^0.4.6",
2222
"react": "^19.1.1",
2323
"react-dom": "^19.1.1",

0 commit comments

Comments
 (0)