# MCP

Give 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/mcp`

## Connect

### Claude

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

```
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
```

### Cursor

.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.ts
```

```
npx mcp-remote https://gifi.ai/mcp
```

## Tools

### Inspect

`inspect` · no credits

What is present. Nothing is changed.

### Clean

`clean` · text no credits · file 1 credit

Unicode in text, or metadata in a file.

### Rewrite

`rewrite` · 1 credit per candidate

Different words. Best-effort.

### Usage

`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.

[See plans](https://gifi.ai/pricing.md). [API reference](https://gifi.ai/docs.md).