---
title: "Sentry"
description: "Read organizations, projects, issues and event pages, and update one explicitly selected issue with a customer Sentry auth token. Native response data is returned under data alongside the provider paginationLink header;"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Sentry

<p>Read organizations, projects, issues and event pages, and update one explicitly selected issue with a customer Sentry auth token. Native response data is returned under data alongside the provider paginationLink header; links are never followed automatically. This six-command subset targets sentry.io only and excludes self-hosted instances, bulk changes and event ingestion. Account role and token scopes still apply.</p>

<details data-command-index><summary>What you can do (6)</summary>
<h2>What you can do</h2>
<p>Available commands: 6 (5 read, 1 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/sentry#command-sentry-organizations-list">List one page of accessible organizations</a> — <code>sentry.organizations.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sentry#command-sentry-projects-list">List one page of organization projects</a> — <code>sentry.projects.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sentry#command-sentry-issues-list">List one explicit page of project issues</a> — <code>sentry.issues.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sentry#command-sentry-issues-get">Read one issue</a> — <code>sentry.issues.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sentry#command-sentry-issues-update">Update explicitly selected issue state</a> — <code>sentry.issues.update</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/sentry#command-sentry-events-list">List one explicit page of issue events</a> — <code>sentry.events.list</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/sentry">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Sentry, then enter the issued values in the connection form below.</p>
<ol>
<li>In Sentry, create a user auth token under User settings → Auth Tokens, or use an authorized internal integration token following the official authentication guide. Grant only needed org:read, project:read and event:read scopes; changing issues also requires event:write and the corresponding account role. Paste it into this connection’s Sentry API token field. Start with organizations.list and projects.list; use native slugs and issue IDs. Results contain data and paginationLink; pass a next cursor explicitly rather than fetching the link automatically. This connection uses sentry.io, not a self-hosted instance. Save selected commands and create a separate scoped Tooluse.net API key; never expose the Sentry token in the MCP URL.</li>
</ol>
<p><a href="https://docs.sentry.io/api/auth/">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Sentry API token</td>
<td>Required</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-sentry-organizations-list">
<summary><span>List one page of accessible organizations — <code>sentry.<wbr>organizations.<wbr>list</code></span></summary>
<p>Run <strong>List one page of accessible organizations</strong> with Sentry. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sentry?command=sentry.organizations.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.cursor</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sentry/commands/sentry.organizations.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sentry-projects-list">
<summary><span>List one page of organization projects — <code>sentry.<wbr>projects.<wbr>list</code></span></summary>
<p>Run <strong>List one page of organization projects</strong> with Sentry. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sentry?command=sentry.projects.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.organizationSlug</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.cursor</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sentry/commands/sentry.projects.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "organizationSlug": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sentry-issues-list">
<summary><span>List one explicit page of project issues — <code>sentry.<wbr>issues.<wbr>list</code></span></summary>
<p>Run <strong>List one explicit page of project issues</strong> with Sentry. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sentry?command=sentry.issues.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.organizationSlug</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>path.projectSlug</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.cursor</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>query.query</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.statsPeriod</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.sort</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;date&quot;,&quot;new&quot;,&quot;priority&quot;,&quot;freq&quot;,&quot;user&quot;]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sentry/commands/sentry.issues.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "organizationSlug": "example",
    "projectSlug": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sentry-issues-get">
<summary><span>Read one issue — <code>sentry.<wbr>issues.<wbr>get</code></span></summary>
<p>Run <strong>Read one issue</strong> with Sentry. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sentry?command=sentry.issues.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.issueId</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sentry/commands/sentry.issues.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "issueId": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sentry-issues-update">
<summary><span>Update explicitly selected issue state — <code>sentry.<wbr>issues.<wbr>update</code></span></summary>
<p>Run <strong>Update explicitly selected issue state</strong> with Sentry. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sentry?command=sentry.issues.update">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.issueId</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>body.status</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;resolved&quot;,&quot;unresolved&quot;,&quot;ignored&quot;]</code></td>
</tr>
<tr>
<td><code>body.hasSeen</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.isBookmarked</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.isSubscribed</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sentry/commands/sentry.issues.update">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "issueId": "example"
  },
  "body": {
    "status": "resolved"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-sentry-events-list">
<summary><span>List one explicit page of issue events — <code>sentry.<wbr>events.<wbr>list</code></span></summary>
<p>Run <strong>List one explicit page of issue events</strong> with Sentry. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/sentry?command=sentry.events.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.issueId</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.cursor</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/sentry/commands/sentry.events.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "issueId": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://docs.sentry.io/api/">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/sentry/index.mdx