MCP has no code mapping or repository tools

Open
#2,137 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start in packages/mcp-core/src/tools/catalog/ and read update-project.ts and permissions.ts to understand the existing tool and scope patterns. Compare them with the cited Sentry API endpoints for code mappings and repository deletion. Done means agents can perform the requested mapping and repository operations through MCP with the required scopes; the issue does not specify detailed tool behavior or tests.

Written by the indexing model from the issue text.

Description

An agent using the hosted MCP could not move a project's code mappings from a GitHub repo to a GitLab repo and remove the GitHub repo: no MCP tool lists, creates, updates, or deletes code mappings, or removes a repository. update_project only takes name, slug, and platform. Reported through MCP feedback MCP-SERVER-GN1 (Claude, impact blocked).

MCP side (toolkit bb046c7)

  • No catalog tool in packages/mcp-core/src/tools/catalog/ calls /code-mappings/ or /repos/.
  • update-project.ts:28-79: name, slug, platform only.
  • The MCP scope set (permissions.ts:13-30) has no org:integrations, and no catalog tool requires org:admin.

Sentry API (getsentry/sentry 99c124e)

Related

  • The CLI-first MCP work (#1899, #1916) marks sentry api as exposed on hosted MCP, which would give agents a raw path to these endpoints. The CLI itself has only code-mappings upload (stdio-only in #1916) and repo list.

via @sergical.

--

View Session [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.