Tapcart

com.tapcartPublished by tapcart.comOfficial publisherv1.5.0Updated Oct 24, 2026

Tapcart analytics, App Studio blocks and components, and push campaigns for your mobile app.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Remote Tapcart MCP server that lets an assistant work with mobile app analytics, App Studio blocks and components, and push campaigns.

What you can do
  • Read Tapcart app analytics for a mobile storefront app
  • Work with App Studio blocks and components
  • Manage push notification campaigns for the app
  • Tool-level detail is not published; the manifest lists no individual tools, so exact capabilities must be confirmed after connecting.
When to use it
Useful when you manage a Tapcart mobile app and want an assistant to look at app analytics, adjust App Studio blocks and components, or handle push campaigns without switching between dashboards.
Requirements
A remote MCP endpoint at mcp.tapcart.com over streamable HTTP; no local package or environment variables are needed. Authentication is OAuth and required, so you need a Tapcart account with access to the relevant app.
Before you install
OAuth grants the assistant access to your Tapcart account. The server covers App Studio blocks and components and push campaigns, which can change your live app and send messages to customers; review write actions before approving them. No tool list is published, so scope cannot be verified in advance.

Installation

In SourceWeft

  1. Open Tapcart 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.tapcart%2Fmcp/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": {
    "tapcart": {
      "type": "http",
      "url": "https://mcp.tapcart.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

2
  1. v1.5.0LatestSep 29, 2026
  2. v1.4.1Sep 16, 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.