Investigate issues and events with source evidence. Read project context before changing an explicitly selected issue's state.
Example workflows
Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.
Investigate a production issue
Read the Sentry issue I identify by issue ID. Summarize the error, affected release context and available evidence. Suggest a focused investigation and distinguish hypotheses from facts. Do not resolve, ignore or reassign the issue.
Explore this command: sentry.issues.get
Prepare project triage
Read one page of issues for the Sentry organization and project slugs I provide. Prioritize investigation using the returned issue evidence and include issue links. Do not update an issue or fetch additional pages without asking.
Explore this command: sentry.issues.list
What you can do (6)
What you can do
Available commands: 6 (5 read, 1 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List one page of accessible organizations — sentry.organizations.list |
Read |
List one page of organization projects — sentry.projects.list |
Read |
List one explicit page of project issues — sentry.issues.list |
Read |
Read one issue — sentry.issues.get |
Read |
Update explicitly selected issue state — sentry.issues.update |
Write |
List one explicit page of issue events — sentry.events.list |
Read |
Connect and use
This connection uses your provider account.
Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.
Get your provider credentials
Follow these steps for Sentry, then enter the issued values in the connection form below.
- 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.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Sentry API token | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
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's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
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.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
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.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
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.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
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.
HTTP call
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": {}
}'
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.
Commands
List one page of accessible organizations — sentry.organizations.list
List one page of accessible organizations
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
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.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Optional | additionalProperties: false |
|
query.cursor |
string | Optional | ||
query.per_page |
integer | Optional | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
List one page of organization projects — sentry.projects.list
List one page of organization projects
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
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.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.organizationSlug |
string | Required | minLength: 1 |
|
query |
object | Optional | additionalProperties: false |
|
query.cursor |
string | Optional | ||
query.per_page |
integer | Optional | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{
"path": {
"organizationSlug": "example"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
List one explicit page of project issues — sentry.issues.list
List one explicit page of project issues
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
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.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.organizationSlug |
string | Required | minLength: 1 |
|
path.projectSlug |
string | Required | minLength: 1 |
|
query |
object | Optional | additionalProperties: false |
|
query.cursor |
string | Optional | ||
query.per_page |
integer | Optional | minimum: 1; maximum: 100 |
|
query.query |
string | Optional | ||
query.statsPeriod |
string | Optional | ||
query.sort |
string | Optional | enum: ["date","new","priority","freq","user"] |
Full JSON Schema
Example input
{
"path": {
"organizationSlug": "example",
"projectSlug": "example"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read one issue — sentry.issues.get
Read one issue
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
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.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.issueId |
string | Required | minLength: 1 |
Full JSON Schema
Example input
{
"path": {
"issueId": "example"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Update explicitly selected issue state — sentry.issues.update
Update explicitly selected issue state
This operation can change provider data. Review the input before allowing an agent to call it.
Parameters
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.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.issueId |
string | Required | minLength: 1 |
|
body |
object | Required | additionalProperties: false |
|
body.status |
string | Optional | enum: ["resolved","unresolved","ignored"] |
|
body.hasSeen |
boolean | Optional | ||
body.isBookmarked |
boolean | Optional | ||
body.isSubscribed |
boolean | Optional |
Full JSON Schema
Example input
{
"path": {
"issueId": "example"
},
"body": {
"status": "resolved"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
List one explicit page of issue events — sentry.events.list
List one explicit page of issue events
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
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.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.issueId |
string | Required | minLength: 1 |
|
query |
object | Optional | additionalProperties: false |
|
query.cursor |
string | Optional | ||
query.per_page |
integer | Optional | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{
"path": {
"issueId": "example"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client'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.