xorventa

Connect your AI assistant to Xorventa to understand account status and work with Assist, SEO, Social, and Persona.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Xorventa Status: The account's products, unfinished setup tasks, what is waiting on the owner's decision, and links to the account pages. follow_up names the waiting items this connection can work thr
  • Xora Ask: Ask Xora, Xorventa's account assistant, a question about this account or about Xorventa. The answer is grounded in the help library, the account's Business Facts and counts of its open work.
  • Xora Capabilities: Every action Xora can take for this account, and every action that stays with the owner, with its effect, required scopes, the tool that runs it, whether it runs directly or as a pr

What data it sees

Do you need an account

No: the server works without sign-in

Connect your AI assistant to Xorventa to understand account status and work with Assist, SEO, Social, and Persona. It can prepare, manage, and carry out permitted account actions within the permissions and approval controls you select. Billing, security settings, purchases, and provider sign-ins remain with you.

How to connect

How to connect xorventa to Claude

The server address to paste into Claude settings:

https://xorventa--ron-57t2.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect xorventa to ChatGPT

The server address to paste into ChatGPT settings:

https://xorventa--ron-57t2.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect xorventa to Cursor

The server address to paste into Cursor settings:

https://xorventa--ron-57t2.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (14)

Raw names from tools/list. Only developers need these.

xorventa_statusThe account's products, unfinished setup tasks, what is waiting on the owner's decision, and links to the account pages. follow_up names the waiting items this connection can work through in the conversation, each with a question offering to go through it and the xora_read action that lists it. Reads only.
xora_askAsk Xora, Xorventa's account assistant, a question about this account or about Xorventa. The answer is grounded in the help library, the account's Business Facts and counts of its open work. When a registry action would do what was asked, its name is listed in suggested_actions. This tool answers questions; it does not change business or account settings. The question and answer are kept as this connection's thread; pass back workflow_id to continue it.
xora_capabilitiesEvery action Xora can take for this account, and every action that stays with the owner, with its effect, required scopes, the tool that runs it, whether it runs directly or as a proposal for this connection, and whether this connection can use it now (and why not). Paginated.
xora_action_detailsOne action's input schema (the arguments that action accepts), its effect, the tool that runs it, its confirmation rule, its mode for this connection and its owner page. Metadata only; it runs nothing.
xora_readRuns one read-only action from Xorventa's own account API, by name with its arguments, and returns its data: lists, look-ups and summaries of this account's chat windows, Business Facts, settings, drafts, posts, SEO audits and activity. It refuses any action that changes something. A repeated call with the same client_request_id returns the recorded action and does not run it again.
xora_change_settingsRuns one settings action from Xorventa's own account API, by name with its arguments: chat window look and wording, Business Facts, knowledge sources, assistant, phone, mailbox and SEO settings, drafts that are not published, and similar changes inside this account. It runs when this connection holds xorventa:manage and the owner allows Xora to change settings; the few settings that always ask first also need xorventa:execute, or become a proposal the owner confirms with xorventa:prepare. It refuses reads, publishing, sending and deleting. The social media actions — upload_social_media, add_campaign_draft, create_social_post and edit_social_draft — also take an image or video in the same call: image_url (a public https address the server fetches) or file_base64 with mime_type (the file itself), checked like any upload. A repeated call with the same client_request_id returns the recorded action and does not run it again.
xora_publish_or_sendRuns one publishing or sending action from Xorventa's own account API, by name with its arguments: social posts and replies, email replies, appointment changes that notify the person who booked, and website changes that go live. With xorventa:execute it runs within the owner's switches; with xorventa:prepare and without execute it becomes a proposal the owner confirms at owner_confirmation_url. It refuses every other kind of action. The social media actions — upload_social_media, add_campaign_draft, create_social_post and edit_social_draft — also take an image or video in the same call: image_url (a public https address the server fetches) or file_base64 with mime_type (the file itself), checked like any upload. A repeated call with the same client_request_id returns the recorded action and does not run it again.
xora_deleteRuns one delete action from Xorventa's own account API, by name with its arguments: removing drafts, records, knowledge sources, reports, connections and published posts. With xorventa:execute it runs within the owner's switches; with xorventa:prepare and without execute it becomes a proposal the owner confirms at owner_confirmation_url. It refuses every other kind of action. A repeated call with the same client_request_id returns the recorded action and does not run it again.
xora_action_statusThe current state of an action this connection requested. Reads only; it never runs, retries or changes the action.
xora_cancel_actionCancel a proposed or queued action this connection requested, while nothing has been sent to a provider yet. Needs xorventa:prepare or xorventa:execute. Cancelling an action that is already cancelled changes nothing.
xora_upload_prepareReserves a one-time upload for an action that takes a file, after checking the declared type, size and SHA-256 against that action's limits. Returns upload_url, which accepts one HTTPS PUT of exactly the declared bytes with required_headers and expires after ten minutes; the URL carries its own single-use credential, so no Authorization header is needed. owner_upload_url is a portal page where the owner can choose the file instead. The server never reads a local path. An image for a social post can instead be given to the action itself, by address or as base64.
xora_upload_statusWhether a prepared upload arrived and passed its size, hash and type checks. When the state is ready, upload_reference is the value an upload-taking action accepts as its upload_id argument.
xora_upload_from_urlFetches a file from a public https address and stages it as a one-time upload for an action that takes a file, after the same type and size checks a direct upload meets. Private, loopback and link-local addresses, non-https addresses and every redirect to one are refused. When the state is ready, upload_reference is the value the upload action accepts as its upload_id argument; it expires after ten minutes and is used once.
xora_upload_requestShows the owner a file picker in the conversation for an action that takes a file. The owner chooses the file there; it is checked against the action's type and size limits and staged as a one-time upload, and its upload_reference is then posted into the conversation. This call itself uploads and changes nothing.