Etalasse

com.etalassePublished by etalasse.comOfficial publisherv1.0.1Updated Nov 5, 2026

Etalasse for Indonesian small shops: manage orders, products, stock, customers and sales reports

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for Etalasse, an Indonesian small-shop platform, letting an assistant manage orders, products, stock, customers and sales reports.

What you can do
  • Manage orders, including creating and updating shop orders
  • Maintain the product catalog and stock levels
  • Handle customer records
  • Produce sales reports for the shop
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful for Indonesian small-shop owners or their staff who already run their store on Etalasse and want an assistant to handle day-to-day order, product, stock and customer work and pull sales reports without switching apps.
Requirements
A remote MCP endpoint at mcp.etalasse.com over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared. An Etalasse account is implied by the OAuth flow.
Before you install
The assistant can change shop data such as orders, products, stock and customer records, so review write actions before approving them. OAuth grants access to your Etalasse account; check the scopes requested. Order and customer data is sent to the remote service.

Installation

In SourceWeft

  1. Open Etalasse in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.etalasse%2Fetalasse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "etalasse": {
      "type": "http",
      "url": "https://mcp.etalasse.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestNov 5, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.