The words used in MaShop
Understand projects, agents, runs, previews and connected tools.
Project and Code
A project is the workspace context for your software and agent tasks. A software project’s repository contains its source files. Code is the conversation area for working on that software; Agents is for operational tasks and configured agents. A Code mode determines whether the assistant investigates, plans or makes changes; the selected model is the AI used for the task.
A version identifies a recorded state of the application code. Restoring a version changes code; it does not automatically restore a database. A preview runs the application for inspection, while publishing makes it available through a chosen hosting service.
Agent and execution
An agent combines instructions and selected capabilities for a job. An execution or run is one attempt to perform a task. A routine configures repeatable work. An approval is a decision requested before an action; a pending approval means that action has not yet been performed.
Skills provide task-specific guidance. Memory stores information intended to help future work. Neither is proof that an execution succeeded: check its history and the output in the destination service.
Connections and MCP
A connection authorizes access to a service. Native integrations and MCP connections have different setup flows and available capabilities. MCP exposes named tools that the assistant can call under the granted permissions.
Connecting another service’s MCP tools inside MaShop is different from connecting an external assistant to the MaShop MCP server. The first brings a service into your MaShop task; the second exposes MaShop tools to the authorized external client.