Laplace Analytics

io.github.laplacetecPublished by GitHub account laplacetecv1.0.0Updated Nov 4, 2026

E-commerce P&L for brands: orders, ad spend and COGS across Korean & global channels.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for Laplace Analytics that gives an assistant access to e-commerce profit-and-loss data: orders, ad spend and COGS across Korean and…

What you can do
  • No tool list is published, so capabilities are inferred from the description.
  • The server connects an assistant to Laplace's e-commerce P&L analytics for brands.
  • It covers order data, advertising spend and cost of goods sold.
  • Data spans Korean and global sales channels.
When to use it
Useful when you want an assistant to look at brand e-commerce profitability — orders, ad spend and COGS — across Korean and global channels without leaving the chat.
Requirements
A remote streamable HTTP endpoint at the provider's gateway; no local package or runtime. Authentication is OAuth and required, sent as an Authorization bearer header carrying a Laplace API key. The key is issued in Laplace under project settings, API, MCP key.
Before you install
The Authorization header carries a secret API key; keep it out of logs and shared transcripts. The key is scoped to a Laplace project, so the assistant may see that project's order, ad spend and cost data. No tool list is published, so what the assistant can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Laplace Analytics 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/io.github.laplacetec%2Fecommerce-analytics/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": {
    "laplace-analytics": {
      "type": "http",
      "url": "https://gateway.laplacetec.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.0LatestNov 4, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.