Cursor with Markup AI MCP
Overview
Connect Cursor to the hosted Markup AI MCP server at https://api.markup.ai/mcp/ so your agent can run brand-voice, clarity, persona, and other content checks inline. Add the remote server and log in through your browser.
You’ll need a Markup AI account to continue. Sign up at https://console.markup.ai/signup.
Add the Markup AI MCP Server to Cursor
Log in with OAuth
Open your MCP config
- Open Cursor Settings (
Cmd/Ctrl + ,). - Search for “MCP” and click Edit in mcp.json (use
~/.cursor/mcp.jsonfor all projects or.cursor/mcp.jsonfor one workspace).
Because there’s no secret in the file, this config is safe to commit to .cursor/mcp.json and share with your team. Each person logs in with their own Markup AI account.
Use an API key
Get your API key
- Visit https://console.markup.ai/signup and create an account.
- Copy your API key from the console.
Store your key securely. Prefer environment variables over committing keys to code—Cursor supports ${env:VAR} interpolation in headers.
Use either OAuth or an API-key header—not both. If you set an Authorization header, Cursor sends it instead of starting the login flow, so a bad key surfaces as a connection failure rather than an OAuth prompt.
Restart & Verify
- Save
mcp.json. - Fully restart Cursor.
- Open a new chat and confirm the
markup-aiserver and its tools are listed.
Test Your Setup
Troubleshooting
- If tools don’t appear, confirm
mcp.jsonis valid JSON andmcpServersis at the top level. - Verify the URL is
https://api.markup.ai/mcp/, including the trailing slash—without it the request redirects and Cursor can’t discover the OAuth endpoints. - If the login flow doesn’t start, make sure the entry has no
headersblock; anAuthorizationheader suppresses OAuth. - Restart Cursor after changes; a full restart is often required.
Links
- Official Cursor MCP docs: https://cursor.com/docs/mcp