Skip to main content
Glama

Server Details

The elmah.io MCP server allows AI assistants to interact directly with your error logs, deployments, and organization statistics. Debug production issues faster than ever before.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

B3.4/5.0

Scored across 27 tools

Disambiguation4/5

Each tool targets a distinct resource+action, and the descriptions explicitly differentiate near-neighbors: messages_bot vs messages_bot_by_query (ID vs query), messages_count vs messages_histogram (single total vs buckets), and fix/open and hide/unhide are clear inverses. A few pairs (messages_bot_by_query vs messages_unbot_by_query, recommendations_list vs get_details) require reading descriptions, but overall boundaries are clear.

Naming Consistency4/5

The dominant pattern is resource_action in snake_case (logs_list, messages_count, uptime_get_details, users_get_current), applied consistently. Minor deviations exist: get_details is sometimes just _details implied, and bare state verbs like messages_bot/messages_fix/messages_open lack an explicit action-name pairing with their inverses (unbot/unhide), but the convention remains readable.

Tool Count3/5

27 tools is slightly over the comfortable range, driven by 8 message-mutation variants (bot/unbot/fix/open/hide/unhide plus by_query versions). Each has a distinct role in the domain, but the surface feels heavy and the paired mutation tools inflate the count.

Completeness3/5

Read coverage is broad across logs, messages, heartbeats, deployments, uptime, recommendations, organizations and users, plus message state mutations. However, most resources are read-only (no create/update/delete for logs, heartbeats, uptime checks or deployments), and there is no general message query/search tool beyond recent, frequent and count, which are notable gaps for a monitoring platform.

Publisher details

Operator
elmah.io
Operator website
https://elmah.io
Vendor relationship
Not available
Privacy policy
Not provided
Trust center
Not available
Restrictions
Not available

Available Tools

27 tools
deployments_listA
Read-onlyIdempotent
Inspect

List recent deployments for a log. A deployment represents a release of the software.

Inputs: logId (required), count, includeLogMessageMetrics.

heartbeats_get_detailsA
Read-onlyIdempotent
Inspect

Get detailed information and recent check-in history for a specific heartbeat.

Inputs: logId (required), heartbeatId (required).

heartbeats_listB
Read-onlyIdempotent
Inspect

Get a list of all heartbeats configured for a log, including their current status.

Inputs: logId (required).

logs_get_detailsB
Read-onlyIdempotent
Inspect

Get detailed configuration and metadata for a specific log.

Inputs: logId (required), includeFilterDetails, includeUptimeDetails, includeHeartbeatDetails.

logs_listB
Read-onlyIdempotent
Inspect

Get a list of logs that the current user has access to.

Inputs: access, favorites, environment.

messages_botA
DestructiveIdempotent
Inspect

Mark log messages as bot-generated by ID. Changes data. Unless the user asked for exactly this change, say which messages you will change and get their confirmation first.

Inputs: logId (required), messageIds (required).

messages_bot_by_queryA
DestructiveIdempotent
Inspect

Mark all messages matching a query as bot-generated (use instead of messages_bot for large groups, e.g. one client IP). Changes data. Unless the user asked for exactly this change, say which messages you will change and get their confirmation first. First run messages_count with the same logId/severity/query/from and show the user the number (it also counts messages already marked as bot, which are skipped). Returns matchedCount, updatedCount, capped and a few sample messages.

Inputs: logId (required), query (required), severity (required), to, +3 more.

messages_countC
Read-onlyIdempotent
Inspect

Count the number of log messages based on severity and timeframe.

Inputs: logId (required), from, query, hidden, +1 more.

messages_fixA
DestructiveIdempotent
Inspect

Mark a log message as fixed by ID. Changes data. Unless the user asked for exactly this change, say which messages you will change and get their confirmation first.

Inputs: logId (required), messageId (required), markAllAsFixed.

messages_getA
Read-onlyIdempotent
Inspect

Fetch a single log message by ID. Includes full details like stack trace and metadata.

Inputs: logId (required), messageId (required), fields.

messages_hideA
DestructiveIdempotent
Inspect

Hide a log message by ID. Changes data. Unless the user asked for exactly this change, say which messages you will change and get their confirmation first.

Inputs: logId (required), messageId (required), markAllAsHidden.

messages_histogramA
Read-onlyIdempotent
Inspect

Count log messages per hour, day or week, to see when errors started, spiked or stopped. Empty buckets are included with a count of 0. Use messages_count for a single total.

Inputs: logId (required), to, from, query, +3 more.

messages_list_frequentB
Read-onlyIdempotent
Inspect

Identify the most frequent/common error groups in a log. Great for finding 'noisy' bugs.

Inputs: logId (required), to, from, count, +4 more.

messages_list_recentB
Read-onlyIdempotent
Inspect

List the most recent log messages for a specific log.

Inputs: logId (required), to, from, count, +4 more.

messages_openA
DestructiveIdempotent
Inspect

Reopen a fixed log message by ID. Changes data. Unless the user asked for exactly this change, say which messages you will change and get their confirmation first.

Inputs: logId (required), messageId (required), markAllAsOpen.

messages_unbotA
DestructiveIdempotent
Inspect

Unmark log messages as bot-generated by ID. Changes data. Unless the user asked for exactly this change, say which messages you will change and get their confirmation first.

Inputs: logId (required), messageIds (required).

messages_unbot_by_queryA
DestructiveIdempotent
Inspect

Unmark all messages matching a query as bot-generated. Changes data. Unless the user asked for exactly this change, say which messages you will change and get their confirmation first.

Inputs: logId (required), query (required), severity (required), to, +3 more.

messages_unhideA
DestructiveIdempotent
Inspect

Unhide a hidden log message by ID. Changes data. Unless the user asked for exactly this change, say which messages you will change and get their confirmation first.

Inputs: logId (required), messageId (required), markAllAsUnhidden.

organizations_get_detailsB
Read-onlyIdempotent
Inspect

Get detailed information about an organization including configuration, subscription, usage statistics, and more.

Inputs: organizationId (required), includeUsage.

organizations_listA
Read-onlyIdempotent
Inspect

Get a list of all organizations that the current user is a part of. When authenticated as an organization, the current organization is returned.

Inputs: no named parameters.

recommendations_get_detailsA
Read-onlyIdempotent
Inspect

Get details about a single recommendation for a log or an organization. Specify exactly one of logId or organizationId.

Inputs: recommendationId (required), logId, organizationId.

recommendations_listA
Read-onlyIdempotent
Inspect

List automated recommendations for improving error monitoring setup, security and configuration, for a log or an organization (exactly one of logId or organizationId). Excludes description and suggestions; use recommendations_get_details for those.

Inputs: logId, state, organizationId.

stacktrace_renderA
Read-onlyIdempotent
Inspect

Shows a stack trace to the user as a formatted, syntax highlighted view (.NET and JavaScript). Use this whenever the user shares or asks about a stack trace, from elmah.io or from their own code, instead of repeating it in a code block. Pass the stack trace exactly as received. It does not analyze the trace; explain it in your own reply.

Inputs: stackTrace (required), language.

system_get_contextA
Read-onlyIdempotent
Inspect

Getting system information like current date and time. Use this when calculating time intervals, etc.

Inputs: no named parameters.

uptime_get_detailsA
Read-onlyIdempotent
Inspect

Fetches the latest real-time results for a specific uptime check, including regional performance metrics.

Inputs: logId (required), checkId (required).

uptime_listA
Read-onlyIdempotent
Inspect

Get a list of all uptime checks for a log, including their current status and 24h up/down percentage.

Inputs: logId (required).

users_get_currentB
Read-onlyIdempotent
Inspect

Fetch the current user details.

Inputs: no named parameters.

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources