xTiles
by xTiles
Read and build visual pages, tiles, projects and tasks in an xTiles workspace from an AI agent. Anthropic lists 28 tools; one more appears in xTiles' own agent skill files. Nothing publishes a page to the web. OAuth sign-in with identity-only scopes.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect xTiles via MCP
https://mcp.xtiles.app/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
xTiles Tools & Capabilities (28)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The OAuth scopes are identity claims and grant no boundary.
openid,profile,emailandoffline_accessname no xTiles object and no verb. Consent is all-or-nothing: there is no way to approve reading a workspace without also approving creating pages and deleting tasks. - Anthropic's listing under-lists the connector by at least one write.
xtiles_set_page_layoutappears in four of xTiles' own skill files and has a matching REST route, and it is not in the directory's 28. Assume the real total is 29 or more. - xTiles' three published enumerations do not agree with each other or with Anthropic. The help centre's eight action names share no literal string with the directory's, and one of them,
update-page, has no counterpart in the listing at all. - We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request on 2026-08-23, so no parameter-level detail or
destructiveHintis published here. Parameter facts on this page come from xTiles' public REST specification, which the tool names map onto but which xTiles does not formally declare as the connector's backing API. - Where a deleted task goes is undocumented. xTiles' Trash article lists projects, pages, subpages, subprojects and page groups. Tasks are absent from it, and we found no statement either way. Treat
xtiles_delete_tasksas possibly permanent. - Nothing in the surface can restore anything. No restore, unarchive or trash-listing tool exists. Recovery requires a human in the xTiles app, and xTiles notes Undo stops working after a page reload.
- Capability is plan-gated and unobservable from inside. Editing existing content requires Plus; working in shared or team spaces requires Pro. No tool reports the account's plan, so an agent finds the limit by being refused.
- The plan requirement is documented inconsistently. xTiles' MCP blog post states the integration is "available now for xTiles users on Plus and above". Its help centre states MCP "works on all xTiles plans" with limitations on Free, and its plan comparison lists AI Integrations under Free. The help centre is newer and more specific; we did not resolve the contradiction.
xtiles_get_workflowreturns content the agent is instructed to obey. xTiles' skill files direct the model to fetch a workflow and "follow it exactly". Nothing observed was harmful, but the channel is server-controlled and invisible from the tool name.- Sharing is on the roadmap for the AI integration. xTiles lists "Sharing (coming soon)" and "Edit structure & access rights (coming soon)" under its AI Integrations feature rows. The no-publish finding on this page is current, not permanent.
- The nominated documentation URL is a marketing blog post. It carries no tool names and no parameter detail. The reference documentation is in the help centre, linked below.
- Two of xTiles' own machine-readable pointers are dead. Its authorization server metadata advertises an agent-auth skill at
https://mcp.xtiles.app/auth.md, which returned 404 on 2026-08-23, and itsauth.mdon the main site points athttps://api.xtiles.app/docs, which also 404s. The working OpenAPI document is at a different path, listed below. - We found no published rate limit for the MCP server or the REST API.
Frequently asked questions
No tool in the surface does. xTiles has a real publish feature that makes a project readable by anyone with the link and optionally indexable by search engines, but it lives in the app's Share panel. No tool name carries a publish or share verb, and xTiles' public REST specification contains no publish, share or public endpoint at all. Treat it as outside the connector today.
No. The only delete tool is xtiles_delete_tasks, which deletes tasks. Anthropic's directory entry states plainly that the connector cannot delete projects, pages or workspaces, and xTiles' public REST specification exposes exactly two DELETE routes, both for tasks. Pages and projects deleted in the app go to Trash and can be restored; nothing in the connector reaches Trash.
Anthropic lists 28, and at least 29 exist. xTiles publishes agent skill files that name xtiles_set_page_layout, a tool absent from the directory listing that rearranges the tiles on a page. Its matching REST route is a layout update, so it is a real write. The server requires authentication, so we could not read the live list to settle the true total.
Identity claims only, which grant no boundary. The server's RFC 9728 descriptor advertised openid, profile and email on 2026-08-23, and its authorization server adds offline_access for refresh tokens. None of the four names an xTiles object or verb, so consent cannot separate reading a project from creating one or deleting a task.
No. Nothing in the surface buys, renders or bills anything, and xTiles publishes no per-call rate. What is metered is capability rather than spend: xTiles gates what the connected AI may do by subscription plan, so a call that succeeds on Pro can be refused on Free. No tool reports your plan or remaining allowance.
Any plan connects, but the plans differ in what the agent may then do. xTiles states MCP works on all plans, that Free lets connected AI create pages and tasks, that Plus adds editing and reorganising existing content in personal spaces, and that Pro extends editing to shared and team spaces. The connector's own blog post says Plus and above, which contradicts the help centre.
Yes, indirectly, once you connect a calendar to xTiles. xTiles' public REST specification exposes a calendar-events read whose response carries event titles, locations, descriptions, conference links, the organiser and up to 25 named guests with their email addresses. Those are other people's details arriving in the agent's context from a system outside xTiles.
Not directly, but two indirect paths exist. xTiles' own skill files describe a notification when the agent finishes writing, and xTiles documents that teammates are notified automatically when a task is completed or a project shared. Task tools also accept an assignee email address, so assigning work to a colleague is a write whose effect leaves your own account.
Sources
- xTiles help centre, "How to Connect xTiles to Claude" (retrieved 2026-08-23). Source of the eight kebab-case action names. · retrieved 2026-08-23
- xTiles help centre, "How to Connect xTiles to Other AI Tools" (retrieved 2026-08-23). Source of the all-plans statement and the skill-file instruction. · retrieved 2026-08-23
- xTiles help centre, "xTiles Plan Options" (retrieved 2026-08-23). Source of the per-plan AI Integration gates and both "coming soon" lines. · retrieved 2026-08-23
- xTiles help centre, "Plus Plan Features" (retrieved 2026-08-23) · retrieved 2026-08-23
- xTiles help centre, "How to Restore a Deleted Project or Page" (retrieved 2026-08-23). Source of the Trash, Archive and Space-deletion behaviour. · retrieved 2026-08-23
- xTiles help centre, "Public Project" and "Public Page" — · (retrieved 2026-08-23). Source of the publish and search-indexing behaviour that lives outside the connector. · retrieved 2026-08-23
- xTiles help centre, "How to Share a Project" (retrieved 2026-08-23) · retrieved 2026-08-23
- xTiles Public API OpenAPI 3.0.1 specification (retrieved 2026-08-23). 29 paths, 37 operations, 20 GET, 10 POST, 4 PATCH, 1 PUT, 2 DELETE. Source of the delete count, the access-level enumeration, the calendar-event and user-search response shapes, and the absence of any publish route. · retrieved 2026-08-23
- xTiles agent skills index and the eight skill files (retrieved 2026-08-23). Source of
xtiles_set_page_layoutand the workflow-following instruction. · retrieved 2026-08-23 - xTiles MCP SKILL.md, served at the MCP host (retrieved 2026-08-23). Fourteen category labels, not tool names. · retrieved 2026-08-23
- xTiles MCP server card (retrieved 2026-08-23). Declares
toolsandresourcescapabilities. · retrieved 2026-08-23 - xTiles machine-readable index (retrieved 2026-08-23). Its
robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes, an express opt-in to AI synthesis. · retrieved 2026-08-23 - xTiles blog, "xTiles + Claude MCP Integration: Full Guide" (retrieved 2026-08-23). The URL Anthropic's directory nominates. Marketing rather than reference: 2,030 words, no tool names, and its "full walkthrough" link points back at itself. · retrieved 2026-08-23
- xTiles blog, "A Nonprofit Team's Shared xTiles Workspace" (retrieved 2026-08-23). Source of the automatic teammate notification on task completion and project sharing. · retrieved 2026-08-23
- Live OAuth posture check: anonymous initialize returned HTTP 401 with
WWW-Authenticate: Bearer, RFC 9728 metadata athttps://mcp.xtiles.app/.well-known/oauth-protected-resource, and authorization server metadata athttps://mcp.xtiles.app/.well-known/oauth-authorization-server(2026-08-23). A nonsense path under the same prefix returned a distinct 404, so the descriptor is genuine rather than a catch-all. · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23 · retrieved 2026-08-23
- xTiles support — <mailto:support@xtiles.app> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- xTiles
- Tools
- 28
- Domain
- mcp.xtiles.app
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.