Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Smile IO is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
14
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Look up loyalty customers, points history, rewards and VIP tiers, and add points or activities.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http smile-io-mcp https://smile-io.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# smile_list_customers, smile_get_customer, smile_list_points_transactions and 11 more
Smile IO costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http smile-io-mcp https://smile-io.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | Exact email address to look up. | |
| state | string | no | candidate = not yet joined, member = in the program, disabled = excluded. |
| updated_at_min | string | no | Only records updated at/after this ISO 8601 date-time, e.g. 2026-01-01T00:00:00Z. |
| include_vip_status | boolean | no | Include each customer's vip_status object (include=vip_status). |
| limit | integer | no | Maximum number of results, 1-250 (Smile default 50). |
| cursor | string | no | Cursor from the previous response's metadata.next_cursor (or previous_cursor). Omit for the first page. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | yes | Smile customer ID. |
| include | array | no | Related objects to include, e.g. ["vip_status.vip_tier", "vip_status.next_vip_tier"]. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | no | Only this customer's transactions. |
| updated_at_min | string | no | Only records updated at/after this ISO 8601 date-time, e.g. 2026-01-01T00:00:00Z. |
| limit | integer | no | Maximum number of results, 1-250 (Smile default 50). |
| cursor | string | no | Cursor from the previous response's metadata.next_cursor (or previous_cursor). Omit for the first page. |
Fetch one points transaction by ID. Smile: GET /points_transactions/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| points_transaction_id | integer | yes | Smile points transaction ID. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| exchange_type | string | no | Only fixed- or variable-price products. |
| page | integer | no | Page number, starting at 1. |
| page_size | integer | no | Results per page, 1-250 (default 50). |
Fetch one points product (a way to redeem points) by ID, including its reward. Smile: GET /points_products/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| points_product_id | integer | yes | Smile points product ID. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | no | Only this customer's rewards. |
| fulfillment_status | string | no | — |
| usage_status | string | no | — |
| updated_at_min | string | no | Only records updated at/after this ISO 8601 date-time, e.g. 2026-01-01T00:00:00Z. |
| limit | integer | no | Maximum number of results, 1-250 (Smile default 50). |
| cursor | string | no | Cursor from the previous response's metadata.next_cursor (or previous_cursor). Omit for the first page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum number of results, 1-250 (Smile default 50). |
| cursor | string | no | Cursor from the previous response's metadata.next_cursor (or previous_cursor). Omit for the first page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include | array | no | Nested objects to include, e.g. ["perks", "entry_rewards"]. |
Fetch the points program's configuration, e.g. the points currency label ("Points", "Stars"). Smile: GET /points_settings.
No parameter schema on file.
Fetch the referral program's configuration: whether it is active, and the sender (advocate) and receiver (friend) rewards. Smile: GET /referral_settings.
No parameter schema on file.
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | yes | Smile customer ID. |
| points_change | integer | yes | Points to add (positive) or deduct (negative). |
| description | string | no | Customer-visible reason, e.g. "Points correction". |
| internal_note | string | no | Merchant-only note, never shown to the customer. |
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 acti
| Parameter | Type | Required | Notes |
|---|---|---|---|
| token | string | yes | Activity type token, e.g. activity_f57a9b5a8d0ac5. |
| customer_id | integer | no | Smile customer ID (or give customer_email). |
| customer_email | string | no | Customer email (or give customer_id). |
| distinct_id | string | no | Unique id for this activity in your system; prevents duplicates for the same token. |
| created_on_origin_at | string | no | ISO 8601 date-time the action actually happened, if earlier than now. |
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 redemp
| Parameter | Type | Required | Notes |
|---|---|---|---|
| points_product_id | integer | yes | Smile points product ID. |
| customer_id | integer | yes | Smile customer ID. |
| points_to_spend | integer | no | Points to spend — variable-price products only. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Smile IO or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Smile IO can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.