Exceptionless

@Exceptionless show me the current project configuration including data exclusions and session tracking settings

Retrieved configuration for project 'Production API Monitor'. Session tracking is enabled with a 30-second heartbeat interval. Data exclusions are active for fields matching 'password', 'token', and 'creditCard'. Storage limit is set to 3,000 events per day with a 90-day retention window. Note that this configuration contains sensitive project settings—review carefully before sharing with teammates or external tools.

This example demonstrates read-only configuration retrieval. The MCP returns settings for exactly one project tied to your API key—you cannot query multiple projects or switch context. Configuration values may include sensitive thresholds or exclusion patterns that reveal your monitoring strategy.

@Exceptionless submit an error event for a failed database connection in the checkout service with stack trace and user context

Submitted error event to Exceptionless. Event type: error. Message: 'Database connection timeout in checkout service'. Included stack trace (12 frames), user context (ID: user_89234, email: redacted), and environment tags (service: checkout, region: us-east-1). Exceptionless accepted the event for asynchronous processing—confirmation does not guarantee the event was persisted or will appear in your dashboard immediately.

This write example shows telemetry submission. The MCP accepts the event but returns only an acknowledgment—Exceptionless processes events asynchronously, so you won't see immediate confirmation of storage or indexing. Rate limits apply per your plan tier; burst submissions may be throttled or dropped.

@Exceptionless record a session heartbeat for user session abc-7829 and then summarize what active session tracking tells us about current system health

Recorded heartbeat for session 'abc-7829' at 14:32 UTC. Session has been active for 8 minutes with 4 prior heartbeats. Based on Exceptionless session tracking patterns, active sessions indicate real-time user engagement—frequent heartbeats with no error events suggest stable client connectivity, while gaps or missing heartbeats often precede crash reports or network issues. This session shows consistent 30-second intervals, aligning with healthy client behavior.

This synthesis example pairs a write action (heartbeat recording) with AI reasoning about session health patterns. The heartbeat write is irreversible and contributes to your event quota. The AI's interpretation is illustrative—actual session health analysis requires querying your Exceptionless dashboard for aggregate metrics across all sessions.

When Exceptionless MCP helps support triage production crashes

A 3-person support team fields customer complaints about intermittent crashes in a SaaS product. The Exceptionless MCP lets them submit structured events from Switchy when a customer reports an issue—tagging the event with ticket ID, user context, and reproduction steps—so engineering sees the full picture without Slack back-and-forth. The MCP's 4 tools cover the core workflow: submit events, check project config to confirm the right environment is logging, and close sessions when a repro attempt finishes. This works when your support volume is under 50 tickets a day and your team already uses Exceptionless for error tracking. If you're triaging hundreds of issues daily or need cross-project visibility, the single-project API key becomes a bottleneck. For small teams consolidating error context in one workspace, this MCP closes the loop between support and engineering.

Why this MCP fits lean on-call rotations

A 5-engineer startup runs a weekly on-call rotation. When an alert fires at 2am, the on-call engineer opens Switchy, pulls logs from other MCPs, and uses Exceptionless to submit a structured event capturing the incident timeline, affected endpoints, and mitigation steps. The session heartbeat tool keeps the incident session alive while they investigate; closing the session marks resolution. This pattern works because Exceptionless is already their error aggregator, and the MCP's API key scopes to one project—no risk of cross-contaminating staging and production events. The trade-off: if your on-call process spans multiple services or projects, the single-key constraint means you'll toggle API keys or skip the MCP entirely. For teams with one primary production project and fewer than 10 incidents a month, this MCP turns Switchy into a lightweight incident journal.

When Exceptionless MCP streamlines manual QA workflows

A 2-person QA team runs exploratory testing sessions before each release. They use Switchy to coordinate test coverage, and the Exceptionless MCP to log session starts, submit events when they hit a bug, and close sessions when a test pass finishes. The session heartbeat tool keeps long QA runs from timing out. This setup shines when your QA cycle is under 20 hours a week and your team already tags Exceptionless events with release metadata. The MCP's 4 tools map cleanly to the session lifecycle, and the API key constraint enforces single-project discipline—no accidental cross-environment pollution. If your QA process involves parallel testing across staging, canary, and production, the one-key-per-project model breaks down fast. For small teams doing serial, focused QA on a single environment, this MCP turns ad-hoc bug reports into structured telemetry without leaving the workspace.