Skip to main content
Glama

Server Details

Send notifications, manage templates, and configure integrations with Courier.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
trycourier/courier-mcp
GitHub Stars
2
Server Listing
Courier MCP Server

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsB

Average 3.7/5 across 123 of 123 tools scored. Lowest: 2.8/5.

Server CoherenceA
Disambiguation4/5

Despite having 123 tools, each has a distinct purpose clearly explained in the description. Some pairs like send_message vs send_message_template are similar but differentiated by inline vs template usage. A few tools like cancel_automation and invoke_ad_hoc_automation are distinct but might cause minor confusion. Overall, the surface is well-differentiated.

Naming Consistency3/5

The naming pattern is mostly verb_noun (create_brand, delete_list, get_message). However, there are inconsistencies like 'add_subscribers_to_list' vs 'bulk_subscribe_to_list' and 'replace_profile' vs 'patch_profile'. Some tools use 'list_' while others use 'get_' for similar operations (list_messages vs get_message). This mix, while readable, lacks a uniform style.

Tool Count3/5

123 tools is a large number for a single server. The domain is broad (notifications, users, lists, tenants, journeys, automations, etc.), but some tools feel redundant (multiple send_message variants) or tangential (courier_installation_guide). The count is on the high side but still somewhat justified by the platform's scope.

Completeness5/5

The tool surface covers nearly every operation for all major entities: CRUD, publish/archive, versioning, bulk operations, preferences, and more. Missing operations are rare (e.g., no direct 'get_bulk_job_users' but that's minor). The set feels comprehensive for a notification infrastructure platform.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.