Courier

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

검사 2/3 통과 · 내가 묻는 내용은 제작자 서버(mcp.courier.com)를 거쳐요 · ✓ 명령 확인 2026년 11월 13일

claude mcp add --transport http --scope user courier https://mcp.courier.com

{
  "mcpServers": {
    "courier": {
      "url": "https://mcp.courier.com"
    }
  }
}

{
  "servers": {
    "courier": {
      "type": "http",
      "url": "https://mcp.courier.com"
    }
  }
}

어떤 앱에서 쓸 수 있나요

이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.

인터넷으로 연결하는 앱

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

모든 앱과 장단점 →

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 11일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• list_messages

  List messages you've previously sent. Filter by status, recipient, notification, provider, tags, or tenant.

• get_message

  Get the full details and status of a single message by its ID.

• get_message_content

  Get the rendered content (HTML, text, subject) of a previously sent message.

• get_message_history

  Get the event history for a message, showing each step in the delivery pipeline (enqueued, sent, delivered, etc.).

• list_notifications

  List notification templates, newest first. Pass tags to return only templates carrying ALL of the given tags. Page through the rest with cursor.

• get_notification_content

  Get the published content blocks of a notification template.

• get_notification_draft_content

  Get the draft (unpublished) content blocks of a notification template.

• create_notification

  Create a V2 notification template. name is required. Content may be provided inline or set separately afterwards. A newly created template is a draft; making it live is a separate step this tool cannot perform. Link a routing strategy via notification.routing.strategy_id to contr

• get_notification

  Retrieve a notification template by ID. Optionally request draft, published, or a version such as v001.

• replace_notification

  Replace a notification template entirely (full document PUT). The template stays a draft; making it live is a separate step this tool cannot perform.

• put_notification_content

  Replace the elemental content of a V2 notification template. Overwrites all elements. Use channel elements to target specific channels. Multi-channel example: elements: [{ type: "channel", channel: "email", elements: [{ type: "meta", title: "Hello" }, { type: "text", content: "Em

• put_notification_element

  Update a single element within a V2 notification template. The template stays a draft; making it live is a separate step this tool cannot perform.

• put_notification_locale

  Set locale-specific content overrides for a V2 notification template. Each element override must reference an existing element by its id. Example for Spanish locale: { notification_id: "nt_01abc", locale_id: "es", elements: [{ id: "elem_meta_1", title: "Restablecer contraseña" },

• list_notification_versions

  List the version history of a notification template — each published version with when it was created. Use this to say what changed and when, or to find the version string get_notification accepts.

• list_notification_checks

  List the checks recorded against one notification submission. Checks are the gates a submission has to clear before it goes out, so a failing check here is the reason a template is stuck rather than live.

• list_providers

  List configured provider integrations for the workspace.

• get_provider

  Fetch a single provider configuration by ID.

• list_provider_catalog

  List the provider integrations Courier supports and the configuration each one expects. This is the catalog of what COULD be connected, not what this workspace has configured — use list_providers for that. Answers "what can I connect Courier to" and "what do I need in order to se

• get_routing_strategy

  Retrieve a routing strategy by ID. Returns the full entity including routing, channels, and providers.

• list_routing_strategies

  List the workspace's routing strategies, returning metadata only. A routing strategy decides which channel a notification takes and in what order. Use this to find the rs_-prefixed strategy ID that get_routing_strategy needs for the full definition.

• list_preference_sections

  List the workspace's preference sections, each with the topics inside it. One call returns the whole opt-in surface: everything a user could subscribe to or opt out of. This is what the workspace DEFINES — use get_user_preferences for what a particular person actually chose.

• get_preference_section

  Get one preference section by ID, including its topics. Use this when you already know which section you need; list_preference_sections returns every section with its topics in one call.

• list_preference_topics

  List the subscription topics inside one preference section. A topic is the individual thing a user opts in or out of, and its ID is what get_user_preference_topic takes.

• get_preference_topic

  Get one subscription topic within a section, including its default opt-in state. Returns 404 if the section or topic does not exist, or if the topic belongs to a different section — so a 404 here can mean the pairing is wrong rather than the topic missing.

• create_journey

  Create a new journey. Always created as a draft; making it live is a separate step this tool cannot perform. Send two nodes: the trigger, and an exit node last. Both are required — a create with no exit node is rejected, and the API reports that as "exit node must be the last nod

• get_journey

  Get a journey by ID. Pass version=draft to retrieve the working draft, or version=vN for a historical version. Defaults to published.

• replace_journey

  Replace (update) a journey draft. Full document replacement — include all nodes and properties in the body, the trigger included; anything omitted is deleted. The journey stays a draft; making the change live is a separate step this tool cannot perform. This is where send, delay,

• create_journey_template

  Create a notification template scoped to a journey. Always created as a draft; making it live is a separate step this tool cannot perform. The template can then be referenced in journey send nodes. content.elements must be wrapped in a channel block — the API rejects bare element

• put_journey_template_content

  Replace the elemental content of a journey-scoped notification template. Overwrites all elements. The template stays a draft; making it live is a separate step this tool cannot perform.

• put_journey_template_locale

  Set locale-specific content overrides for a journey-scoped notification template. Each element override must reference an existing element by its id. The template stays a draft; making it live is a separate step this tool cannot perform.

• list_journeys

  List journey templates in the workspace, returning the journey IDs and version state of each. Optionally filter by version (published or draft).

• list_journey_templates

  List notification templates scoped to a journey. Journey-scoped templates can only be used by send nodes within the same journey. Call this to discover template IDs before wiring send nodes in replace_journey.

• get_journey_template

  Get a journey-scoped notification template by notification ID. Pass version=draft to retrieve the working draft (required before the template has been published). Defaults to published.

• get_journey_template_content

  Fetch the elemental content of a journey-scoped notification template. Pass version=draft for the working draft, or vN for a historical version. Defaults to published.

• get_notification_metrics AI에게 내리는 지시처럼 보여요

  Delivery funnel for ONE notification template over time: sent, delivered, opened, clicked, errors and undeliverable, per provider and channel, in time buckets. Choosing the window — supply EITHER `lookback` OR `start` and `end` together, NEVER both. Supplying both is rejected. Fo

• get_tenant

  Get a tenant by its ID.

• list_tenants

  List the workspace's tenants. A tenant is a customer or organisation whose users, branding and preferences are scoped separately; this answers "what tenants do I have" and gives you the tenant IDs get_tenant needs.

• list_tenant_users

  List the users associated with one tenant. Use this to confirm whether someone actually belongs to the tenant whose branding or preferences you are reasoning about.

• get_user_profile_by_id

  Get a user profile by their ID. Returns profile data including email, phone, and custom properties.

• get_user_list_subscriptions

  List the lists one user is subscribed to. Use this when explaining why a user received something — a subscription here is the reason a list-addressed send reached them, and its absence rules that path out.

• get_user_preferences

  Get a user's notification preferences (subscriptions, opt-outs, channel preferences).

• get_user_preference_topic

  Get one user's choice for a single subscription topic — whether they opted in or out, and per channel. Use this when you already know which topic is in question; get_user_preferences returns all of them at once.

• list_user_tenants

  List the tenants a user belongs to. Preferences and branding can be scoped per tenant, so this tells you which tenant-scoped settings could apply to this user at all before you go looking for them.

• list_brands

  List the workspace's brands. A brand is the reusable logo, colors and email styling a notification template renders with; this gives you the brand IDs a template's brand reference points at.

• get_brand

  Get one brand by ID, including its colors, logo and styling settings. Read this to describe what a template referencing this brand will actually look like.

• courier_installation_guide

  Get the Courier SDK installation guide for one platform: the install command, a quick-start code sample and the relevant doc links. This is the answer to "how do I integrate Courier" or "how do I get started". Client-side platforms need a JWT to authenticate; each guide says so a

• list_automations

  List the workspace's automation templates, each with its template ID and whether it has a published or draft version. Answers "what automations already exist here" — this only reads the catalog, it never runs one.

• list_audiences

  List the workspace's audiences. An audience is a saved filter over user profiles — a dynamic segment — so this answers "who can I target" and gives you the audience IDs that journey audience triggers and send requests refer to.

• get_audience

  Get one audience by ID, including the filter that defines its membership. Read this to explain why someone is or is not in an audience — the filter is the rule, not a stored member list. Use list_audience_members for who currently matches.

• list_audience_members

  List the users who currently match an audience's filter. Membership is computed, so this reflects profiles as they are right now — a profile change can move someone in or out without the audience itself being edited.

• list_lists

  List the workspace's lists. A list is an explicit, subscription-based group of users — someone is on it because they were subscribed, not because they match a rule. Optionally filter by an id pattern such as "example.list.*".

• get_list

  Get one list by its ID, including its name and current state.

• get_list_subscribers

  List the users subscribed to a list. Use this to confirm whether someone was actually on a list at all — a subscription here is the reason a list-addressed send reached them.

• list_digest_instances

  List the digest instances for a digest schedule. Each instance is the events accumulated so far for one user against that schedule, so this shows what is waiting to go out and answers why a digest has not arrived yet — it is still accumulating, or it has nothing in it.

• update_audience

  Create or update an audience with a filter definition.

• delete_audience

  Delete an audience by its ID.

• get_audit_event

  Get a specific audit event by its ID.

• list_audit_events

  List audit events in the workspace. Useful for tracking API usage and changes.

• generate_jwt_for_user

  Generate a JWT authentication token for a user. Used for client-side SDK auth (Inbox, Preferences, etc.).

• invoke_automation_template

  Invoke an automation run from an existing automation template. template_id refers to an existing automation template in the workspace. Example: { template_id: "auto-onboarding", recipient: "user-123", data: { plan: "pro" } }.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 15일 점검

• ✓ 통과

  제작자와 저장소 일치

  레지스트리 이름이 GitHub 계정 trycourier 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  750ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✕ 실패

  도구 설명에 숨겨진 지시 없음

  도구 설명 2개에 AI에게 지시하는 것처럼 보이는 글이 있어요. 설치하기 전에 아래 내용을 읽어 보세요

우리가 확인하는 것 → · JSON

사용자 리뷰

아직 리뷰가 없어요

로그인하고 리뷰 쓰기

기타 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 19870개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 19870개 중 10%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 19870개 중 45%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

비슷하게 동작하는 다른 것

같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.

카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.

제작자: koala73·널리 사용됨·★ 9.1만·어제 업데이트

클라우드에서 실행✓ 서비스 회사 · worldmonitor.app

연결 방법

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

제작자: openstatusHQ·널리 사용됨·★ 9.3천·2개월 전 업데이트

클라우드에서 실행✓ 서비스 회사 · openstatus.dev

연결 방법

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

제작자: JanDeDobbeleer·널리 사용됨·★ 2.4만 저장소 전체의 별·26일 전 업데이트

클라우드에서 실행✓ 서비스 회사 · ohmyposh.dev

연결 방법

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

제작자: Klavis-AI·성장 중·★ 5.8천·14개월 전 업데이트

클라우드에서 실행저장소 보관됨✓ klavis.ai

연결 방법

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

제작자: jitsucom·널리 사용됨·★ 5.1천·4개월 전 업데이트

클라우드에서 실행✓ 서비스 회사 · jitsu.com

연결 방법

• World Monitor — 클라우드에서 동작, 설치 불필요 · 키 불필요
• openstatus — 클라우드에서 동작, 설치 불필요 · 키 불필요
• Oh My Posh Validator — 클라우드에서 동작, 설치 불필요 · 키 불필요
• Strata — 클라우드에서 동작, 설치 불필요 · 키 불필요
• Jitsu — 클라우드에서 동작, 설치 불필요 · 키 불필요

제작자의 README

저장소에서 README를 찾지 못했어요