MCP tools
MCP tools are the actions an MCP server offers an AI app, each with a name, a description and the arguments it takes, such as read a file, edit a file or take a screenshot.
Updated
On this page
What it is
When an AI app connects to an MCP server, it asks for the server's list of tools. Each tool describes what it does and which arguments it needs, so the AI can decide when to call it, fill in the arguments and read what comes back.
Tools are how an AI does real work outside the chat. A good set is small enough to understand and covers the whole job, and each tool checks what it is given, because the AI may call it in ways nobody planned.
In Xodia
Xodia's MCP server gives your AI tools for each part of a website: reading and editing files, running checks and builds, taking screenshots of the live preview, working on requests and review comments, the site plan, CMS collections, forms, languages, pages and folders, SEO tests, deploys and restore points.
Your AI calls them on the same live preview you see in Xodia, with your own permissions, and every change waits for you to review and push. The MCP reference lists every tool with what it does.
Read more
Related terms
- MCP (Model Context Protocol)MCP, the Model Context Protocol, is an open standard that lets an AI app connect to outside tools and data through one common interface.
- MCP OAuthMCP OAuth is how a remote MCP server signs in the person using an AI app: the app opens the server's sign-in page, you approve access, and the app gets a token it sends with every call.
- AI-built siteAn AI-built site is a website whose code was written mostly by an AI app, such as Claude Code or Cursor, from descriptions rather than by hand.