Xyla MCP server

Which servers in the official MCP registry are Xyla's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-22

← Back to Xyla

Whose server it is

Registry nameai.xyla/xylaverified in the MCP registry

The registry name sits under xyla.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-22

Stateanswerschecked 2026-10-22
Tools20
Server calls itselfxyla
Server version1.0.0
Protocol version2025-06-18

On 2026-10-22 the server answered initialize and tools/list without a sign-in. First answer in 564 ms.

Should an agent connect itNot proven either way yet

Whether its tools do the product's job has not been judged yet.
Checked on 3 of the 7 days it takes to judge reliability.

Once connected

reject_post, request_post_fix, confirm_post_fix, set_autopilot change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-22

INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
Answeredmeasuring3 of the 7 daily checks it takes to print a share
Median first answer568 ms
Space in an agent's context≈ 12,019 tokensthe definitions of all its tools (20), which an agent carries on every turn
Tool definitionsA · 100 of 100
Typed results0 of 20 toolsdeclared outputSchema: results come typed, read once

Every tool passes all six checks.

What an agent can do with it

not sure · turn store products into reels and carousels
can do · schedule posts across six social networks automatically
not sure · promote bestsellers and seasonal sales on social

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

Tools that change data, on a server that answers without a sign-in: reject_post, request_post_fix, confirm_post_fix, set_autopilot

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers20 tools · read 2026-10-22

whoami
Shows which Xyla shop this connection acts for and whether it can only read or can also make changes.
shop_overview
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.
upcoming_posts
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…
pending_approvals
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…
insights
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.
connection_status
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_settings
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.
change_settings
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…
undo_change
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.
change_history
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.
connect_account
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…
approve_posts
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…
reject_post
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.
approve_first_batch
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…
request_post_fix
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…
post_fix_status
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.
confirm_post_fix
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…
set_autopilot
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…
preview_store
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…
preview_status
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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "xyla": {
      "type": "http",
      "url": "https://app.xyla.ai/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

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

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://app.xyla.ai/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.