MCP Functions

Run API Endpoint

Executes an API endpoint as part of an MCP Server Tool function stack

Parameter	Purpose
API Group	The API group that contains the API you’d like to run
Endpoint	The API endpoint to run
Return as	The variable to store the output of the API call

Note

When using the Run API Endpoint function, authentication tokens are not checked.

Run Task

Executes a task as part of an MCP Server Tool function stack

Parameter	Purpose
Task	The task to run

Tasks have no output.

MCP List Tools

Provides a list of available tools and their configurations from an MCP server

Parameter	Purpose
url	The URL to access the MCP server
bearer token	If required, an authentication token to access the server

MCP Call Tool

Executes a tool available on a remote MCP server

Parameter	Purpose
url	The URL to access the MCP server
bearer token	If required, an authentication token to access the server
tool name	The name of the tool to call
args	The data that the tool requires, if any. This should usually be a JSON object.

Ask the User (Elicit)

Asks the MCP client’s user for structured input while a tool, prompt or resource runs, such as a confirmation before a refund or a missing detail. In the function panel, it’s under MCP → Ask the User (Elicit). It’s available only in tool, prompt and resource stacks.

Parameter	Purpose
key	A name for this question, unique within the stack. Used to match the user’s answer and to simulate one in Run & Debug.
message	What to ask the user.
fields	What to ask for: `text`, `email`, `date`, `int`, `decimal`, `bool` or `enum` (an enum may be a list, for multi-select). With no fields, the user can only accept, decline or cancel.
Return as	The user’s answer: `{action, content}`.

action is accept, decline or cancel. content holds the field values, and only when the user accepts.

mcp.elicit {
  key = "confirm_refund"
  message = "Refund order " ~ $input.order_id ~ "?"
  input {
    bool proceed
    text reason? filters=max:200
  }
} as $answer

conditional {
  if ($answer.action != "accept") {
    return {
      value = "Refund cancelled."
    }
  }
}

Everything before an elicit runs again for every answer. The client answers by retrying the whole request, so your stack restarts from the top each time. Put database writes, emails, external API calls and other side effects after the last elicit. The builder flags a write that comes before one.

Always handle cancel. You get {action: "cancel"} immediately, and the stack continues, when:

the client doesn’t support elicitation, which includes every client on a protocol version before 2026-07-28
the stack runs outside an MCP request, such as from an agent or a test
you use Run & Debug without a simulated answer for that key

Fields can’t collect passwords or other sensitive values, and can’t be objects, files, JSON or timestamps. An answer is valid for 10 minutes. In Run & Debug, pick an answer for each elicit under Simulated elicitation.

Report Progress

Sends a progress update to the MCP client during a long-running tool, prompt or resource. In the function panel, it’s under MCP → Report Progress.

Parameter	Purpose
progress	How far along the work is. Must increase with each call; a value that doesn’t is skipped. Required.
total	The value `progress` reaches when the work is done. Optional.
message	A short status message. Optional.

mcp.progress {
  progress = 50
  total = 100
  message = "Imported 50 of 100 rows"
}

It returns nothing and never fails. It does nothing outside an MCP request, or when the client didn’t ask for progress. Run & Debug shows the updates in a Progress table. These functions build the login handoff for an MCP server with hosted OAuth sign-in. Use them in XanoScript.

Function	Purpose
`mcp.oauth.request`	Reads a pending sign-in request: the client’s name, logo and callback host, whether the client is verified, and the server’s name. Show these on your consent screen.
`mcp.oauth.complete`	Records the signed-in user’s decision, `approve` or `deny`, and returns the continue URL to send the browser to.
`mcp.oauth.revoke`	Ends sign-ins on a server for one user, one grant, or everyone.

See Require sign-in (OAuth) for examples and the rules each one enforces.

Build

Test & Deploy

Team Collaboration

Integrations

Security

Tutorials

Enterprise

Agencies

Account and Settings

Legal

Run API Endpoint

Note

Run Task

MCP List Tools

MCP Call Tool

Ask the User (Elicit)

Report Progress

​Run API Endpoint

​Note

​Run Task

​MCP List Tools

​MCP Call Tool

​Ask the User (Elicit)

​Report Progress

​Sign-in functions

Run API Endpoint

Note

Run Task

MCP List Tools

MCP Call Tool

Ask the User (Elicit)

Report Progress

Sign-in functions