Shop MCP

Connect a module

Neto by Maropost

Neto doesn't have a public OAuth flow, so the connect step is two short forms — generate an API key inside Neto admin, then paste it here.

1. Generate an API key in Neto admin

Log into your Neto by Maropost control panel, then go to Settings & tools → Staff users. Click Add new staff user and complete the required fields:

  • Username
  • First name
  • Last name
  • Email address — this cannot be the same as another staff user
  • Password

Click Regenerate to create an API key for this user, then set the User Permission Group dropdown to API User.

You can also create a custom permission group from Add or Edit User Permission Groups. We recommend cloning the API user group, then adding or removing permissions for the access ShopMCP should have.

Click Save, then copy the username and API key for step 2.

2. Choose the Neto permissions

Start from the API User permission group, then confirm it includes the resources ShopMCP should be able to access:

  • Order: Get, Add, Update
  • Customer: Get, Add, Update
  • Item / Product: Get, Add, Update
  • Inventory: Get, Update
  • Voucher, RMA, Supplier, Category, Content: Get (add write scopes only if you want the assistant to make changes)

3. Paste the credentials into ShopMCP

Open Settings → Integrations and click Connect on the Neto card. Fill in:

  • Store URL — e.g. https://your-store.neto.com.au
  • API username — optional; use the username from the staff user if your Neto API user has one
  • API key — the key generated for the staff user

4. Check the connection

Submit the form. ShopMCP verifies the store domain and API key by making a read-only Neto API call, then marks the connection as Connected.

If you manage multiple Neto stores, repeat the same flow for each store and give each connection a clear nickname.

Troubleshooting

  • "Invalid API credentials" — Neto returns this when the username and key don't match, when the user is disabled, or when the store URL has a typo. Re-check all three.
  • Tool returns "permission denied" — update the permissions for the user group assigned to the API user, then retry the tool. You do not need to reconnect the store.