Claude · Cursor · any MCP host
MarkdownGive the agent the same tools. It spends the same credits.
Sign in, approve scopes. Same inspect, clean, rewrite and usage as the API. Every plan. Remote auth is OAuth 2.1.
https://gifi.ai/mcpConnect
Claude
Settings → Connectors → Add custom connector. OAuth opens in the browser. CIMD, not DCR.
https://gifi.ai/mcpClaude Code
Then /mcp to sign in. JSON needs `"type": "http"`.
claude mcp add --transport http gifi https://gifi.ai/mcpCursor
.cursor/mcp.json or ~/.cursor/mcp.json.
{
"mcpServers": {
"gifi": {
"url": "https://gifi.ai/mcp"
}
}
}Local stdio
API key, not OAuth. Stdio-only hosts: mcp-remote.
GIFI_API_KEY=wmr_live_... npx tsx mcp/stdio.tsnpx mcp-remote https://gifi.ai/mcpTools
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 Claude, Cursor or another agent?
- Yes. Add https://gifi.ai/mcp. Sign in, approve scopes. Same credits as the API.
- Is MCP different from the API?
- No. Same tools, credits and limits. Remote uses OAuth; stdio uses an API key.