Return markdown from MCP command calls

Open
#1,892 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
57/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Start with the linked design and task plan for cli-first-mcp, especially task 3.4, then inspect the MCP execute tools and the issue view and trace view tests. Confirm which commands expose a markdown renderer and how format: "markdown" is handled. Done means tests cover markdown output for both views.

Written by the indexing model from the issue text.

Description

CLI enhancement MCP

Part of #1357. Plan: cli-first-mcp task 3.4 (design, tasks). Depends on #1890.

Catalog tools format stack traces, traces, and issue summaries for agents. format: "markdown" on the execute tools returns the command's plain markdown output instead of JSON, for commands with a markdown renderer.

Done when

  • Tests for issue view and trace view in markdown.

via @BYK.

--

View Session in Sentry

Dominant language
TypeScript
Stars
961
Forks
179
Avg merge
15h 33m
Merged PRs (30d)
476

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/toolkit

All issues in getsentry/toolkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.