Connect guide
Connect Cursor to your brand.
Your product team writes more customer-facing words than most of marketing — interface copy, empty states, error messages, docs. Cursor speaks MCP natively, so it can read your brand model while it writes them.
Publish your brand
Import and publish your brand in SPOKEPROS. Copy the endpoint from your published brand page.
Add the MCP server
In Cursor's settings, add a new MCP server and paste your endpoint URL. It appears alongside the tools Cursor can already call.
Build
Generating a settings page, an onboarding flow, a 404? Cursor can pull your voice rules and colour and typography rules mid-task — so the copy sounds like the company and the styles match the system.
https://app.spokepros.com/api/mcp/your-brandMenus move between releases. The constant: wherever Cursor accepts a custom connector or MCP server, paste this URL. What the brand server is →
The result is the product and the marketing finally sounding like the same company — because they're reading the same model. When the brand updates, the next generation picks it up automatically.
Fair questions.
What's this actually useful for in a codebase?
Interface copy, empty states, error messages, docs pages, marketing pages built in code — anywhere a developer writes words or applies brand colours and type.
Does it expose our code or data to SPOKEPROS?
No. The connection is one-way: Cursor reads your published brand model. Nothing from your codebase is sent back.
Do developers need SPOKEPROS accounts?
No — the endpoint is read-only for published brands. One URL in the team's MCP config and everyone's covered.
One URL, and Cursor knows your brand.
Import, publish and connect on the Free plan — in one sitting.