Read iContact contacts, lists, campaigns and message stats; add contacts and manage subscriptions. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"icontact": {
"url": "https://icontact.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"icontact": {
"type": "http",
"url": "https://icontact.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Application id (API-AppId), iContact username and API password.
Optional: Client folder id.
iContact API access needs an application id: register one in iContact's developer portal (help.icontact.com, search for "API Developer Portal") and set an API password for it. The API password is the one you choose for the application id, not your iContact login password. The username is the one you log in to iContact with. If your account has several client folders and you want one other than the first, enter its id. Your credentials are used only to call the iContact API on your behalf; they are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Application id (API-AppId), iContact username and API password. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the iContact connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
icontact_get_account | read | Get account The iContact account behind the credentials (company name, address, plan fields) and its client folders, with the folder this server uses. GET /a/ and GET /a/{accountId}/c/. |
icontact_list_contacts | read | List contacts List contacts (email, name, address, phone, status, create date). Filter by status, exact email, first/last name or a list the contact belongs to. GET /contacts. |
icontact_get_contact | read | Get contact One contact by id. GET /contacts/{contactId}. |
icontact_create_contact | write | Create contact WRITE: add one contact to the account (it is not added to any list; use icontact_set_subscription for that). Not idempotent: an email that already exists is reported by iContact as a warning. POST /contacts. |
icontact_update_contact | write | Update contact WRITE: change fields of one contact; only the fields you pass are sent. Setting status to donotcontact or deleted stops mail to that contact. POST /contacts/{contactId}. |
icontact_list_lists | read | List mailing lists List the account's mailing lists (name, description, welcome-message settings). GET /lists. |
icontact_get_list | read | Get mailing list One mailing list by id. GET /lists/{listId}. |
icontact_list_subscriptions | read | List subscriptions List list memberships (subscriptionId, contactId, listId, status). Filter by list, contact or status. GET /subscriptions. |
icontact_set_subscription | write | Subscribe or unsubscribe contact WRITE: put a contact on a list (status normal, or pending to start double opt-in) or unsubscribe it (status unsubscribed). Only for contacts who agreed to receive mail. POST /subscriptions. |
icontact_list_campaigns | read | List campaigns List campaigns (the sender identity and settings that messages belong to). GET /campaigns. |
icontact_get_campaign | read | Get campaign One campaign by id. GET /campaigns/{campaignId}. |
icontact_list_messages | read | List messages List messages (subject, type, campaign, create date, HTML and text bodies). Filter by type or campaign. GET /messages. |
icontact_get_message | read | Get message One message by id, with subject and HTML/text bodies. GET /messages/{messageId}. |
icontact_get_message_statistics | read | Get message statistics Delivery statistics of a message (released, bounces, opens, clicks, unsubscribes, complaints, forwards). GET /messages/{messageId}/statistics. |
icontact_list_message_activity | read | List message activity Who opened, clicked, bounced from or unsubscribed after a message: one page of events for one message. GET /messages/{messageId}/opens | clicks | bounces | unsubscribes. |
icontact_list_sends | read | List sends List sends (a message sent to lists/segments: send id, message id, included/excluded lists, scheduled time, status). GET /sends. |
icontact_get_send | read | Get send One send by id. GET /sends/{sendId}. |
icontact_list_segments | read | List segments List saved segments (rule-based groups of contacts). GET /segments. |
icontact_get_segment | read | Get segment One segment by id. GET /segments/{segmentId}. |
icontact_list_custom_fields | read | List custom fields List the account's custom contact fields (name, type). GET /customfields. |
icontact_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
icontact_request_feature | Request a missing feature Tell usefulapi that the user needs something the iContact tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
icontact_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on iContact (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
icontact_cancel_subscription | Cancel the Pro subscription Cancel the caller's iContact Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run icontact_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this iContact server only. Subscribe with icontact_upgrade (it returns a Stripe Checkout link). Cancel any time with icontact_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running icontact_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by iContact. The server calls the iContact API with your own iContact access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Application id (API-AppId), iContact username and API password. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Application id (API-AppId), iContact username and API password. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the iContact API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in iContact.
Yes, if you approve it. 3 of the 20 iContact tools can create or change data. The other 17 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this iContact server only. Cancel any time: Pro then runs to the end of the paid period. Run icontact_usage_status to see how many calls you used.
Ask the AI to run icontact_upgrade: it returns a Stripe Checkout link. To cancel, run icontact_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with icontact_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.