Skip to main content
Glama
getsentry

Sentry MCP

Official
by getsentry

create_project

Create a new project in Sentry MCP, providing a unique SENTRY_DSN for error tracking. Define project name, team, platform, and organization for effective monitoring setup.

Instructions

Create a new project in Sentry, giving you access to a new SENTRY_DSN.

Use this tool when you need to:

  • Create a new project in a Sentry organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the project to create. Typically this is commonly the name of the repository or service. It is only used as a visual label in Sentry.
organizationSlugNoThe organization's slug. This will default to the first org you have access to.
platformNoThe platform for the project (e.g., python, javascript, react, etc.)
teamSlugYesThe team's slug. This will default to the first team you have access to.

Implementation Reference

  • The handler function that creates a new Sentry project using the apiService, optionally generates a client key (DSN), and returns formatted output with project details.
    async handler(params, context: ServerContext) {
      const apiService = apiServiceFromContext(context, {
        regionUrl: params.regionUrl ?? undefined,
      });
      const organizationSlug = params.organizationSlug;
    
      setTag("organization.slug", organizationSlug);
      setTag("team.slug", params.teamSlug);
    
      const project = await apiService.createProject({
        organizationSlug,
        teamSlug: params.teamSlug,
        name: params.name,
        platform: params.platform,
      });
      let clientKey: ClientKey | null = null;
      try {
        clientKey = await apiService.createClientKey({
          organizationSlug,
          projectSlug: project.slug,
          name: "Default",
        });
      } catch (err) {
        logIssue(err);
      }
      let output = `# New Project in **${organizationSlug}**\n\n`;
      output += `**ID**: ${project.id}\n`;
      output += `**Slug**: ${project.slug}\n`;
      output += `**Name**: ${project.name}\n`;
      if (clientKey) {
        output += `**SENTRY_DSN**: ${clientKey?.dsn.public}\n\n`;
      } else {
        output += "**SENTRY_DSN**: There was an error fetching this value.\n\n";
      }
      output += "# Using this information\n\n";
      output += `- You can reference the **SENTRY_DSN** value to initialize Sentry's SDKs.\n`;
      output += `- You should always inform the user of the **SENTRY_DSN** and Project Slug values.\n`;
      return output;
    },
  • Input schema definition for the create_project tool, specifying parameters like organizationSlug, teamSlug, name, platform using Zod.
    inputSchema: {
      organizationSlug: ParamOrganizationSlug,
      regionUrl: ParamRegionUrl.nullable().default(null),
      teamSlug: ParamTeamSlug,
      name: z
        .string()
        .trim()
        .describe(
          "The name of the project to create. Typically this is commonly the name of the repository or service. It is only used as a visual label in Sentry.",
        ),
      platform: ParamPlatform.nullable().default(null),
    },
  • Imports the createProject tool and registers it under the name 'create_project' in the tools index export.
    import createProject from "./create-project";
    import updateProject from "./update-project";
    import createDsn from "./create-dsn";
    import findDsns from "./find-dsns";
    import analyzeIssueWithSeer from "./analyze-issue-with-seer";
    import searchDocs from "./search-docs";
    import getDoc from "./get-doc";
    import searchIssues from "./search-issues";
    import useSentry from "./use-sentry";
    
    // Default export: object mapping tool names to tools
    export default {
      whoami,
      find_organizations: findOrganizations,
      find_teams: findTeams,
      find_projects: findProjects,
      find_releases: findReleases,
      get_issue_details: getIssueDetails,
      get_trace_details: getTraceDetails,
      get_event_attachment: getEventAttachment,
      update_issue: updateIssue,
      search_events: searchEvents,
      create_team: createTeam,
      create_project: createProject,
  • Defines the tool name as 'create_project' in the defineTool call.
    name: "create_project",
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the outcome ('giving you access to a new SENTRY_DSN') but doesn't disclose behavioral traits such as required permissions, rate limits, whether the operation is idempotent, or error handling. This is a significant gap for a mutation tool.

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

Conciseness4/5

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

The description is appropriately sized with two sentences and a bullet point, front-loaded with the main purpose. It avoids redundancy, though the bullet point could be integrated more smoothly for better flow.

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?

Given the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., permissions, side effects) and return values, leaving gaps for an AI agent to operate effectively.

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 adds no parameter-specific information beyond what's in the schema, resulting in a baseline score of 3 as it doesn't compensate but doesn't detract either.

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 verb ('Create') and resource ('new project in Sentry'), specifying it provides access to a new SENTRY_DSN. However, it doesn't explicitly differentiate from sibling tools like 'create_team' beyond mentioning the resource type, missing a direct comparison.

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

Usage Guidelines3/5

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

The description provides a bullet point stating 'Use this tool when you need to: - Create a new project in a Sentry organization,' which implies context but lacks explicit guidance on when to use alternatives (e.g., 'list_projects' for viewing existing ones) or prerequisites like required permissions.

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

Related 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/getsentry/sentry-mcp'

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