Sentry ACTION
List Project Issues.
Return a list of issues bound to a project. See the docs here
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Sentry account once, then configure and run List Project Issues. from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "sentry-list-project-issues",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
sentry: { authProvisionId: "apn_xxxxxxx" },
organizationSlug: "Organization",
projectId: "Project",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "sentry-list-project-issues",
"configured_props": {
"sentry": { "authProvisionId": "apn_xxxxxxx" },
"organizationSlug": "Organization",
"projectId": "Project"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "sentry",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "sentry-list-project-issues",
arguments: {
organizationSlug: "Organization",
projectId: "Project",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
organizationSlug Organization | string | The organization for which to consider issues events Required Dynamic |
projectId Project | string | The project to perform your action Required Dynamic |
statsPeriod Stats Period | string | An optional stat period (e.g. "24h", "14d"). Optional |
shortIdLookup Short ID Lookup | boolean | If this is set to true then short IDs are looked up by this function as well. This can cause the return value of the function to return an event issue of a different project which is why this is an opt-in. Optional |
query Query | string | An optional Sentry structured search query. If not provided an implied is:unresolved is assumed. Optional |
maxResults Max Results | integer | The maximum number of registers to return. Defaults to 1000. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- sentry-list-project-issues
- Version
- 0.1.3
- App
- Sentry
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗