Smile.io MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Smile.io MCP by usefulapi is answering right now. Last checked 5 min ago. It exposes 14 tools. Last commit 10 Oct 2026.

Look up loyalty customers, points history, rewards and VIP tiers, and add points or activities.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

93 ms

Response time

average over 24h

Stars

last commit 10 Oct 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

7 Oct a tool changed version2 times that day

30 Sep a tool changed version

and 4 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check Smile.io MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.smile-io]
url = "https://smile-io.usefulapi.io/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

smile

smile_create_activity

WRITE: record that a customer performed an action (identified by an activity type token configured in Smile Admin, e.g. a custom 'newsletter signup' activity). Smile then asynchronously applies the store's earning rules and may issue points or rewards. Identify the customer by customer_id OR customer_email (exactly one). Pass distinct_id (e.g. an order number) to make it idempotent — a second activity with the same token + distinct_id is rejected. Custom activity types need Smile's Plus/Enterprise plan. Requires the activity:write scope. Smile: POST /activities.

smile_create_points_transaction

WRITE: add or deduct points from a customer's balance (a manual adjustment, e.g. a goodwill credit or a correction). points_change > 0 adds, < 0 deducts; Smile rejects a deduction that would make the balance negative. Undo by creating an opposite adjustment. `description` is shown to the customer; `internal_note` is merchant-only. To reward a customer for completing an action, prefer smile_create_activity. Requires the points_transaction:write scope. Smile: POST /points_transactions.

smile_get_customer

Fetch one customer by Smile customer ID: name, email, state, points_balance, referral_url, vip_tier_id, and optionally their VIP status with current and next tier. Smile: GET /customers/{id}.

smile_get_points_product

Fetch one points product (a way to redeem points) by ID, including its reward. Smile: GET /points_products/{id}.

smile_get_points_settings

Fetch the points program's configuration, e.g. the points currency label ("Points", "Stars"). Smile: GET /points_settings.

smile_get_points_transaction

Fetch one points transaction by ID. Smile: GET /points_transactions/{id}.

smile_get_referral_settings

Fetch the referral program's configuration: whether it is active, and the sender (advocate) and receiver (friend) rewards. Smile: GET /referral_settings.

smile_list_customers

List loyalty-program customers, newest first, with their points balance, state and VIP tier id. Look a customer up by exact email, or filter by state or last-updated time. Cursor-paginated (metadata.next_cursor). Smile: GET /customers.

smile_list_earning_rules

List the enabled earning rules — the ways customers earn points or rewards (placing an order, signing up, birthdays, custom activities), with reward, reward_value, earning_limit and any VIP-tier restriction. Cursor-paginated. Smile: GET /earning_rules.

smile_list_points_products

List points products — the rewards customers can buy with points. 'fixed' products cost points_price; 'variable' products trade variable_points_step points for variable_points_step_reward_value, between variable_points_min and variable_points_max. Each embeds its reward. Page-numbered (page, page_size); a page shorter than page_size is the last. Smile: GET /points_products.

smile_list_points_transactions

List points transactions (every earn, spend and manual adjustment), newest first — e.g. a customer's full points history. Each has points_change (+/-), a customer-visible description and a merchant internal_note. Cursor-paginated. Smile: GET /points_transactions.

smile_list_reward_fulfillments

List rewards that have been issued to customers — usually discount codes — with code, fulfillment_status (pending/issued/cancelled/failed), usage_status (used/unused/untracked), used_at and expires_at. Use customer_id to answer 'what codes does this customer have?'. Cursor-paginated. Smile: GET /reward_fulfillments.

smile_list_vip_tiers

List the VIP program's tiers, sorted by milestone (the threshold to reach each tier), optionally with each tier's perks and entry rewards. Smile: GET /vip_tiers.

smile_purchase_points_product

WRITE — SPENDS THE CUSTOMER'S POINTS: redeem points on the customer's behalf by purchasing a points product; Smile deducts the points and issues the reward (the response's points_purchase.reward_fulfillment usually holds a discount code). Only do this when the customer asked for it. For a 'variable' product pass points_to_spend; leave it out for 'fixed' products. There is no API to cancel a redemption — a mistaken one can only be compensated with smile_create_points_transaction. Requires the points_purchase:write scope. Smile: POST /points_products/{id}/purchase.

Endpoints

URL	Transport	State	Latency	Checked
https://smile-io.usefulapi.io/mcp	streamable-http	answering	66 ms	5 min ago

Alternatives to Smile.io MCP by usefulapi

same job, measured the same way

Shopmonkey MCP by usefulapi

by usefulapi

Look up shop customers, vehicles, work orders and parts, and create orders or book appointments.

23 tools answering

MailBluster MCP by usefulapi

by usefulapi

Manage MailBluster leads, custom fields, products and orders: look up, add and update records.

13 tools answering

Veeqo MCP by usefulapi

by usefulapi

Read Veeqo orders, products, stock, warehouses, customers and POs; add notes, tag, set stock.

22 tools answering

Loyverse MCP by usefulapi

by usefulapi

Query Loyverse POS receipts, shifts, items, inventory and customers, and update stock and customers.

21 tools answering

Ecwid MCP by usefulapi

by usefulapi

Read store products, orders, customers, categories and coupons; adjust inventory and update orders.

12 tools answering

Waitwhile MCP by usefulapi

by usefulapi

Read Waitwhile visits, bookings, customers, services and analytics; add, update and cancel visits.

29 tools answering

Braintree MCP by usefulapi

by usefulapi

Search Braintree transactions, customers and payment methods, and refund or void charges.

7 tools answering

Boulevard MCP by usefulapi

by usefulapi

Look up appointments, clients, services, staff and orders, and update clients in Boulevard.

21 tools answering

Smile.io MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Smile.io MCP by usefulapi do?

It exposes 14 tools, read directly from the server on our last check. Among them: smile_create_activity, smile_create_points_transaction, smile_get_customer, smile_get_points_product, smile_get_points_settings, smile_get_points_transaction and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Smile.io MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 93 ms. The bar chart above shows every period we have measured.

How do I connect Smile.io MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Smile.io MCP by usefulapi need an API key?

No. Smile.io MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Smile.io MCP by usefulapi?

It answers our handshake in 93 ms on average, which is faster than 87% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Smile.io MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.