Skip to main content
Glama
varity-labs

Varity MCP Server

Official
by varity-labs

Create GitHub Repository

varity_create_repo
Destructive

Creates a GitHub repository and pushes your local project code to it for dynamic deployments, or generates a repo from a SaaS template when no path is given.

Instructions

Create a new GitHub repository and push the current project to it. For custom apps (the primary use case): pass the 'path' parameter with the local project directory, this creates an empty repo and pushes your actual code to GitHub. The GitHub URL is required for dynamic deployments, always call this before varity_deploy. For template-based quick-start: omit 'path' to create from the Varity SaaS template. Requires a GitHub personal access token (classic) with repo scope from https://github.com/settings/tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRepository name (lowercase, hyphens allowed, e.g. 'my-app')
pathNoAbsolute path to the local project directory to push to GitHub (e.g. '/home/user/my-app'). When provided, pushes the actual project code. Required for custom apps that will use varity_deploy with dynamic hosting. If omitted, creates a repo from the Varity SaaS template instead.
visibilityNoRepository visibilitypublic
descriptionNoShort description of your app (optional)
github_tokenNoGitHub personal access token (optional if GITHUB_TOKEN env var is set). Needs 'repo' scope.
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses that the tool creates an empty repo and pushes actual code, or creates from a SaaS template if no path is given. It also mentions the need for a GitHub token and the requirement to call before varity_deploy, providing critical behavioral context.

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 well-structured: a concise opening sentence, then a logical breakdown of two use cases, followed by a deployment ordering note, and finally a token requirement. Every sentence is informative and front-loaded, with no redundancy.

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

Completeness4/5

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

The description covers preconditions, use cases, and side effects well for a creation tool with no output schema. However, it does not explicitly state what the tool returns (e.g., the repository URL), which would be beneficial for the agent to know that it can capture the output for use in subsequent commands.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant meaning: it explains the dual behavior of the 'path' parameter (push code vs. template), clarifies that 'name' must be lowercase and hyphens allowed, and notes that 'github_token' can come from an environment variable. This enriches the schema's descriptions.

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

Purpose5/5

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

The description clearly states the tool's purpose: creating a GitHub repository and pushing code. It distinguishes two primary use cases (custom apps with path vs. template without path), and differentiates from sibling tools by specifying its role in dynamic deployments before varity_deploy.

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

Usage Guidelines5/5

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

The description provides explicit guidelines: when to use path (custom apps) vs. omit path (template quick-start), and when to call before varity_deploy. It also states the prerequisite of a GitHub token with repo scope, covering when and how to use the tool effectively.

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/varity-labs/varity-mcp'

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