Model Context Protocol lets AI assistants create and manage greeting cards in your iGreet account — no local install required.
Pick your platform below. Claude and ChatGPT connect with OAuth (URL only in most cases). Cursor uses a Bearer token from MCP settings.
Shared by every platform — copy these first, then follow the steps for your tool.
Paste this URL into your AI tool when asked for the MCP server endpoint.
Optional for Claude — installs iGreet best-practice guidance as a Skill.
Claude connects with OAuth auto-discovery. Paste the MCP URL only — Client ID and Secret are optional.
Use the URL from Connection details above (or from MCP settings).
On Free / Pro / Max:
Team / Enterprise: an Owner adds the connector under Organization settings → Connectors → Add → Custom → Web (URL only). Members then click Connect.
Click Connect, sign in to iGreet in the browser, and Authorize. You can revoke access later from MCP settings → Authorized clients.
In a conversation, open + → Connectors and enable the iGreet connector.
Install the Skill from the repository above so Claude follows iGreet best practices (draft first, always open the edit link).
ChatGPT connects with OAuth via Developer mode. It usually registers automatically; Client ID/Secret are only needed if ChatGPT asks for them.
Use the URL from Connection details above. Generate credentials in MCP settings only if prompted later.
In ChatGPT on the web: Settings → Security and login → Developer mode ON. Available on paid plans (Plus / Pro / Business / Enterprise / Edu).
/mcp)Complete the browser sign-in and Authorize on iGreet. Paste Client ID / Secret only if ChatGPT asks for them.
Open a chat → Plus menu → Developer mode → select the iGreet app. Confirm tool calls when ChatGPT asks.
Cursor connects with a Bearer token from MCP settings → Token access.
Open MCP settings → Token access, click Connect, and copy the one-time token. Enable Allow send / schedule only if you want the assistant to schedule or send without opening iGreet first.
Go to Settings → Tools & MCP → New MCP Server,
or edit ~/.cursor/mcp.json (global) / .cursor/mcp.json (project):
{
"mcpServers": {
"igreet": {
"url": "https://igreet.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN_HERE"
}
}
}
}
Save / refresh and check that iGreet shows as connected in Tools & MCP. Use it from Agent mode.
Revoke the token from MCP settings → Token access if you need to rotate access.
Any remote MCP client that supports HTTP MCP can connect to iGreet. Prefer OAuth when available; otherwise use a Bearer token.
Paste the MCP server URL and complete the authorize flow in the browser. Provide Client ID / Secret from MCP settings only if the client requires static credentials.
Create a token under Token access, then send
Authorization: Bearer … on every request to the MCP URL (same pattern as Cursor).
Add a remote HTTP MCP server with the URL above. Use OAuth or headers per that tool’s docs, then authorize or paste your Bearer token.
Once connected, your assistant can help with everyday iGreet tasks.
Your assistant cannot buy packs or complete checkout for you. It always shares an edit link so you can open the card in iGreet anytime.
Each connection belongs to your iGreet account. By default it can read and create drafts. Sending or scheduling needs an extra permission you choose when connecting. You can revoke a connection anytime from MCP settings.
Important actions like create, schedule, and send are logged for your account.
How we handle connector data is described in our Privacy Policy (see “AI Assistants and MCP Connectors”).