Skip to main content
Glama
PhialsBasement

GitHub MCP Server Plus

create_repository

Create a new GitHub repository in your account with customizable settings for name, description, privacy, and initialization.

Instructions

Create a new GitHub repository in your account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRepository name
descriptionNoRepository description
privateNoWhether the repository should be private
autoInitNoInitialize with README.md

Implementation Reference

  • Core handler function that executes the GitHub API POST request to /user/repos to create the repository.
    export async function createRepository(options: CreateRepositoryOptions) {
      const response = await githubRequest("https://api.github.com/user/repos", {
        method: "POST",
        body: options,
      });
      return GitHubRepositorySchema.parse(response);
    }
  • Zod schema defining the input parameters for the create_repository tool.
    export const CreateRepositoryOptionsSchema = z.object({
      name: z.string().describe("Repository name"),
      description: z.string().optional().describe("Repository description"),
      private: z.boolean().optional().describe("Whether the repository should be private"),
      autoInit: z.boolean().optional().describe("Initialize with README.md"),
    });
  • index.ts:78-82 (registration)
    Tool registration in the list of available tools returned by ListToolsRequestHandler.
    {
      name: "create_repository",
      description: "Create a new GitHub repository in your account",
      inputSchema: zodToJsonSchema(repository.CreateRepositoryOptionsSchema),
    },
  • Dispatcher handler in the CallToolRequestHandler switch statement that parses arguments and delegates to the core createRepository function.
    case "create_repository": {
      const args = repository.CreateRepositoryOptionsSchema.parse(request.params.arguments);
      const result = await repository.createRepository(args);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a write operation, the description doesn't mention authentication requirements, rate limits, what happens on success/failure, or whether this is a destructive operation that creates permanent resources. It lacks essential context for safe and effective use.

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?

The description is a single, clear sentence with zero wasted words. It's perfectly front-loaded and communicates the core purpose immediately without unnecessary elaboration.

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 write operation with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (what's returned), authentication needs, error conditions, or how this differs from similar tools like fork_repository. The context signals indicate this is a non-trivial operation that requires more guidance.

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?

With 100% schema description coverage, the schema already documents all 4 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. This meets the baseline expectation when schema coverage is high.

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') and resource ('new GitHub repository in your account'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'fork_repository' or explain why to use create_repository versus fork_repository when both create repositories.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like authentication), when to use create_repository versus fork_repository, or any limitations (like rate limits or account restrictions).

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/PhialsBasement/mcp-github-server-plus'

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