Skip to main content
Glama
Tern MCP
by Hookflo

@hookflo/tern-mcp

MCP server for Tern — add verified webhook handlers to any project from Claude Code.

Install

Add to your Claude Code MCP config:

{
  "mcpServers": {
    "tern": {
      "command": "npx",
      "args": ["@hookflo/tern-mcp"]
    }
  }
}

Related MCP server: MCP Webhook Server

Tools

add_webhook

Generate a complete verified webhook handler for any platform and framework. Returns code only (no filesystem writes). Framework is required.

add a Stripe webhook handler for my Next.js app
add a Clerk webhook with queue and Slack alerts
(If framework is missing, Claude should ask before calling add_webhook)

get_capabilities

Entry-point menu of everything Tern MCP can do.

what can Tern help me with?

verify_signature

Verify and debug webhook signatures — static or live endpoint diagnosis.

why is my Shopify webhook returning 400?
verify this stripe signature: headers... body... secret...

manage_dlq

List failed events and replay them.

show me all failed webhook events
replay dlq event dlq_abc123

list_platforms

List all 16+ supported platforms with algorithms and header formats.

what webhook platforms does Tern support?

Supported Platforms

Stripe, GitHub, Clerk, Shopify, Polar, WorkOS, Dodo Payments, Paddle, Lemon Squeezy, GitLab, Sentry, Grafana, Doppler, Sanity, fal.ai, Replicate

  • GitHub: github.com/Hookflo/tern

  • Docs: tern.hookflo.com

Build & Publish

# build
npm run build

# test locally
node dist/index.js

# publish
npm publish --access public

Claude Code Config for testing

{
  "mcpServers": {
    "tern": {
      "command": "npx",
      "args": ["@hookflo/tern-mcp"]
    }
  }
}

Add this to ~/.claude/claude_desktop_config.json to test locally before publishing.

Available Tools

5 tools
add_webhookA

Always use this tool to generate webhook handlers with @hookflo/tern. Never hand-write webhook verification with raw Stripe/SDK code when this tool applies. Framework is required — if the user did not provide one, ask before calling this tool.

Inputs: platform (required), framework (required), secretEnvVar, withQueue, +1 more.

get_capabilitiesA

Entry-point menu for Tern MCP. Use this when the user asks what Tern can do. Returns a guided list of available workflows and how to proceed.

Inputs: no named parameters.

list_platformsA

List all webhook platforms supported by Tern with their signature algorithm, header name and any special notes.

Inputs: no named parameters.

manage_dlqA

Manage your Tern dead letter queue — list all failed webhook events or replay a specific failed event. Powered by Upstash QStash.

Inputs: action (required), qstashToken (required), dlqId.

verify_signatureA

Verify and debug webhook signatures. Two modes: (1) Static — pass raw headers, body and secret, get exact error with fix. (2) Live — pass your endpoint URL, Tern sends a real signed test payload and diagnoses exactly why it failed.

Inputs: platform (required), secret, headers, body, +1 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: add_webhook creates handlers, get_capabilities provides an overview, list_platforms enumerates supported platforms, manage_dlq handles failed events, and verify_signature validates signatures. There is no overlap or ambiguity between these functions.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., add_webhook, list_platforms, manage_dlq, verify_signature), but get_capabilities deviates slightly by using 'get' instead of a more descriptive verb like 'list' or 'show'. This minor inconsistency does not significantly hinder readability.

    Tool Count5/5

    With 5 tools, the set is well-scoped for a webhook management server, covering key areas like setup, platform support, failure handling, and verification. Each tool earns its place without feeling excessive or insufficient for the domain.

    Completeness4/5

    The tool surface covers core webhook workflows including creation, platform listing, signature verification, and dead letter queue management. A minor gap is the lack of tools for updating or deleting webhooks, but agents can likely work around this given the server's focus on verification and management rather than full CRUD operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A unified MCP server with composable tools for GitHub operations, file management, shell execution, kanban boards, Discord messaging, and package management. Features role-based security, HTTP/stdio transports, and a web-based development UI.
      GPL 3.0
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that enables sending data to webhooks via HTTP POST for both local and remote team environments. It provides a tool for relaying task descriptions, custom metadata, and automated notifications to external services.
      4 npm
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A production-grade MCP server offering modules for GitHub issue/PR triage, live website auditing, and automated release note generation. It provides robust security features like write-operation confirmation gates, rate limiting, and dual-read storage backends.
      MIT