Add Gifi to Cursor, Claude, and Claude CodeThirty seconds in Cursor.

Start with Cursor. Point .cursor/mcp.json at the MCP URL, then sign in and approve scopes. Same inspect, clean, rewrite and usage as the API. Every plan. Remote auth is OAuth 2.1. A pasted GitHub skill is a prompt. Gifi is a signed-in connector.

Markdown
https://gifi.ai/mcp

Connect

Cursor

Thirty seconds. .cursor/mcp.json or ~/.cursor/mcp.json. Point it at the URL, then sign in.

{
  "mcpServers": {
    "gifi": {
      "url": "https://gifi.ai/mcp"
    }
  }
}

Claude Code

Then /mcp to sign in. JSON needs `"type": "http"`.

claude mcp add --transport http gifi https://gifi.ai/mcp

Claude

Settings → Connectors → Add custom connector. OAuth opens in the browser. CIMD, not DCR.

https://gifi.ai/mcp

Local stdio

API key, not OAuth. Stdio-only hosts: mcp-remote.

GIFI_API_KEY=wmr_live_... npx tsx mcp/stdio.ts
npx mcp-remote https://gifi.ai/mcp

Tools

Inspect

no credits

What is present. Nothing is changed.

Clean

text no credits · file 1 credit

Unicode in text, or metadata in a file.

Rewrite

1 credit per candidate

Different words. Best-effort.

Usage

no credits

Balance, limits, last 30 days.

What this cannot promise

  • We cannot certify a vendor detector. SynthID-Text uses a private key.
  • A rewrite does not prove human authorship.
  • Pixel, audio and video watermarks are out of scope.

Questions

Can I use Gifi from Cursor, Claude or another agent?
Yes. Add https://gifi.ai/mcp. Sign in, approve scopes. Same credits as the API. A pasted GitHub skill is a prompt. Gifi is a signed-in connector.
Is MCP different from the API?
No. Same tools, credits and limits. Remote uses OAuth; stdio uses an API key.

Subscribe, then connect.

See plansAPI reference