---
title: "MCP or CLI? Yes."
description: "Sentry ships a unified experience that bridges CLI and MCP, arguing both can coexist rather than one replacing the other. The CLI handles filesystem tasks like grepping raw event logs from session replays, which MCP cannot do efficiently without server-side pre-aggregation. MCP provides native tool discovery and steering that the CLI lacks, allowing agents to discover behavior without explicit instructions. The implementation shares authentication by launching the MCP server in stdio mode with a shim that passes CLI credentials through a different token header to bypass OAuth constraints. This approach works around current MCP limitations, including inconsistent support for deferred tool calling, instructions metadata, and events across different harnesses."
---

# MCP or CLI? Yes.

[Sentry](https://yomu.fyi/company/sentry) · David Cramer · Nov 10, 2026

**Type:** Announcement

## Summary

Sentry ships a unified experience that bridges CLI and MCP, arguing both can coexist rather than one replacing the other. The CLI handles filesystem tasks like grepping raw event logs from session replays, which MCP cannot do efficiently without server-side pre-aggregation. MCP provides native tool discovery and steering that the CLI lacks, allowing agents to discover behavior without explicit instructions. The implementation shares authentication by launching the MCP server in stdio mode with a shim that passes CLI credentials through a different token header to bypass OAuth constraints. This approach works around current MCP limitations, including inconsistent support for deferred tool calling, instructions metadata, and events across different harnesses.

## Context

The post argues that the debate between CLI and MCP is unnecessary because both can coexist. Sentry’s unified experience bridges the gap by sharing authentication and allowing each tool to handle tasks it is best suited for. The CLI has a filesystem for tasks like grepping raw event logs, which MCP cannot do efficiently, while MCP provides native tool discovery and steering that the CLI lacks. The approach is a pragmatic solution to current limitations in MCP implementations.

## Approach / What changed

Sentry ships a unified CLI and MCP experience where the CLI command sentry mcp launches the MCP server in stdio mode with a shim that shares the CLI’s authentication credentials. The MCP server uses a different token header (Sentry-Bearer) to bypass the OAuth proxy’s CIMD/DCR constraints, allowing the CLI’s device code flow authentication to pass through. The MCP server can also inject steering into its responses to tell the agent how to use the CLI for tasks the MCP cannot efficiently handle.

## Takeaways

- Sentry’s unified CLI and MCP experience shares authentication by using a different token header (Sentry-Bearer) to bypass the OAuth proxy’s CIMD/DCR constraints.
- The CLI has a filesystem for tasks like grepping raw event logs, which MCP cannot do efficiently without server-side implementations.
- MCP implementations differ in tool search, deferred tool calling, and support for instructions metadata and events, making it hard to rely on features beyond basic tool calling.

## FAQ

### How does Sentry share authentication between CLI and MCP?

The \`sentry mcp\` command launches the MCP server in stdio mode with a shim that shares the CLI's authentication credentials. It uses a different token header (Sentry-Bearer) to bypass the OAuth proxy's CIMD/DCR constraints, so the CLI's device code flow authentication passes through.

### What can the CLI do that MCP cannot?

The CLI has a filesystem, allowing it to fetch raw event logs, grep through them, and paginate efficiently. MCP cannot do this without inefficient server-side implementations, so it relies on pre-aggregation and search APIs instead.

### What inconsistencies exist in MCP implementations?

MCP implementations differ in tool search, deferred tool calling, and support for instructions metadata and events. These inconsistencies make it hard for MCP server authors to rely on features beyond basic tool calling across different harnesses.

**Tags:** [Agentic AI](https://yomu.fyi/topic/agentic-ai), [Authentication](https://yomu.fyi/topic/authentication), [CLI](https://yomu.fyi/topic/cli), [MCP](https://yomu.fyi/topic/mcp)

- Source: [Sentry](https://blog.sentry.io/mcp-or-cli)
- Source URL: https://blog.sentry.io/mcp-or-cli
- Ingested by Yomu: 2026-11-10T21:00:14.245Z

[Read original post](https://blog.sentry.io/mcp-or-cli)
