Skip to main content
Glama
diegofornalha

MCP Sentry para Cursor

sentry_create_project

Create a new Sentry project to track deployments, releases, and application health metrics for error monitoring and performance insights.

Instructions

Create a new project in Sentry. Track deployments, releases and health metrics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
slugYesProject slug (URL-friendly identifier)
platformNoPlatform (e.g., 'javascript', 'python', 'node')
teamYesTeam slug

Implementation Reference

  • MCP tool handler for 'sentry_create_project' that validates apiClient, extracts parameters (name, slug, platform, team), calls SentryAPIClient.createProject, and returns formatted project details.
    case "sentry_create_project": {
      if (!apiClient) {
        throw new Error("Sentry API client not initialized. Provide auth token.");
      }
      
      const { name, slug, platform = "javascript", team } = args as any;
      const project = await apiClient.createProject({ name, slug, platform, team });
      
      return {
        content: [
          {
            type: "text",
            text: `Project created successfully:\n` +
              `- Name: ${project.name}\n` +
              `- Slug: ${project.slug}\n` +
              `- ID: ${project.id}\n` +
              `- Platform: ${project.platform}\n` +
              `- Status: ${project.status}`,
          },
        ],
      };
    }
  • src/index.ts:570-595 (registration)
    Tool registration in ListToolsRequestSchema handler, defining name, description, and input schema requiring name, slug, team with optional platform.
    {
      name: "sentry_create_project",
      description: "Create a new project in Sentry. Track deployments, releases and health metrics.",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "Project name",
          },
          slug: {
            type: "string",
            description: "Project slug (URL-friendly identifier)",
          },
          platform: {
            type: "string",
            description: "Platform (e.g., 'javascript', 'python', 'node')",
          },
          team: {
            type: "string",
            description: "Team slug",
          },
        },
        required: ["name", "slug", "team"],
      },
    },
  • Input schema defining properties and requirements for the sentry_create_project tool.
      type: "object",
      properties: {
        name: {
          type: "string",
          description: "Project name",
        },
        slug: {
          type: "string",
          description: "Project slug (URL-friendly identifier)",
        },
        platform: {
          type: "string",
          description: "Platform (e.g., 'javascript', 'python', 'node')",
        },
        team: {
          type: "string",
          description: "Team slug",
        },
      },
      required: ["name", "slug", "team"],
    },
  • Core helper method in SentryAPIClient that sends POST request to Sentry API endpoint /teams/{org}/{team}/projects/ with project data to create the project.
    async createProject(data: any) {
      return this.request(`/teams/${this.org}/${data.team}/projects/`, {
        method: 'POST',
        body: JSON.stringify(data),
      });
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden. It states 'Create' (implying a write/mutation operation) but doesn't disclose behavioral traits like required permissions, whether it's idempotent, what happens on duplicate slugs, rate limits, or what the response contains. The mention of tracking capabilities adds some context but doesn't cover critical mutation behaviors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences that efficiently convey the core purpose and value. First sentence states the action, second adds context about capabilities. No wasted words or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool (create operation) with no annotations and no output schema, the description is insufficient. It doesn't explain what gets returned, error conditions, side effects, or dependencies. The tracking capabilities mention adds some value but doesn't compensate for missing behavioral transparency needed for a write operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all 4 parameters. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., doesn't explain relationships between name/slug, platform options, or team requirements). Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create a new project') and resource ('in Sentry'), with additional context about what the project enables ('Track deployments, releases and health metrics'). It distinguishes from siblings like sentry_list_projects (list vs create) but doesn't explicitly differentiate from sentry_setup_project, which might have overlapping functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. While the description implies this is for initial project creation, it doesn't mention prerequisites (e.g., needing an organization or team first), when not to use it (e.g., for updating existing projects), or clarify its relationship with sentry_setup_project.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/diegofornalha/sentry-mcp-cursor'

If you have feedback or need assistance with the MCP directory API, please join our Discord server