A project .cursor/mcp.json may be committed to your repo, so do not put a
real token in a file you commit. Use a placeholder and have each developer
fill in their own, or keep the config in the global ~/.cursor/mcp.json
instead. Prefer an MCP token (csk_mcp_…) from Settings › MCP. The csk_st_…
setup token in the integration prompt expires in 24 hours, so a config file holding one
stops working overnight.
Cursor
Connect CashSDK to Cursor so you can manage your account from the editor.
Add the CashSDK MCP server to Cursor and your agent can operate your workspace (model catalog, generate paywalls, register webhooks) without leaving the editor.
Add the server#
Create .cursor/mcp.json in your project root (or edit the global
~/.cursor/mcp.json to make it available everywhere):
{
"mcpServers": {
"cashsdk": {
"url": "https://mcp.cashsdk.com/mcp",
"headers": {
"Authorization": "Bearer csk_mcp_..."
}
}
}
}
Copy the token from your dashboard's integration prompt. It names the app it belongs to, so tools work without passing an app id.
Enable and verify#
Go to Cursor Settings → MCP (or Tools & Integrations). Cursor
detects the cashsdk server from your mcp.json.
Enable the cashsdk server. Cursor connects to the hosted endpoint over
HTTP, so there is nothing to install or spawn.
The server should show a green status and a list of tools like
get_setup_checklist, create_product, and generate_paywall. If it
shows an error, check the Authorization header. An expired or mistyped
setup token comes back as 401.
You can also add a .cursor/rules file pointing Cursor at
https://docs.cashsdk.com/llms-full.txt so the model always has the full
CashSDK reference in context. See llms.txt.
Example prompts#
Open the Cursor chat in Agent mode and try:
- "Using CashSDK, create a monthly Pro subscription with a
proentitlement." - "Generate an onboarding paywall from a template and add a placement for it."
- "Register a webhook at
https://api.myapp.com/hooks/cashsdkand send a test event." - "Tail the recent CashSDK events for this app."
- "What's still outstanding on my CashSDK setup checklist?"