Spike: run the CLI SDK on workerd
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cloud, nodejs, sqlite, typescript
- Domain
- backend-api-design, cli
Research direction
Start with the cli-first-mcp task 6.1 design document linked in the issue, then find where createSentrySDK() and the exposed commands are assembled. Bundle them for workerd with nodejs_compat and the current compatibility date, then try a few read commands with a token and SQLite stubbed out. Record bundle or runtime failures by module and command, compare bundle size with the Workers script limit, and update the design document with findings and any stdio-only commands.
Written by the indexing model from the issue text.
Description
Part of #1357. Plan: cli-first-mcp task 6.1 (design).
Why
The hosted MCP will run commands through createSentrySDK(), one instance per request, with the OAuth grant's token and persistence off. Whether the exposed commands bundle and run under nodejs_compat is unknown until we build it. This can start now; it doesn't depend on the API client move.
Scope
- Bundle
createSentrySDK()with the exposed commands for workerd, undernodejs_compatand a current compatibility date.mcp-cloudflareis on 2025-03-21 today. - Run a few read commands with a token and SQLite stubbed out.
- Record what fails to bundle or run (by module and by command) and the bundle size against the Workers script limit, in the
cli-first-mcpdesign.
Done when
- The findings are in the design doc, and blocked commands are marked stdio-only (or filed if they look fixable).
via @BYK.
--
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/toolkit
-
MCP mcp-feedback-pattern
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/toolkit#2276 · 1 comment ·
Maintainers usually reply within 1 day
-
CLI enhancement MCP
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
getsentry/toolkit#1908 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
getsentry/toolkit#1471 · 1 comment ·
Maintainers usually reply within 1 day
-
get_sentry_resource gives no guidance for Explore > Errors list URLsPossibly taken @sentry-junior claimed this today. OpenMCP mcp-feedback-pattern
Difficulty 2/5 1-3 hours Newbie friendliness 32/100
getsentry/toolkit#2278 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
getsentry/toolkit#2275 · 1 comment ·
Maintainers usually reply within 1 day
All issues in getsentry/toolkit
Similar issues
-
Add: BOM CineOpenapproved check:passed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug platform-android
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Termix-SSH/Mobile#146 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
devswha/herdr-web-ui#3875 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100