Ascendkit

dev.ascendkitPublished by ascendkit.devv0.3.22Updated Oct 24, 2026

Auth, email, journeys, surveys, webhooks, and analytics for SaaS in one project, one API key.

VerifiedSTDIODesktop onlyCommunication & CollaborationData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Ascendkit gives an assistant access to a SaaS project's auth, email, journeys, surveys, webhooks, and analytics through one API key.

What you can do
Ascendkit is a local MCP server for a SaaS platform that bundles authentication, email, user journeys, surveys, webhooks, and analytics into a single project. It runs over stdio and is started with npx from the @ascendkit/cli package. The manifest does not list individual tools, so the exact operations exposed to the assistant are not documented here.
When to use it
Consider it when you already use Ascendkit for a SaaS product and want an assistant to work with that project's auth, messaging, journey, survey, webhook, or analytics data. It is not useful without an existing Ascendkit project.
Requirements
A local runtime with Node.js so npx can run the @ascendkit/cli package over stdio. The manifest declares no authentication, environment variables, or headers, but the description refers to an API key, so credentials are likely needed and are not documented here. Desktop only.
Before you install
The description mentions an API key, but the manifest declares no authentication or environment variables, so how the key is supplied is unclear. The server appears to cover auth, email, journeys, surveys, webhooks, and analytics, which can involve sending messages, changing user data, and reading customer analytics. Review what it can write or send before connecting it to a production project.

Installation

In SourceWeft

  1. Open Ascendkit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.22LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.