Use connected MCP tools
Connect a compatible MCP server and use its actual tool catalog.
What MCP adds
Model Context Protocol lets a compatible server expose tools to an assistant. The available actions depend on that server, its current tool definitions and the account you authorized. MaShop does not gain every feature of a service simply because its MCP server is connected.
Check the connection details for the tools returned by the server and the permissions associated with them. Access to a local desktop or browser requires the appropriate tool and connection; a cloud service connection alone cannot control your computer.
Try one concrete action
- Connect the server using the supported connection flow.
- Review the current tool catalog and choose a small task you can verify.
- Ask the assistant to discover the appropriate capability and use its exact input fields.
- Approve the action if required and inspect the returned result.
- Check the destination service for actions that change external data.
Handle a missing tool
If a tool is absent, refresh or reconnect the server and check its documentation. The assistant should not invent a tool name or claim an action succeeded without a result. Provider access, authentication and tool permissions can fail independently.
Code and Agents can use connected tools when the task, mode and permissions allow it. Read-only Code modes do not gain write access through MCP.