Send personalized SMS, email, and WhatsApp campaigns you can actually track. Segment customers, automate follow-ups, and retarget based on real behavior. Built for Egypt, Saudi Arabia, UAE, and 8 more countries.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.nonito.io
39tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.nonito.io/mcp
Skill page: https://www.mcpbundles.com/skills/nonito-mcp-40e5664149
Explore capabilities (39)
read 17
write 7
other 1
Showing 25 of 39
Showing 25 of 39 tools from the public preview. Connect the server to inspect the full live tool list.
Get7
List6
Create2
Update2
Other capabilities8
Who am I
other
whoami
Return the Nonito user id resolved from the API key and basic profile info (company, email, currency, subscription, channel providers), plus a short brand summary (name, logo, primary colour, whether the customer confirmed it in onboarding). Useful as a smoke test that the connection works and to ground later tool calls in the user's account context. For the full brand (colours, fonts, socials, sender) call get_brand_kit.
Who am I — Return the Nonito user id resolved from the API key and basic profile info (company, email, currency, subscription, channel providers), plus a short brand summary (name, logo, primary colour, whether the customer confirmed it in onboarding). Useful as a smoke test that the connection works and to ground later tool calls in the user's account context. For the full brand (colours, fonts, socials, sender) call get_brand_kit.
Get brand kit — The workspace's brand as the customer confirmed it during Nonito onboarding: name, tagline, website, logo (an https URL safe for email), icon, the five colour roles (primary, secondary, accent, background, text) plus palette, heading and body fonts with email-safe font-family stacks, socials, contact details, and the email sender (address and display name). Call it before drafting any email and use these values: never invent brand colours, logos or fonts. `missing` lists brand facts that aren't
List flows — List the marketing automation flows in the user's Nonito workspace. Each flow can be active or inactive and represents a sequence of automated WhatsApp/SMS/email steps. Filter by status; results are ordered by created_at desc.
Get flow — Fetch a single flow by id, including its full configuration (nodes/edges) from flow_configurations.
Validate flow — Check a flow graph without saving anything: pass either flowId (an existing flow) or configuration (a draft). Returns errors that would stop the flow compiling or sending, warnings, and a summary (trigger, mode, paths, channels). Graph format (same as get_flow returns): exactly one kind of trigger with no incoming edges — an "event" node (data.event: "abandon cart" | "order confirmation" | "order delivered" | "order cancelled" | "refund created" | "customers email marketing consent update") or a
Create flow — Create a new flow as an inactive draft (it never starts sending on create — use enable_flow after). The graph is validated; an invalid graph is still saved as a draft (valid=false) so it can be finished in the app or with update_flow, and the errors are returned. Set is_marketing: true for promotional flows (abandoned cart, win-back, audience blasts) so opted-out customers are suppressed; false for transactional ones (order confirmation, delivery, refund). Graph format (same as get_flow returns)
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Send personalized SMS, email, and WhatsApp campaigns you can actually track. Segment customers, automate follow-ups, and retarget based on real behavior. Built for Egypt, Saudi Arabia, UAE, and 8 more countries.
How do I connect Nonito to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does Nonito provide?
Operate this server?
Request removal if you do not want Nonito listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Nonito?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
Update flow — Change a flow's name, description, is_marketing flag, or graph. For the graph, either replace it (configuration) or merge settings into specific nodes (node_updates, e.g. [{node_id:"wait-1", data:{waitTime:"2"}}]). Defaults to dry_run: true — returns the before/after diff, validation and warnings without saving. Pass dry_run: false to apply. Editing an ACTIVE flow takes effect for new entrants immediately; an active audience flow re-enrols its segment on every graph change. An update that would
Enable flow — Turn a flow on so it starts messaging customers. Defaults to dry_run: true — returns what will happen (trigger, audience size for audience flows, channels, validation) without enabling. Pass dry_run: false to enable. Refuses flows that fail validation. Event flows only affect customers who trigger the event from now on; AUDIENCE flows enrol their whole segment immediately. Always show the preview to the user and get their confirmation before calling with dry_run: false.
Disable flow — Turn a flow off so no new customers enter it. Defaults to dry_run: true — returns the flow and how many already-scheduled messages it has pending, without disabling. Pass dry_run: false to disable. Messages already scheduled before disabling are NOT cancelled.
List segments — List the user's audience segments from segments_summary_cache. Each row has segment_id, name, user_count, description, and source platform flags (shopify, zyda, foodics, form, prepit) indicating where the segment originated.
Get segment definition — Fetch one segment by segment_id (the integer id from list_segments): its kind (uploaded list, rule snapshot, live rule, or console rule), its rule (JSON plus a plain-English version) for rule segments, the older console filters (days_since_last_order, aov, area, order_count, product_ids, collection_ids) where set, is_live/is_uploaded flags, and its size: user_count (members with a phone) and email_count (distinct email addresses, including email-only members).
Segment rule fields — What a segment rule can filter on, with this workspace's own values: every field and its operators, the cities customers order from, products and collections (with the ids a rule needs), lifecycle stages with their sizes, value tiers and reachability. Call this before writing a rule for preview_segment or create_segment (mode "generate"). Rules need Shopify customer data; for other workspaces it says so, and segments are built by uploading a list.
Preview segment rule — Check a segment rule and see who it matches, without saving anything: how many customers, how many have a phone, an email, only an email, how many emails are opted out, how many are reachable by email, a masked sample, and the rule in plain words. A rule is {"match":"all"|"any","conditions":[{"field","op","value"}]}. Fields: days_since_last_order, days_since_first_order, order_count (whole numbers) and aov, total_spend (numbers) take gt/lt/eq/between — gt 60 on days_since_last_order means the la
Suggest segments — Suggest ready-made segments worth targeting, built from this workspace's own customers and lifecycle stages (e.g. Champions gone quiet, high-value At Risk, one-timers who used a discount, big spenders, lapsed 90–180 days, email-reachable shoppers). Each comes with its rule, live size and email reach; empty ones are left out. Pass a suggestion's name and rule to create_segment (mode "generate") to save it.
Create segment — Create an audience segment, two ways. mode "save": from data — contacts [{phone?, email?, name?}] and/or csv (pasted CSV/TSV/spreadsheet text; phone, email and name columns are found by header, e.g. phone/mobile/userid/رقم, email/e-mail/ايميل, name/الاسم; or first column = phone or email). Phones are normalised to international digits (Egyptian 01… → 201…), emails lower-cased, rows deduplicated, and invalid rows reported back. Rows with only an email are kept as email-only members. Up to 20,000
Update segment — Change a segment's name, description or rule, by segment_id. Rules can only change on segments built from a rule (uploaded lists have none); a snapshot is re-evaluated with the new rule, and a live segment updates its rule. Defaults to dry_run: true — the preview shows before/after sizes, every flow and unsent campaign that uses the segment, and a row_version. Apply with dry_run: false and the row_version (and confirmation_token when the preview asks for one). Flows and campaigns find segments b
Delete segment — Delete a segment by segment_id: its registry row and its members (phone and email-only). History (segment audit logs) is kept. Refused while an active flow or an unsent campaign uses it. Defaults to dry_run: true — the preview shows its size and everything that references it. Pass dry_run: false to delete; this cannot be undone.
List contacts — List Shopify customers in the workspace from fact_shopify_customer_info. Default sort is most-recent last_order_date. Includes lifetime spend, order count, AOV, first/last order dates.
Search contacts — Find contacts by email, phone, or first name (case-insensitive substring match). Provide at least one of email, phone, or name. Returns up to 50 matches; use get_customer_profile with a customer_id for the full picture.
Customer profile — Everything about one customer, as on their profile page in the console: contact details and cities; KPIs (completed orders, total spend, AOV, first/last order, days since last order); their Nonito Pulse lifecycle segment (stage, journey band, rule, next best action, value tier, last segment move); recent orders with which flow or campaign gets credit (last touch); the flows they have entered and what each sent them; marketing consent; and optionally their recent WhatsApp messages. Find the custo
Customer lifecycle segments (Nonito Pulse) — The customer base split into Nonito Pulse lifecycle segments — the same numbers as the Pulse page. 11 segments in 5 journey bands (Just arrived, Growing, Regulars, Slipping, Lapsed), each with customers, share of base, avg orders, AOV, revenue, avg days since last order, net change over the last 7 days, its rule and the next best action. Scored nightly for Shopify stores. These are automatic lifecycle segments; for the marketing audiences a merchant built themselves, use list_segments.
Customers in a lifecycle segment — List the customers currently in one Nonito Pulse lifecycle segment, with contact details, orders, spend, AOV, last order and value tier. Segments: New, One-Timer - Recent, Returning, Loyal, Champions, One-Timer - Cooling, Cooling, At Risk, One-Timer - Churned, Previously Loyal, Lost. Paginate with offset.
Customer changes this week — What changed in the customer base recently, in plain language — the same view as the console's "Changes this week". Groups customers who moved lifecycle segment into: Ordered again, Came back, Due for a 2nd order, Late, Gone quiet; with a one-line verdict, what each group means, what to do, the exact moves (before → this week), and the top customers in each group by value. Caveats: scores update nightly, and each customer carries only their latest move.
Get flow performance — Return cumulative all-time performance per flow from shopify_flow_analytics_overview: messages sent (whatsapp/sms/email), unique users, users with orders, total orders, order value, conversion rate. Pass a flowId for one flow, or omit for the top flows by total_messages_sent.
List flow-attributed orders — Recent Shopify orders attributed to a flow message (within the attribution window). Useful for proving ROI: shows order_name, value, phone, the flow that drove it, and when the message was sent vs when the order happened.
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 39 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Nonito require?
Nonito may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.