iContact MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://icontact.usefulapi.io/mcp

claude mcp add --transport http icontact https://icontact.usefulapi.io/mcp

{
  "mcpServers": {
    "icontact": {
      "url": "https://icontact.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "icontact": {
      "type": "http",
      "url": "https://icontact.usefulapi.io/mcp"
    }
  }
}

https://icontact.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• icontact_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

  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

  One contact by id. GET /contacts/{contactId}.

• icontact_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: 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

  List the account's mailing lists (name, description, welcome-message settings). GET /lists.

• icontact_get_list

  One mailing list by id. GET /lists/{listId}.

• icontact_list_subscriptions

  List list memberships (subscriptionId, contactId, listId, status). Filter by list, contact or status. GET /subscriptions.

• icontact_set_subscription

  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

  List campaigns (the sender identity and settings that messages belong to). GET /campaigns.

• icontact_get_campaign

  One campaign by id. GET /campaigns/{campaignId}.

• icontact_list_messages

  List messages (subject, type, campaign, create date, HTML and text bodies). Filter by type or campaign. GET /messages.

• icontact_get_message

  One message by id, with subject and HTML/text bodies. GET /messages/{messageId}.

• icontact_get_message_statistics

  Delivery statistics of a message (released, bounces, opens, clicks, unsubscribes, complaints, forwards). GET /messages/{messageId}/statistics.

• icontact_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

  List sends (a message sent to lists/segments: send id, message id, included/excluded lists, scheduled time, status). GET /sends.

• icontact_get_send

  One send by id. GET /sends/{sendId}.

• icontact_list_segments

  List saved segments (rule-based groups of contacts). GET /segments.

• icontact_get_segment

  One segment by id. GET /segments/{segmentId}.

• icontact_list_custom_fields

  List the account's custom contact fields (name, type). GET /customfields.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 71 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 20 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32403 servers in this category
• Published to the registry more recently than 97% of the other 32403 servers in this category
• Basic checks equal to or better than 100% of the other 32403 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{