AI tools (MCP server)

1.What it is

Our MCP server lets an AI assistant work with your Gia’s Giraffes account: find gifts in the catalog, look up contacts and upcoming birthdays and meetings, check whether a gift was opened or redeemed, and draft and send gifts. You talk to the assistant in plain words; it calls our tools. It’s part of Pro (including Complimentary Pro and Pro team seats).

The server URL is:

https://www.giasgiraffes.com/api/mcp

It uses the Model Context Protocol’s Streamable HTTP transport, signs you in with OAuth on our consent screen, and also accepts your API keys for developer tools (a key keeps its scope there: read only, read and draft, or read, draft and send; a test key only touches test data). Manage connections, keys, limits and usage in the Developer hub.

2.Connect Claude (web and desktop)

1. In Claude, open Customize → Connectors, choose + Add, then Add custom connector.
2. Name it Gia’s Giraffes and paste https://www.giasgiraffes.com/api/mcp as the URL. Leave the OAuth settings on their defaults.
3. Choose Connect. Sign in to Gia’s Giraffes if asked, pick what Claude can do and its spending limits, then choose Allow.

On a Claude Team or Enterprise plan, an owner adds custom connectors for the organization in its connector settings first.

3.Connect ChatGPT

1. In ChatGPT, open Settings → Apps & Connectors. If custom connectors are off, turn on Developer mode under Advanced settings (on a business workspace, an admin may need to allow it).
2. Choose Create (or Add custom MCP server), name it Gia’s Giraffes, paste https://www.giasgiraffes.com/api/mcp and choose OAuth for authentication.
3. Confirm, then sign in and choose Allow on our consent screen.

ChatGPT connects with OAuth only (not API keys).

4.Connect Cursor

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "gias-giraffes": { "url": "https://www.giasgiraffes.com/api/mcp" }
  }
}

Open Cursor Settings → MCP; next to Gia’s Giraffes choose Connect (or Needs login) and approve on our consent screen. To use an API key instead, add a header (keep the key in an environment variable, never in a shared file):

"gias-giraffes": {
  "url": "https://www.giasgiraffes.com/api/mcp",
  "headers": { "Authorization": "Bearer ${env:GIAS_GIRAFFES_API_KEY}" }
}

5.Connect Claude Code

Add the server, then sign in from Claude Code:

claude mcp add --transport http gias-giraffes https://www.giasgiraffes.com/api/mcp

In Claude Code, run /mcp, pick gias-giraffes and choose Authenticate. Your browser opens our consent screen. Or use an API key (it then skips OAuth):

claude mcp add --transport http gias-giraffes https://www.giasgiraffes.com/api/mcp \
  --header "Authorization: Bearer $GIAS_GIRAFFES_API_KEY"

6.Tools

Every tool says whether it only reads or changes something, so your AI tool can ask before the ones that spend money.

Example: “Send Avery a $50 thank-you”

1. The assistant finds Avery with search_contacts.
2. It calls create_gift_draft with her contact, budget_cents: 5000 and your note. Nothing is sent. It shows you the summary: who, what (her choice of gifts up to $50), the note, the most it can cost, and the card.
3. You say “send it”. It calls send_gift with the draft id and confirm: true. Avery gets her gift by email; you’re charged only if she accepts.
4. Later: “Did Avery redeem it?” → get_gift_status.

7.Safety and spending limits

• Nothing sends without a draft. send_gift needs a draft id and confirm: true; without it, it sends nothing and returns the summary. Drafts expire after 24 hours.
• Read-only connections. On the consent screen you can give a tool read-only access: it can search and look things up but can’t draft, send or create links.
• Spending limits per connection, per gift, per day and per month (new connections start at $100 a gift, $300 a day and $1000 a month). They count what gifts could cost (their budgets), so they hold before anyone redeems; a GG Link counts as claims × budget. Each send reserves its amount atomically, so several sends at once can’t together go over a limit. Change them on the consent screen or later in Settings.
• Teams. Owners can cap what each member sends through AI tools a month (Team page). Monthly team budgets and approvals apply as in the app: a gift over budget waits for approval.
• Your card stays with us. Gifts use your saved card (or your team card) and are charged only if accepted. If you have no card, the tool gives you a link to add one in the app; AI tools never see or collect card details.
• Recipients never see prices. Gifts are sent by email or as a link you share; AI tools don’t send texts.
• Each connection can make 60 requests a minute. Every tool call is logged (which tool, a summary of what was asked, the result), and gifts show “Sent via Claude” (or the tool’s name) in your gifts list and Reports.
• A connection only ever sees your own data (and your team’s shared contacts).

8.See and revoke connections

Settings → Developers → AI tools lists every tool that signed in with OAuth, with when it was last used, what it has spent, its limits and recent activity. Choose Revoke to disconnect one; it stops working immediately. A tool connected with an API key isn’t listed there: manage and revoke the key in Settings → Developers → API keys (its request counts are on the Usage tab), and it stops working the moment the key is revoked.

If your plan leaves Pro, connected tools get an upgrade message instead of results until you’re back on Pro. Questions: hello@giasgiraffes.com.