Connect a service
Give MaShop access to the account and tools a task actually needs.
Choose the right connection
A native integration and an MCP server are different connection paths. GitHub, Supabase and Netlify have project integrations. MCP connections expose the tools provided by a compatible server. A service can appear in a recommendation before you have connected it.
Ask the assistant which tools are connected for the task. It should use the current connection status and available tools rather than assume access from a previous message.
Authorize deliberately
- Open the proposed connection or find the service in connected tools.
- Check the provider and sign in to the account you intend to use.
- Review the requested permissions and the resources you are sharing.
- Complete the connection and confirm its status.
- Try a small read or draft task before allowing broader actions.
Return to the task after connecting
When the assistant proposes a connection for a task, complete that provider’s authorization and return to the conversation that requested it. MaShop checks that the expected service is connected before continuing the pending request. Signing in to a provider is not enough if the connection still fails verification.
If you return after a long break or the conversation does not resume, reopen that same conversation and ask to continue the task. Review the next response and any approval request. The connection supplies access; it does not prove that the requested work has already been completed.
When a connection is missing
If a service is disconnected, follow its connection flow. If verification is unavailable, retry the check; that is different from a confirmed disconnection. A connected account may still lack access to a specific workspace, repository or document.
Never put passwords or private API keys into a public web search or an ordinary chat request. Use the provider’s connection flow or the secure credential field offered for that connection.