Xenition MCP Server

Use this when the user wants to change an app they built in Xenition — add a feature, change a screen, restyle it, fix something — described in plain words. Rewrites the affected files and saves a new version of the app. If the app is already live, the change is not published until deploy_app is called again. The app must have finished building (check app_status).

Use this when the user wants one of their existing Xenition items changed in place — rewrite, shorten, expand, change tone, fix grammar or translate. Saves a new version and returns it. Best for documents and notes. To only suggest changes without editing, use review_artifact.

Use this when the user wants an existing image changed: edit it by instruction, upscale, remove the background, enhance, erase something, restyle, colorize, restore, expand the canvas, or make a variation. Saves the result as a new image in their Xenition library; the original is kept.

Use this when the user wants an existing video improved: burned-in captions, enhanced picture and sound, the background removed, or silences cut out (jump cut). Starts the edit and returns an id right away; video_status reports when the new video is ready. The original is kept; the result is saved to their Xenition library.

Use this when the user asks how their app build or deploy is going, or whether it is live. Returns the build phase and file count while building, the finished app when built, and the live URLs once deployed. Needs the id returned by build_app.

Use this when the user wants to open Xenition's no-code app builder themselves, pre-filled with their idea, to shape the app by hand. Returns the link. To have the app built for them from the conversation, use build_app instead.

Use this when the user wants a ready-made app for a kind of business — a dance school, restaurant, clinic, store, CRM — to start from. Searches Xenition's ~200 full-stack templates (web app, API and database, each with a live demo) and returns matches with their demo links. To start the user's own copy, pass a template id to build_app_from_template.

Use this to check a background agent run started by run_agent, when the user asks whether it is done or what it found. Returns its status, the final answer when finished, and a link to view it in Xenition. An unknown id is reported as not found, not as still working.

Use this when the user wants one of their Xenition agents to work on a task in the background (research can take a few minutes). Returns a run id right away; progress, the final result and a link appear as it finishes, and check_agent_run reports on it. Call list_agents first if you do not know the agent.

Use this when the user wants something done for them on a schedule — every day, on certain weekdays, or every few hours — e.g. 'every Monday at 9, summarise my sales sheet'. Creates a Xenition automation that runs on its own at those times, even when nobody is in this chat. Results appear in Xenition, and anything that would act in a connected app waits for the user's approval. Do not use for a one-off task now (use run_agent).

Use this when the user wants to pause one of their automations or turn a paused one back on. Needs the automation's id from list_automations.

Use this when the user wants a working web (or mobile) app built for them — e.g. a booking site, a CRM, an internal tool. Generates the full app (screens, API and database) in their Xenition workspace. Takes a few minutes: returns the app's id right away; check progress with app_status, then publish it with deploy_app. The user can also open the link to watch it build. To only open the builder with an idea, use create_app.

Use this when the user picks one of Xenition's app templates (from find_app_templates) and wants their own working copy. Copies the full template into their Xenition workspace and publishes it to a live URL; publishing takes a few minutes and app_status reports the links. To generate a new app from a description instead, use build_app.

Look up real, current information from open public sources: jobs, hospitals, clinics, pharmacies, banks, schools, universities, companies, government offices. Reads the sources live at the moment of asking rather than from a stored copy, so it is current. Place types (hospitals, schools, banks, pharmacies, clinics, government offices) REQUIRE `near`. Always tell the user which sources answered and when. Each result may carry `phone`, `website`, `address`, `lat`/`lng` and a `detail` map (salary, cuisine, opening hours). QUOTE THEM — a phone number or an apply link that came back and was not shown is the answer the user asked for, thrown away. Do NOT web-search for a detail that is already in the result. Where a field is genuinely absent, say so for that entry rather than searching again.

Say where a Discover answer comes from: which public sources would be asked for a data type, and under what licence. Use when the user asks how we know something, or whether the information can be trusted.

Use this when the user asks for a written piece — a report, article, letter, brief, essay or plan — to be created in their Xenition workspace. Returns the document and a link to open and edit it. For slides use create_slides; for a fill-in template such as an invoice or resume, use find_forms.

Answer a question about, or find a specific thing inside, ONE of the user's Xenition documents (grounded only in that document). Use to look something up in a specific file the user names.

Use this when the user wants to record an invoice, bill or receipt in their Xenition ledger — vendor, amount, due date, optionally already paid. Returns the ledger's invoices. Do not use to pay, send or email an invoice; Xenition has no payment or messaging channel.

List the user's own Xenition ledger invoices with paid/unpaid status. Optionally filter to a vendor or only unpaid ones. Use ONLY when the user is asking to see or total invoices already recorded in their Xenition ledger — e.g. 'what invoices are unpaid', 'how much do I owe vendor X'. Do NOT use it to send, text, email, or deliver an invoice to anyone (Xenition cannot send communications), and do NOT use it to look up invoices that are not in the user's Xenition ledger.

Check the status of a 3D model started by create_3d_model. Returns whether it is still generating, completed (with the model), or failed. The inline preview calls this automatically; you can also call it if the user asks whether their model is ready.

Generate a 3D model (glTF/GLB) in the user's Xenition workspace from a text prompt or a reference image. Starts generation and returns immediately; an interactive inline preview fills in as it renders (~30-60s, longer for 'realistic'), plus a link to open, edit, and export it (GLB/STL/OBJ) in Xenition. Use when the user asks for a 3D model, mesh, or asset. Best for a single object.

Use this when the user wants a new spreadsheet or data table — a budget, tracker, schedule or list with formulas where useful — created in their Xenition workspace. Returns the sheet and a link to open it. To add rows to an existing sheet, use add_rows.

Answer a question or compute a result over one of the user's Xenition spreadsheets — sums, trends, lookups, or 'what does this data say'. Returns the answer and, when relevant, a suggested formula.

Use this when the user wants a short AI video clip made from a description. Starts the video and returns its id right away; generating takes a few minutes, and video_status reports when it is ready with the file link. The clip is saved to their Xenition library.

Use this when the user asks whether a video from create_video or edit_video is ready. Returns generating, the finished file link, or why it failed. Needs the id from create_video or edit_video.

The user's day at a glance from Xenition: today's calendar events, tasks due today or overdue, and anything awaiting approval. Use ONLY when the user explicitly asks about their day, schedule, or agenda — e.g. 'what does my day look like', 'what's on my plate today'. Do NOT use it as a fallback for vague requests like 'just handle it' or 'take care of the rest' — for those, ask the user what they mean instead.

Use this when the user asks what Xenition agents (named AI workers) they have, or before run_agent to pick the right one. Returns each agent with its name and what it does.

Approve a pending action awaiting the user's decision (from list_pending_approvals).

Use this when the user wants to read or open one specific item — a document, deck, spreadsheet, note or other artifact — and you have its id (from search_artifacts or an earlier result). Returns its content. Very long items come back cut to the first part; use query_document or summarize_artifact to work with the whole thing. Do not use to find items; use search_artifacts.

Search the signed-in user's own Xenition artifacts (documents, slides, sheets, media, code) and return matches. Use ONLY when the user is explicitly looking for their existing content. Do NOT call it to check whether an unsupported or out-of-scope action is possible, to find another person's content, or as a first step toward a bulk/irreversible action — confirm or decline those first.

Use this when the user asks a question about their own Xenition content — their documents, notes, files or saved knowledge. Answers only from that content, with sources cited. Do not use for general knowledge or anything outside their workspace.

Use this when the user asks what automations they have, when they run, or whether one is paused. Returns each with its schedule, on/off state, last run and id.

Use this when the user wants a new Kanban board — columns and task cards — built from a brief, e.g. 'a board to plan our product launch'. Returns the board and a link to manage it. To add a single task to an existing board, use add_task.

Use this when the user says a specific task is done and names it. Moves it to the board's done column and returns the updated board. If several tasks match or none is named, ask which one first.

Use this when the user asks which third-party apps (Gmail, Slack, Notion, …) are connected to their Xenition account. Read-only; it cannot connect new apps or act in them.

Deny a pending action awaiting the user's decision (from list_pending_approvals).

Use this when the user wants their built Xenition app published to a live URL. Deploys the app from build_app (it must have finished building — check app_status) and returns right away; deploying takes a few minutes, and app_status reports the live URLs. Publishing makes the app reachable by anyone with the link, so only do it when the user asks.

Use this when the user wants a diagram — flowchart, sequence, architecture, ER or mind map — created from a description. Returns the diagram and a link to open and edit it in Xenition.

Use this when the user wants to put a new event on their Xenition calendar (a meeting, call, deadline or reminder) with a start time. Returns the upcoming schedule. Do not use to change an existing event (use reschedule_event), and it cannot send invitations to anyone.

Use this when the user asks what is on their Xenition calendar for a range — today, this week, a date, or upcoming. Returns the events with times and links. For a combined view of today's events, tasks and approvals, use my_agenda.

Use this when the user wants one of their Xenition documents as a PDF file — to download, print or attach. Returns a link to the PDF. Works for documents (reports, letters, articles); for slides, sheets or notes, open them in Xenition to export.

Use this when the user wants a specific kind of information pulled out of one of their Xenition documents as a list — names, dates, figures, action items, tasks. Answers only from that document. To ask a free question about it, use query_document.

Use this when the user wants to see what people submitted to a shareable form they made with create_shared_form — sign-ups, survey answers, RSVPs, feedback. Takes the form's link. Returns the responses, newest first, each with its answers and time. Only works for forms the user owns.

Search Xenition's library of ready-made forms (invoice, resume, proposal, meeting agenda, job description, and ~200 more). Returns matching forms with their fields, shown as a fillable form the user can complete right here to generate a document. Use when the user wants to create a specific kind of document or fill out a form.

Use this when the user wants an image made from a description — an illustration, photo-style picture, logo idea or background. Saves it to their Xenition library and returns the image link. To change an existing image, use edit_image.

Use this when the user wants to bring a file's content into their Xenition workspace — e.g. they attached or pasted a document and want it saved. Pass UTF-8 text in textContent, or other content base64-encoded in base64Content, with contentMimeType. Saves it as an editable document that summarize_artifact, query_document, ask_workspace and edit_artifact can work on. Supports text, Markdown, CSV, JSON, HTML and PDF. To bring in a page from the web instead, use add_to_knowledge with its URL.

Use this when the user wants Xenition to remember material so it can answer from it later — pasted notes, a policy, an article, or a public web page link (e.g. 'save this pricing page so I can ask about it'). Saves it privately to their knowledge; ask_workspace and their agents then answer from it with sources. Text or a web page only; PDFs and Word files are uploaded in Xenition. Do not use to create a document (use the document tools) or to answer a question now (use ask_workspace).

Mark a specific invoice in the user's own Xenition ledger as paid. This changes financial records, so it is a confirmed, two-step action: first call it WITHOUT `confirmed` to preview exactly which invoice would change, relay that to the user, and only call again with `confirmed:true` after they explicitly agree. When the user asks to mark ALL/EVERY/multiple unpaid invoices paid, list the affected invoices and get the user's confirmation before marking any. Returns the ledger's invoices.

Use this when the user is looking for a ready-made digital product to buy or download — a template, e-book, design pack or app — from creators on the Xenition Marketplace. Returns matching listings with price and a link to each listing page. Do not use for the user's own files (search_artifacts) or for Xenition's free built-in templates (find_app_templates, find_forms).

Turn a meeting or call transcript into clean notes, decisions, and action items (with owners and due dates), saved to the user's Xenition workspace. Use when the user pastes a transcript or asks to summarize a call into notes and tasks.

Use this when the user asks about one specific Xenition mission (a long-running multi-agent job) by id. Returns its status and results. To see all missions, use list_missions.

Use this when the user asks what missions (long-running multi-agent jobs) they have in Xenition and how they are going. Returns each with its status and id for get_mission.

Use this when the user wants a specific task moved to another column on its board (e.g. to 'In progress'). Returns the updated board. Ask which task if the name is ambiguous.

Use this when the user wants to save something as a note in Xenition — an idea, a snippet, meeting jottings — with optional tags and notebook. Returns the saved note. For a long structured piece, use create_document instead.

Use this when the user is looking for one of their Xenition notes by words, tag or notebook. Returns matching notes with links. To search all their content (documents, decks, sheets), use search_artifacts.

List actions the user's assistant/agents are waiting on the user to approve (the 7A approval gate). Each item's id can be passed to approve_action or deny_action.

Publish an existing Xenition artifact as a public, read-only link anyone can open without signing in. Returns the shareable URL. Use when the user wants to share a document, deck, sheet, board, or other artifact.

Use this when the user wants one of their Xenition items turned into a different format: a task board, calendar events, a form or a slide deck — e.g. meeting notes into a board of action items, or a document into a deck. Creates a new item and returns it; the original is unchanged.

Use this when the user wants to move an existing Xenition calendar event to a new time. Returns the upcoming schedule. Ask which event if several share the name; to add a new event use add_event.

Review one of the user's Xenition documents and return constructive comments — each tied to a quoted passage — on clarity, structure, and correctness. Non-destructive: it suggests, it doesn't edit (use edit_artifact to apply changes).

Use this when the user wants to append rows of data to one of their existing Xenition spreadsheets. Returns the updated sheet. Do not use to create a new spreadsheet (use create_spreadsheet) or to answer questions about the data (use query_spreadsheet).

Create a fillable form with a public link anyone can use to submit responses (like a Google Form) — for surveys, sign-ups, feedback, RSVPs. Returns the shareable link; responses collect in Xenition. Use when the user wants to gather input from other people.

Create a polished, designed presentation deck in the user's Xenition workspace from a brief or topic. Returns the deck's slides (shown as an inline preview) plus a link to open and edit it in Xenition. Use when the user asks for slides, a deck, a presentation, or a pitch deck.

Use this when the user wants text read aloud as an audio file — a voiceover, narration or spoken message. Returns an MP3 link and saves it to their Xenition library.

Submit a filled Xenition form (from find_forms) to generate its document. Saves the result to the user's workspace and returns it. Usually called by the form widget when the user clicks submit.

Use this when the user wants a summary of one of their Xenition documents, notes or research — a TL;DR, key points, action items or a fuller summary. Works on long documents in full. Do not use to change the document (use edit_artifact).

Use this when the user wants to add a task or card to one of their Xenition boards, optionally in a named column with a due date. Returns the updated board. To create a whole new board, use create_board.

Use this when the user asks what tasks are open on their Xenition boards — optionally one board, only theirs, or only overdue ones. Returns each task with its board, column, due date and link.

Use this when the user wants an answer from one of Xenition's built-in tools — a unit conversion (length, weight, volume, area, speed, data size, energy, pressure, and more), a loan payment, BMI, tip split, discount, sales tax, percentage, temperature or age. Returns the computed answer. For interactive tools (timers, QR codes, live weather) it returns what the tool needs and a link that opens it ready to use. Call find_tools first if you do not know the tool id. Do not use for general maths you can do yourself, or for anything that is not a built-in tool.

Use this when the user asks for a calculator, converter or generator (loan, currency, BMI, age, QR code and ~200 more) and you need the tool's id. Returns matching tools with links. To get an answer from the tool, pass its id to run_tool.

Use this when the user wants the words from an audio or video recording — a meeting, lecture, interview or voice memo — and gives a link to the file (https, up to 25 MB). Returns the transcript and saves it as a document in their Xenition workspace. To turn it into notes and action items, pass the text to meeting_notes.