MCP.Market

Xyla AI MCP server

online · 100% uptime
by xyla.ai·ai.xyla/xyla·v1.0.0

Social posts for Shopify and WooCommerce stores: approve posts, see results, change settings.

C65/100grade C
What users say
No reviews yet
Be the first
Safety scan
C65/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Xyla AI yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Xyla AI tools (20, 5 write)

write = sends, deletes, buys or posts
  • approve_first_batchFree

    Approves this Xyla shop's first batch of posts as a whole. When the shop can publish, this also turns autopilot on in include mode (the posts already made are scheduled and nothing is deleted), and releases posts held for review into the schedule. Posts go out at their scheduled times, not straight away.

  • approve_postsFree

    Approves posts in this Xyla shop that are waiting for approval, by their IDs from pending_approvals. Each approved post takes the next free slot in the schedule; nothing publishes straight away. Posts in the shop's first batch cannot be approved one by one: use approve_first_batch for those.

  • change_historyFree

    Lists recent changes to the shop's Xyla settings, newest first: what changed, before and after, who made it (the merchant, Xyla or the assistant), and the undo id to pass to undo_change.

  • change_settingsFree

    Changes the shop's Xyla settings in one setting group (or a few related ones) and returns each value before and after plus an undo id. Every change in a call applies, or none does. Read the group with get_settings first, and confirm the change with the merchant before calling this. Changes affect posts made from now on, not posts already scheduled or published.

  • confirm_post_fixwrite actionFree

    Runs a post fix that request_post_fix started in this Xyla shop, with the change the merchant asked for. Call post_fix_status first and tell the merchant whether it is free or what it costs; a fix that is not free uses the shop's credits. The new image or video replaces the post's media when it is ready.

  • connect_accountFree

    Makes a one-use link that connects a social account to this Xyla shop, or reconnects a broken one. Give the merchant the link to open in their browser; it works once and expires in 10 minutes, and asks for the store's email. To reconnect an account from connection_status, pass its social_media_account_id. Instagram has two ways in: instagram_direct (Instagram Login, the usual choice) and instagram (through a Facebook Page, needed for Stories and product tags). Disconnecting stays on the Xyla website.

  • connection_statusFree

    Shows each social account connected to this Xyla shop: connected, expiring soon, expired, needs reconnecting, restricted or disconnected, and how many upcoming posts a broken account is blocking.

  • get_settingsFree

    Shows the shop's current Xyla settings for one setting group, with the ids change_settings needs and how each field works. Call it without tool to list the setting groups. Read a group before changing it.

  • insightsFree

    Shows how this Xyla shop's published posts performed over the last 7, 14, 30 or 90 days: reach, views, engagement, followers per account, and the top posts. Same data as the Insights page in Xyla.

  • pending_approvalsFree

    Lists the posts in this Xyla shop that wait for the merchant's approval before they are scheduled, 12 per page, with captions and media links. When the shop is still on its first batch, returns that batch as one draft: it is approved as a whole, not post by post.

  • post_fix_statuswrite actionFree

    Reports where a post fix from request_post_fix stands in this Xyla shop: still being checked, free (Xyla found a problem on its side), or how many credits it costs. After confirm_post_fix, reports whether the fix is running, done or failed.

  • preview_statusFree

    Checks a store preview started with preview_store: the brand Xyla found and the sample posts finished so far. done is true once the preview is ready or has stopped. While the preview card is showing it updates itself, so only call this when no card is shown, every few seconds.

  • preview_storeFree

    Shows what Xyla would post for an online store, with no Xyla account. Give it the store's web address (Shopify or WooCommerce). Xyla reads the store's brand (logo, colours, niche) and makes 3 sample social media posts from the store's own product photos, with captions. Returns a preview token at once; the posts take about 3 minutes and the card shows them as they finish. A store previewed in the last 7 days gets its earlier samples back. When no card is shown, call preview_status with the token to follow it. A store that already uses Xyla gets a sign-in link instead.

  • reject_postwrite actionFree

    Rejects one post in this Xyla shop that is waiting for approval, by its ID from pending_approvals. The post is cancelled and will not be published.

  • request_post_fixwrite actionFree

    Starts a fix for one post's image or video in this Xyla shop. Xyla first checks the media for a problem on its side, which makes the fix free; otherwise the fix costs credits. Nothing is changed or charged yet. Then call post_fix_status with the audit_id to learn the cost, tell the merchant, and call confirm_post_fix only once they agree.

  • set_autopilotFree

    Turns Xyla autopilot on or off for this shop. With autopilot on, Xyla makes and schedules posts by itself. mode include (the default) keeps posts already made and adds them to the schedule. mode fresh DELETES every post not yet scheduled, including posts the merchant made by hand, then builds a new schedule: call it first without confirm_delete_count to get the number of posts it deletes, tell the merchant, and only after they agree call again with confirm_delete_count set to that number. Turning autopilot off unschedules upcoming posts and deletes nothing.

  • shop_overviewFree

    Summarises this Xyla shop: its plan, AI credits left, whether autopilot is on, how many posts wait for approval, the next 3 posts due, and any social account that needs fixing.

  • undo_changewrite actionFree

    Puts back the settings a change set replaced, using the undo id from change_settings or change_history. The whole set is undone, or nothing is. It is refused when a setting has changed again since, so a newer choice is never overwritten.

  • upcoming_postsFree

    Lists the posts this Xyla shop will publish, day by day, for up to 7 days from a start date (the shop's today if left out). Each post has its platforms, send time in the shop's time zone, type, caption and media links. Posts waiting for approval are not here: use pending_approvals.

  • whoamiFree

    Shows which Xyla shop this connection acts for and whether it can only read or can also make changes.

Public scan report

scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it

1 high1 low
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1259ms20/20
  • Tool poisoning20 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 5 write-action tools with no auth3/15
  • Maintenanceno repository listed3/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10

Findings (2)

  • highWrite-action tools reachable without authenticationauth.open-write
  • lowNo source repository listedmaint.no-repo
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Xyla AI compares

Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
65/100
higher than 25% of 2,174 E-commerce servers
Tools
20
the typical E-commerce server has 6
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote E-commerce server answers 100%
Response time
486 ms
faster than 32% of 1,527 E-commerce servers

What its tools let an agent do: 12 read · 7 change · 1 send or post

Install Xyla AI in Claude Code, Cursor or VS Code

claude mcp add --transport http xyla https://app.xyla.ai/mcp
Add to Cursor

Xyla AI: common questions

Is Xyla AI MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the Xyla AI safety report
How do I install Xyla AI?
It runs remotely at app.xyla.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Xyla AI need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Xyla AI maintained?
The latest release is v1.0.0.
Is Xyla AI up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Xyla AI?
Servers from other publishers that do the same job: Shopify Multi Store MCP server, DOOMSCROLLR MCP server and Apify MCP server.
How does Xyla AI compare with other E-commerce MCP servers?
safety score 65/100 (higher than 25% of 2,174 E-commerce servers); tools 20 (the typical E-commerce server has 6); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Xyla AI

Same job from other publishers: the closest match first, then the best rated.

  • Shopify Multi Store
    Connect AI agents to multiple Shopify Admin stores for reports, comparisons, and guarded updates.
    A
  • DOOMSCROLLR
    Build owned-audience websites: pages, posts, products, subscribers, ShopMy/Shopify imports.
    A
  • Apify
    Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
    A
  • Mneme Memory
    Cross-session memory for AI coding agents via six tools; local-first SQLite store.
    A
  • Heimdall
    Every App Store Connect + StoreKit 2 endpoint. 929 tools in 13 profiles, narrow to 27.
    B