Skip to main content
Glama
SuprSend MCP Server - deprecated

SuprSend MCP Server - deprecated

by suprsend

SuprSend CLI

cli MCP server

SuprSend CLI는 Go로 작성된 SuprSend API와 상호 작용하기 위한 명령줄 인터페이스 도구입니다.

설치

npm / npx

설치 없이 실행:

npx suprsend --help

또는 전역 설치:

npm i -g suprsend
suprsend --help

macOS, Linux 및 Windows(x64 및 arm64)에서 작동합니다. Node.js ≥ 18(npx용)이 필요합니다.

Homebrew

Homebrew를 사용하여 SuprSend CLI를 설치할 수 있습니다:

brew tap suprsend/tap
brew install --cask suprsend

바이너리 릴리스

다양한 플랫폼용으로 사전 컴파일된 바이너리는 릴리스 페이지에서 확인할 수 있습니다.

소스에서 빌드하기

소스에서 SuprSend CLI를 빌드하려면 다음 단계를 따르세요:

  1. 시스템에 Go가 설치되어 있는지 확인합니다(버전 1.20 이상).

  2. 저장소를 복제합니다:

git clone https://github.com/suprsend/cli.git
cd cli/cmd/suprsend
  1. 바이너리를 빌드합니다:

go build -o suprsend
  1. 바이너리가 현재 디렉토리에 생성됩니다. 쉽게 액세스할 수 있도록 PATH의 위치로 이동할 수 있습니다:

sudo mv suprsend /usr/local/bin/

이제 터미널 어디에서나 suprsend 명령을 사용할 수 있습니다.

Related MCP server: Courier MCP Server

사용법

설치 후 suprsend 명령을 실행하여 CLI를 사용할 수 있습니다. 예:

suprsend --help

문서

여기의 문서를 참조하거나, cobra로 생성된 문서를 보려면 여기를 확인하세요.

기여

기여를 환영합니다! 자유롭게 Pull Request를 제출해 주세요.

로컬에서 빌드 아티팩트 생성

make build는 내장된 type-morph Deno 바이너리를 컴파일하고(Deno 필요), docs/에 CLI 문서와 skills/에 AI 기술을 생성합니다.

make build

main 브랜치에 대한 PR 시 CI 체크를 통해 docs/와 skills/가 최신 상태인지 확인합니다. PR을 열기 전에 make build를 실행하고 결과물을 커밋하세요.

로컬 빌드 아티팩트 제거

make clean

라이선스

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여됩니다. 자세한 내용은 LICENSE 파일을 참조하세요.

Available Tools

22 tools
add_suprsend_object_subscriptionsA
Destructive

Subscribe one or more users or other objects TO this object. The recipient list can mix users and objects in a single call.

Recipients: users by distinct_id, objects by object_type + id. Each entry's shape follows the SuprSend recipient format. Optional properties attach metadata to each subscription (role, joined_at, etc.).

When NOT to use:

  • To remove subscribers — there is no remove tool; use the SuprSend API directly.

  • For mailing-list / segment membership — those are managed via the Lists API.

  • For preference changes on existing subscribers — use the per-user / per-object preference tools.

Side effects: each successful subscription is a separate row. Calling this twice with the same recipient creates duplicate-looking entries; check existing state with get_suprsend_object_subscriptions first if duplicates would be a problem.

Returns: the created subscription records on success.

Inputs: object_id (required), recipients (required), object_type (required), workspace, +1 more.

fetch_suprsend_documentationA
Read-onlyDestructiveIdempotent

Fetch the full content of a SuprSend documentation page when a snippet from search_suprsend_documentation is insufficient.

When to use: after search_suprsend_documentation, when the snippet excerpt doesn't fully answer and you need surrounding context, code examples, or full reference material.

When NOT to use: to discover documentation — search first; don't construct uris yourself.

Returns: the page contents as markdown.

Inputs: uri (required).

get_suprsend_objectA
Read-onlyDestructiveIdempotent

Get a SuprSend object's full state by object_type + object_id. Objects are non-user entities — organizations, projects, vehicles, devices — namespaced by object_type.

When to use: the user references an object by id and you need its stored properties or channel identifiers.

When NOT to use:

  • For users — use get_suprsend_user.

  • For preferences only — use get_suprsend_object_preferences.

  • For followers / members — use get_suprsend_object_subscriptions.

Returns: YAML mirroring get_suprsend_user's shape — object_type, object_id, properties (custom fields), created_at, updated_at, and a channels array (each entry has channel value, status, perma_status).

Inputs: object_id (required), object_type (required), workspace.

get_suprsend_object_preferencesA
Read-onlyDestructiveIdempotent

Read an object's category-level notification preferences and (optionally) per-channel overrides.

When to use:

  • Before update_suprsend_category_preference_object, to read current state.

  • Before sending to an object, to check delivery permission.

When NOT to use:

  • For the object's identity or channels — use get_suprsend_object.

  • For users — use get_suprsend_user_preferences.

Returns: the object's preference tree. Pass category to scope to one preference; omit for the full tree. Set channel_preferences=true to include per-channel overrides.

Inputs: object_id (required), object_type (required), category, workspace, +1 more.

get_suprsend_object_subscriptionsA
Read-onlyDestructiveIdempotent

List users / objects subscribed TO this object (its followers / members). Subscriptions are stored on the followed object.

When to use: the user asks "who follows project X?", "who's a member of organization Y?", or you need to enumerate an object's inbound subscribers.

When NOT to use:

  • For the inverse direction (what a user follows) — use get_suprsend_user_objects_subscriptions.

  • For mailing-list members — use get_suprsend_user_list_subscriptions on each user.

Returns: a paginated list of subscriber {type, id} entries. Set channel_preferences=true to also include each subscriber's channel preferences for this object. Default limit is 20.

Inputs: object_id (required), object_type (required), limit, workspace, +1 more.

get_suprsend_tenantA
Read-onlyDestructiveIdempotent

Get a tenant's settings, branding metadata, and custom properties by tenant_id. Tenants are sub-accounts of a workspace, modeling end-customers in multi-tenant SaaS deployments.

When to use: the user references a tenant by id and you need its full state.

When NOT to use:

  • To enumerate all tenants — use get_suprsend_tenants.

  • For tenant-level preference defaults — use get_tenant_default_preference.

Returns: the tenant's settings (branding URLs, contact info, custom fields).

Inputs: tenant_id (required), workspace.

get_suprsend_tenantsA
Read-onlyDestructiveIdempotent

List all tenants in the workspace. Use to discover tenant_ids before calling get_suprsend_tenant or upsert_suprsend_tenant.

Returns: up to limit tenants (default 100) with their id and properties.

Inputs: limit, workspace.

get_suprsend_userA
Read-onlyDestructiveIdempotent

Get a SuprSend user's full state by distinct_id. Users are end recipients of notifications, identified by your application's user id.

When to use: the user references a recipient by id and you need their stored properties or channel identifiers.

When NOT to use:

  • For non-user entities (organizations, projects, vehicles) — use get_suprsend_object.

  • For preferences only — use get_suprsend_user_preferences.

  • For mailing-list / object subscriptions — use get_suprsend_user_list_subscriptions or get_suprsend_user_objects_subscriptions.

Returns: YAML with distinct_id, properties (custom fields like name, plan, lang), created_at, updated_at, and a channels array — each entry has the channel value, status, and perma_status (e.g., bounced, blocked, soft-bounced).

Inputs: distinct_id (required), workspace.

get_suprsend_user_list_subscriptionsA
Read-onlyDestructiveIdempotent

List the SuprSend Lists this user belongs to. Lists are workspace-level recipient groups (segments / mailing lists), distinct from object follows.

When to use: the user asks "what mailing lists is X on?" or "what segments include X?".

When NOT to use:

  • For object follows (X follows project Y) — use get_suprsend_user_objects_subscriptions.

  • For followers OF an object — use get_suprsend_object_subscriptions.

Returns: a paginated list of List metadata. Default limit is 20; raise it for larger results.

Inputs: distinct_id (required), limit, workspace.

get_suprsend_user_objects_subscriptionsA
Read-onlyDestructiveIdempotent

List the objects this user is subscribed TO — what the user follows.

When to use: the user asks "what does X follow?", "what projects is X in?", or you need to enumerate a user's outbound subscriptions.

When NOT to use:

  • For followers OF an object (inverse direction) — use get_suprsend_object_subscriptions.

  • For mailing-list / segment membership — use get_suprsend_user_list_subscriptions.

Returns: a paginated list of {object_type, object_id} entries. Default limit is 20.

Inputs: distinct_id (required), limit, workspace.

get_suprsend_user_preferencesA
Read-onlyDestructiveIdempotent

Read a user's category-level notification preferences and (optionally) per-channel overrides.

When to use:

  • Before update_suprsend_users_preferences, to read current state.

  • The user asks what categories a recipient is opted in/out of.

  • Before sending, to check delivery permission for a category or channel.

When NOT to use:

  • For the user's identity or channel identifiers — use get_suprsend_user.

  • For tenant-level defaults — use get_tenant_default_preference.

  • For object preferences — use get_suprsend_object_preferences.

Returns: the user's preference tree. Pass category to scope to one preference; omit for the full tree. Set channel_preferences=true to include per-channel overrides.

Inputs: distinct_id (required), category, tenant_id, workspace, +1 more.

get_tenant_default_preferenceA
Read-onlyDestructiveIdempotent

Read a tenant's default category preferences — the inheritance baseline applied to new users in this tenant.

When to use:

  • Before update_suprsend_tenant_default_preference, to read current defaults.

  • To diagnose why new users have unexpected preference state.

When NOT to use:

  • For individual user / object preferences — use get_suprsend_user_preferences or get_suprsend_object_preferences.

Returns: the tenant's full default-preference tree.

Inputs: tenant_id (required), workspace.

list_workflowsA
Read-onlyIdempotent

List notification workflows in a workspace, in either draft or live mode.

mode=live returns the currently-active version of each workflow; mode=draft returns the staged-but-not-yet-promoted version. The two can differ — workflows often have a draft change in flight.

Returns: workflow slug, name, status, category, enabled state, and tags.

Inputs: mode (required), limit (required), workspace (required), offset.

search_suprsend_documentationA
Read-onlyDestructiveIdempotent

Search SuprSend's product documentation for technical guidance — APIs, SDKs, workflows, templates, tenants, lists, vendors, and connectors.

When to use:

  • The user asks how a SuprSend feature works or how to integrate one.

  • You need to verify a behavior before calling a write tool.

  • You're debugging an integration error.

When NOT to use: for runtime operations on SuprSend resources (users, objects, tenants, workflows) — those have dedicated tools.

Returns: a JSON array of {uri, snippet}. Snippets are excerpts; if a snippet doesn't fully answer, follow up with fetch_suprsend_documentation on the relevant uri.

Tips: use precise technical terms ("workflow trigger conditions", not "the rule thing"); add synonyms if the first query returns nothing.

Inputs: query (required).

update_suprsend_category_preference_objectA
DestructiveIdempotent

Set ONE category's preference for ONE object — opted in, opted out, or cant_unsubscribe (locked) — plus per-channel opt-outs within that category.

Replaces, does not merge. This call overwrites the existing preference for the named category. Previous opt-outs within the same category are lost; pass them again in opt_out_channels if you want to keep them.

When to use: changing a single category on a single object.

When NOT to use:

  • For object-wide channel toggles ("block all SMS") — use update_suprsend_object_channel_preference.

  • For users — use update_suprsend_users_preferences.

  • For tenant defaults — use update_suprsend_tenant_default_preference.

Preference values: opt_in enables; opt_out disables; cant_unsubscribe locks the object from toggling this category.

Returns: updated preference state on success; structured error on failure.

Inputs: category (required), object_id (required), preference (required), object_type (required), +2 more.

update_suprsend_object_channel_preferenceA
DestructiveIdempotent

Block or allow specific delivery channels for ONE object, applied across ALL categories.

is_restricted semantics: true blocks delivery on that channel; false re-enables it. Each entry in channel_preferences is a {channel, is_restricted} pair.

When NOT to use:

  • For per-category control — use update_suprsend_category_preference_object.

  • For users — use update_suprsend_user_channel_preference.

Side effects: takes effect on the next workflow run; in-flight notifications may still send.

Returns: updated channel-preference state on success.

Inputs: object_id (required), object_type (required), channel_preferences (required), workspace.

update_suprsend_tenant_default_preferenceA
DestructiveIdempotent

Set the default category preference inherited by NEW users created in this tenant. Existing users are not affected; their preferences are independent.

preference values:

  • opt_in — new users are opted into this category.

  • opt_out — new users are opted out.

  • cant_unsubscribe — new users are opted in AND locked from toggling.

mandatory_channels — channels users cannot disable for this category. blocked_channels — channels that cannot be enabled. visible_to_subscriber — whether end-users see this category in their preference UI.

When NOT to use:

  • For per-user overrides — use update_suprsend_users_preferences.

  • For per-object overrides — use update_suprsend_category_preference_object.

Side effects: changes apply only to users created AFTER this call. To retroactively update existing users, call update_suprsend_users_preferences per user.

Returns: the updated tenant default preference on success.

Inputs: category (required), tenant_id (required), preference (required), blocked_channels (required), +3 more.

update_suprsend_user_channel_preferenceA
DestructiveIdempotent

Block or allow specific delivery channels for ONE user, applied across ALL categories. Use this for "block all SMS to this user" or "allow only email" patterns.

is_restricted semantics: true blocks delivery on that channel; false re-enables it. Each entry in channel_preferences is a {channel, is_restricted} pair.

When NOT to use:

  • For per-category control — use update_suprsend_users_preferences.

  • For permanent invalidation (e.g., a bounced email) — that's set by SuprSend automatically as perma_status; don't try to override it here.

  • For objects — use update_suprsend_object_channel_preference.

Side effects: takes effect on the next workflow run; in-flight notifications already in the queue may still send.

Returns: updated channel-preference state on success.

Inputs: distinct_id (required), channel_preferences (required), workspace.

update_suprsend_users_preferencesA
DestructiveIdempotent

Set ONE category's preference for ONE user — opted in, opted out, or cant_unsubscribe (locked) — plus per-channel opt-outs within that category.

Replaces, does not merge. This call overwrites the existing preference for the named category. Previous opt-outs within the same category are lost; pass them again in opt_out_channels if you want to keep them.

When to use: changing a single category for a single user.

When NOT to use:

  • For tenant-wide defaults — use update_suprsend_tenant_default_preference.

  • For cross-category channel toggles ("block all SMS") — use update_suprsend_user_channel_preference.

  • For the same flow on objects — use update_suprsend_category_preference_object.

Preference values: opt_in enables; opt_out disables; cant_unsubscribe locks the user from toggling this category in their preference UI.

Returns: updated preference state on success; structured error on failure (e.g., unknown category slug).

Inputs: categories (required), distinct_ids (required), channel_preferences (required), workspace.

upsert_suprsend_objectA
Destructive

Modify properties or channel identifiers on a SuprSend object — a non-user entity like an organization, project, or vehicle. One call performs ONE action; for multiple changes, call this tool multiple times.

Actions:

  • set, set_once, unset, remove — modify a scalar property by key/value. remove permanently deletes the key.

  • append, increment — modify array / numeric values.

  • add_email / remove_email, add_sms / remove_sms, add_whatsapp / remove_whatsapp, add_androidpush / remove_androidpush, add_iospush / remove_iospush, add_slack / remove_slack, add_ms_teams / remove_ms_teams, add_webpush / remove_webpush — register or deregister a delivery channel.

Channel registration is special. For channel identifiers ALWAYS use the dedicated add_ / remove_ actions — generic set / unset will not register the channel correctly with the delivery router. Slack and MS Teams additionally require the corresponding slack_details / ms_teams_details payload alongside the action; channel id alone is not enough.

When to use: creating an object or modifying its stored state — properties, channels, identifiers.

When NOT to use:

  • For users — use upsert_suprsend_user instead.

  • For preferences — use update_suprsend_category_preference_object (per category) or update_suprsend_object_channel_preference (across categories).

  • For followers / members — use add_suprsend_object_subscriptions.

Side effects: remove and unset permanently delete data. add_ makes the object reachable on that channel for any future workflow run; remove_ stops delivery immediately.

object_type namespaces the object (e.g., "organization", "project") and is required.

Returns: the updated object on success; structured error with field reasons on failure.

Inputs: action (required), object_id (required), object_type (required), key, +6 more.

upsert_suprsend_tenantA
Destructive

Create a new tenant or update an existing tenant's properties. Tenants are sub-accounts of a workspace, used to model end-customers in multi-tenant SaaS apps.

tenant_properties is merged with existing — not replaced. Pass only the fields you want to change. Common fields include name, branding URLs, and contact info.

When NOT to use:

  • For preference defaults — use update_suprsend_tenant_default_preference.

  • For users / objects within a tenant — use upsert_suprsend_user / upsert_suprsend_object.

Returns: the updated tenant on success.

Inputs: tenant_id (required), workspace, tenant_properties.

upsert_suprsend_userA
Destructive

Modify properties or channel identifiers on a SuprSend user. One call performs ONE action; for multiple changes, call this tool multiple times.

Actions:

  • set, set_once, unset, remove — modify a scalar property by key/value. remove permanently deletes the key.

  • append, increment — modify array / numeric values.

  • set_preferred_language, set_timezone — locale and timezone on the user.

  • add_email / remove_email, add_sms / remove_sms, add_whatsapp / remove_whatsapp, add_androidpush / remove_androidpush, add_iospush / remove_iospush, add_slack / remove_slack — register or deregister a delivery channel.

Channel registration is special. For channel identifiers ALWAYS use the dedicated add_ / remove_ actions — generic set / unset will not register the channel correctly with the delivery router. Slack additionally requires the slack_details payload alongside the action.

When to use: creating a new user or modifying an existing user's stored state.

When NOT to use:

  • For non-user entities — use upsert_suprsend_object.

  • For preferences — use update_suprsend_users_preferences (per category) or update_suprsend_user_channel_preference (across categories).

  • For tenant settings — use upsert_suprsend_tenant.

Side effects: remove and unset permanently delete data. add_ makes the user reachable on that channel for any future workflow run; remove_ stops delivery immediately.

Returns: the updated user on success; structured error with field reasons on failure.

Inputs: action (required), distinct_id (required), key, value, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair, and the descriptions include explicit

    Naming Consistency4/5

    The vast majority of tools follow a clear snake_case verb_suprsend_entity pattern (upsert_suprsend_user, get_suprsend_object_preferences). There are minor irregularities such as list_workflows and get_tenant_default_preference missing the suprsend prefix, and update_suprsend_users_preferences is awkwardly plural.

    Tool Count3/5

    With 22 tools, the set falls into the borderline-heavy range. Many tools are individually justified by the breadth of the domain, but the preference and subscription families alone account for a large number of similar-purpose tools.

    Completeness3/5

    The server covers core reads, upserts, preference management, and subscription listing/creation across users, objects, and tenants. It has notable gaps: no remove/delete tools for subscriptions, users, or objects, no workflow create/update/trigger tools, and no way to actually send a notification, which means several real-world workflows hit dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage OneSignal push notifications, email, SMS, and user management through natural language. Supports multi-channel messaging, segmentation, templates, analytics, and iOS Live Activities with 50+ tools for complete OneSignal API coverage.
      1
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to interact with the Courier notification API, allowing them to send messages, manage profiles, debug deliveries, configure lists, and more through 60 tools.
      15 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Novu's notification infrastructure, supporting event triggering, subscriber management, topic operations, and notification retrieval.
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Human-in-the-loop approvals and notifications for AI agents via WhatsApp. Enables Cursor, Claude Code, and autonomous AI agents to reach users away from their computers.
      196 npm
      ISC