SupWriter logoSupWriter
Cursor

Humanize AI text inside Cursor

Cursor is where you write code and docs. Add SupWriter to its MCP config and humanize a generated README or grammar-check documentation without leaving the editor.

https://supwriter.com/api/mcpOAuth sign-in · uses your plan credits

Two ways to connect

Sign in with OAuth, or use a Direct API key if you'd rather skip the sign-in screen. Either way, calls use your existing plan credits.

Recommended

Sign in with OAuth

  1. 1

    Open MCP settings

    In Cursor, open Settings → Tools & Integrations (the MCP section) and click New MCP Server. That opens your mcp.json — ~/.cursor/mcp.json for every project, or .cursor/mcp.json for just this one.

  2. 2

    Add the server

    Under "mcpServers", add an entry named "supwriter" with "url": "https://supwriter.com/api/mcp". The URL alone is enough — Cursor handles the OAuth sign-in.

  3. 3

    Authenticate

    Save, then toggle SupWriter on in the MCP panel. Cursor opens your browser to sign in to SupWriter and approve access; the indicator turns active.

  4. 4

    Use it

    In the Agent (Composer), ask: "Humanize the draft README."

Alternative

Connect with a Direct API key

For clients that take an Authorization header (and headless agents). Requires a Pro or Ultra plan.

  1. 1

    Create an API key

    In SupWriter, open Settings → API & MCP → API keys and create a key. API access requires a Pro or Ultra plan.

  2. 2

    Add the server with a header

    Point your client at https://supwriter.com/api/mcp and send the key as an "Authorization: Bearer" header — no sign-in screen needed.

  3. 3

    Start writing

    The key inherits your plan credits. Rotate or revoke it any time from Settings → API & MCP.

Example client config
# Cursor / Claude Code — JSON, "mcpServers" key (~/.cursor/mcp.json)
{
  "mcpServers": {
    "supwriter": {
      "url": "https://supwriter.com/api/mcp",
      "headers": { "Authorization": "Bearer sw_live_your_key" }
    }
  }
}

# VS Code — JSON, "servers" key, type "http" (.vscode/mcp.json)
{
  "servers": {
    "supwriter": {
      "type": "http",
      "url": "https://supwriter.com/api/mcp",
      "headers": { "Authorization": "Bearer sw_live_your_key" }
    }
  }
}

# Codex — TOML (~/.codex/config.toml). Codex sends the env var's VALUE as the
# bearer token, so export SUPWRITER_TOKEN=sw_live_your_key first.
[mcp_servers.supwriter]
url = "https://supwriter.com/api/mcp"
bearer_token_env_var = "SUPWRITER_TOKEN"

# Claude Code — one command
claude mcp add --transport http supwriter https://supwriter.com/api/mcp \
  --header "Authorization: Bearer sw_live_your_key"
Create an API key

Test it

Once connected, ask Cursor to use a tool. A few prompts that work well:

  • “Humanize this so it reads naturally: <your text>”
  • “Paraphrase this in a casual tone: <your text>”
  • “Grammar-check and fix this paragraph: <your text>”
  • “Run an AI-detection check on the text above and tell me which sentences look AI-written.”

FAQ

Does connecting cost anything extra?

No separate MCP fee — calls draw on the word credits already in your SupWriter plan (one credit per word). AI detection is metered over MCP too (one credit per word analyzed), the same as the REST API; it's free only inside the web app.

Is my account safe?

Yes. You authorize either through SupWriter's own OAuth sign-in — approving a consent screen that lists exactly what the client can do — or with a scoped API key. OAuth tokens are short-lived, and keys can be rotated or revoked any time from Settings → API & MCP.

Which tools become available?

Four: humanize, paraphrase, grammar-check, and AI detection — the same engines that power the SupWriter editor.

Want the full walkthrough with screenshots?

Read the Cursor setup guide