> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/technical-guides/mcp-server.md). # MCP Server The Smartico **MCP Server** lets an AI assistant — or any program you write — work with your Smartico back-office through a single, standardized interface. Ask it to build a segment, draft a campaign, look up how a feature works, or discover which analytics tables answer a question, all in plain language or with simple API calls. Instead of clicking through builders and forms, you describe what you want, review the assistant's proposal, and confirm. The assistant does the setup. The same service is also a **direct API**: the endpoint an AI assistant connects to can be called directly from your own scripts and backend services, with no AI assistant or special library required. ### What is the MCP Server? MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external systems in a structured, safe way. The Smartico MCP Server exposes your platform as a set of **tools** the assistant can call: it can discover what object types exist, read your existing records, create and update campaigns and segments, run platform operations, and search the product knowledge base. Every call runs against **one label (environment)** and respects the permissions of the back-office user the token belongs to — the assistant can only see and change what that user could change in the UI. Think of it as giving an AI assistant a "Smartico plug-in": it knows what exists in *your* label, understands how Smartico's tools fit together, and can build and save configurations for you — always with your confirmation. And because the same endpoint speaks a standard protocol over HTTP, developers can call it directly as an API to automate the same operations programmatically. ### Why it exists * **Talk to your platform in natural language.** Describe the segment or campaign you want; the assistant assembles it using the same rules the back-office enforces. * **Automate repetitive work.** Clone campaigns, bulk-update templates, or estimate audiences from a script. * **Keep humans in control.** Every write can be previewed with `dry_run` before it commits, and every action is scoped to your token's label and permissions. * **One interface for everything.** The same protocol covers messaging, segmentation, campaigns, gamification look-ups, product knowledge, and analytics schema discovery. Setting up a precise audience or a multi-step automation in the back-office takes time and platform know-how: finding the right user properties, choosing the correct operators and values, and combining conditions so the logic is exactly right. Consider a segment like: > *Players whose total deposits are over €100, whose favourite product is Casino, and who haven't logged in for the last 7 days.* Building that by hand means several screens and careful attention to detail. With the MCP integration, you describe it in one sentence; the AI assistant finds the right properties in your label, assembles the logic, validates it, and shows you a plain-language summary to approve before anything is saved. The result: routine configuration work that used to take minutes (and platform expertise) becomes a short conversation — or a single API call — while you stay in full control of what gets created. ### What you can do today | Area | What you can do | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Segments** | Create and update audience segments with user-state and behavioural logic; list, read, estimate their size. See [MCP Segments Management](/welcome/technical-guides/mcp-server/mcp-segments-management.md). | | **Automation rules** | Create and update real-time and scheduled automation rules. | | **Campaigns** | Create and update campaigns, edit their flow (steps, branches, delays, communications), manage tags and stop/convert rules, clone, start, stop, and change speed. | | **Messaging templates** | Create and update Push, Email, Popup, Inbox, IVR, and Instant-message templates. | | **Label tags** | Create and update label tags. | | **Banners & placements** | Create and update banners and banner placements; link or unlink banner variations to placements. | | **Forms** | Create and update user-facing forms; send active forms to players via personal-form campaigns. | | **Reference data (read-only)** | Look up user properties, events, and activities used to build conditions and flows. | | **Bonus templates** | Create and update bonus templates; look up bonus types and dynamic configuration options. | | **Gamification & catalog** | Look up missions, badges, mini-games, raffles, jackpots, clans, tournaments, and deep links. Levels, avatars, avatar AI prompts, dynamic reward formulas, and tournament scoring formulas can be created and updated. | | **Product knowledge** | Search the Smartico help articles, academy, FAQ, and public API docs and get cited passages. | | **Analytics data knowledge** | Discover which data-warehouse tables answer a question, with their columns, joins, and example queries. | | **Media library** | Upload images, videos, audio, and documents with the `upload_media` operation; search files, change their tags, or delete them. See [MCP - How to manage images](/welcome/technical-guides/mcp-server/mcp-how-to-manage-images.md). | Read-only object types can be listed, fetched, and described, but not created or updated through MCP. For data warehouse exploration and analytics workflows, see [MCP for Data Analysis](/welcome/technical-guides/mcp-server/mcp-for-data-analysis.md). For every tool, operation, and entity type — and which ones can be created or updated — see [MCP - Tools and entity types](/welcome/technical-guides/mcp-server/mcp-tools-and-entity-types.md). {% hint style="info" %} **Can be created and changed:** segments, automation rules, campaigns, messaging templates (push, email, popup, inbox, IVR, instant message), bonus templates, levels, formulas (dynamic reward and tournament scoring), label tags, banners, banner placements, forms, avatars, and avatar AI prompts. **Can be changed but not created:** media files (tags and deletion) — new files are added with the `upload_media` operation. **Read-only:** properties, event types, activity types, bonus types, deep links, communication gateways (email, instant messaging, IVR), and the gamification catalog (missions, badges, mini-games, raffles, jackpots, clans, tournaments). They are available to read and reason about, so the right configuration can be built — they are not edited directly. {% endhint %} #### Example prompts * *"Create a segment of players at the Gold gamification level with more than 5 total deposits who haven't logged in for 7 days."* * *"Build a high-value churning segment: total deposits over €500 and last login more than 30 days ago."* * *"Archive the segment named 'Summer Promo Q3' - it's no longer needed."* * *"Set up a real-time rule that gives 10 diamonds when a user makes their first deposit."* * *"Update the 'Active Sports Bettors' rule to also exclude users flagged as bonus abusers."* * *"Draft a campaign that emails Gold-level players who haven't logged in for 7 days, then follow up with a push after 24 hours."* * *"Clone campaign 12345 into a new draft and show me the flow before I start it."* {% hint style="info" %} **A note on how segments work.** Segments are built from a user's current state - lifetime totals (e.g., total deposit count, total deposit amount), last-activity dates (e.g., last login, last deposit), and current attributes (e.g., gamification level, favorite product). Describe your audience using these, and your assistant will build it reliably. Rolling time-window conditions, such as "deposited 5 times this month" or "claimed a bonus this week," need to be expressed with the same intent - lifetime total plus a last-activity date instead - for example, *"more than 5 total deposits and last deposit within the last 30 days"*. For full guidance on constructing audience filters, see [MCP Segments Management](/welcome/technical-guides/mcp-server/mcp-segments-management.md). {% endhint %} ### Where to go next * [MCP - Connection and security](/welcome/technical-guides/mcp-server/mcp-connection-and-security.md) — connect your AI assistant or call the server as an API, sign in with Smartico (OAuth) or use a static token, how a request is processed, and the security model. * [MCP - Tools and entity types](/welcome/technical-guides/mcp-server/mcp-tools-and-entity-types.md) — the 13 tools, the operations, and which entity types can be read, created, or updated. * [MCP Access Profiles](/welcome/technical-guides/mcp-server/mcp-access-profiles.md) — which tools each access profile allows, and how to assign profiles to users and tokens. * [MCP Segments Management](/welcome/technical-guides/mcp-server/mcp-segments-management.md), [MCP for Data Analysis](/welcome/technical-guides/mcp-server/mcp-for-data-analysis.md), [MCP - How to manage images](/welcome/technical-guides/mcp-server/mcp-how-to-manage-images.md), and [MCP - label and brand settings](/welcome/technical-guides/mcp-server/mcp-label-and-brand-settings.md) — step-by-step guides for common work. ### Usage limits * MCP tool calls are **not rate-limited** on their own. * The actions that consume **AI tokens** are audience estimation (`estimate_audience`), data-warehouse SQL queries (`exec_sql`), and avatar AI prompt tests (`test_avatar_prompt`); they count toward your label's monthly AI usage — the first two by the volume of data scanned, a prompt test per generated image. Everything else — reference reads, entity discovery, creates, and updates — does not consume AI tokens. ### Frequently asked questions **Do I need to know how Smartico segments and rules work to use this?** It helps, but it isn't required. You describe what you want in plain language, and the assistant uses `entity_describe` and the built-in guides to assemble it with the same rules the back-office enforces. Use `dry_run` to preview before anything is saved. **Can I use it without an AI assistant?** Yes. The server is a standard JSON-RPC 2.0 API — you can call it directly from your own scripts or integrations with an MCP token (see [MCP - Connection and security](/welcome/technical-guides/mcp-server/mcp-connection-and-security.md)). **Can the external assistant make a mistake?** The assistant only acts within your user's permissions and label, and every create or update can be previewed with `dry_run` before it commits. The dry-run validation catches structural errors before anything is saved, and you review a plain-language summary before confirming. If something looks off, just say so in the chat — the assistant will revise it. Riskier actions live behind `exec_operation`, which is not marked read-only, so assistants ask you to confirm it — you stay in control of anything that changes state. **Is this the same as Smartico's other AI features?** No. This is a connector that lets your own AI assistant operate your back-office. It's separate from the in-product AI assistants, though it can search the same product knowledge base. **What's coming next?** Coverage keeps expanding across the platform, and new tools and object types are added regularly. Whatever you connect today keeps up automatically — the same token and connection pick up new capabilities as they ship, with no reconfiguration. If there's a workflow you'd like exposed through MCP, let your Smartico contact know. **What is the difference between MCP tokens and the Public API?** MCP is built for platform configuration (creating segments, campaigns, rules, templates) and conversational AI tooling. For high-volume player event tracking, real-time gaming transactions, or front-end widget integration, use the Smartico Public API and front-end SDKs. **Is there an additional fee to use the MCP server?** No. Access to the MCP server endpoint and configuration tools is included with your Smartico platform license. Standard entity discovery, reads, creates, and updates do not incur extra costs. Only audience estimation, data-warehouse SQL queries, and avatar AI prompt tests consume monthly AI token allocation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.smartico.ai/welcome/technical-guides/mcp-server.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.