---
title: "Knit - MCP Servers GitHub"
description: "Knit's GitHub MCP Server gives your AI agents instant, code-free access to every GitHub API endpoint-read, write, and automate without OAuth headaches or custom endpoints."
source_url: "https://www.getknit.dev/mcp-servers/github-mcp-server"
page_type: "mcp-server"
---

_This page is part of Knit's MCP server directory. It describes the GitHub MCP Server, which gives AI agents direct, code-free access to the GitHub API through Knit._

# Knit - MCP Servers GitHub

## **GitHub** MCP Server - Integrate your Agent with **GitHub** in Minutes

Knit's GitHub MCP Server gives your AI agents instant, code-free access to every GitHub API endpoint-read, write, and automate without OAuth headaches or custom endpoints.

### Installing GitHub MCP Server
Watch an agent automate workflows-all with knit's plug-and-play MCP Servers.

## Key Features

All the power of AI-ready tools-serverless hosting, mix-and-match APIs, live updates, semantic search, and built-in auth-in a single, plug-and-play platform.

#### Serverless by Default

Spin up MCP Servers with zero infrastructure-Knit scales, patches, and monitors everything for you.

#### Plug-In Your Own APIs

Expose custom endpoints as AI-ready tools alongside knit's catalog, unifying proprietary logic and third-party apps in one place.

#### Hot-Swap Tools at Runtime

Add or remove tools without downtime; your agents see new capabilities instantly-no server restarts required.

#### Mix-and-Match Tool Bundles

Deploy only the API tools you need from any app in a single lightweight server-no bloat, no duplication.

#### Semantic Tool Search

Natural-language search surfaces the right tools for each use case, shrinking token costs and boosting LLM accuracy.

#### Auth Handled for You

OAuth, SAML, service accounts-Knit manages credentials and refreshes so your team never wrestles with tokens.

### Actions available via GitHub MCP Server
*   Unified Action

#### Get Ticket By ID

The Get Ticket By ID API retrieves the details of a specific ticket using its ID. The request requires the ticket ID as a path parameter. The response includes comprehensive details about the ticket such as its creation and update timestamps, name, assigned user, creator, due date, status, description, type, associated account, project, group, contact IDs, priority, source, URL, tags, and any custom fields.

*   Unified Action

#### Get List of All Tags in the System

This API retrieves a list of all tags that can be applied to a ticket in the system. It supports pagination through the use of a 'cursor' query parameter. The response includes pagination details and an array of tags, each with an ID and name.

*   Unified Action

#### Get List of All Groups or Teams in the System

This API retrieves a list of all groups or teams in the system. It supports pagination through a 'cursor' query parameter. The response includes pagination information and details of each group, such as the group ID, name, description, whether it is public, and the list of user IDs belonging to the group.

*   Unified Action

#### Get Contact or Person Details by ID

This API retrieves the details of a particular contact or person in the system using their contact ID. The request requires the contact ID as a path parameter. The response includes the contact's ID, name, creation date, email address, phone number, and the account ID to which the contact belongs.

*   Unified Action

#### Add Comments for a Ticket

This API is used to add comments, conversations, or notes along with attachments for a particular ticket. The request body requires a 'ticketId' to specify the ticket for which the comment is being added. Optional fields include 'body' for the comment text, 'isPublic' to indicate if the comment is public, 'author' to specify the author of the comment, 'attachments' for any files to be attached, and 'metadata' for any additional fields. The response returns the 'id' of the newly created comment.

*   Unified Action

#### Create Ticket

The Create Ticket API is used to create a new ticket in the system. It requires several parameters in the request body, including the ticket name, assigned user ID, creator user ID, due date, description, ticket type ID, account ID, project ID, group ID, contact IDs, priority, source, tags, and additional metadata. The request must include headers for content type and authorization. Upon successful creation, the API returns the ticket ID in the response body.


## Related pages

- [Ticketing MCP servers category](https://md.getknit.dev/mcp-servers-categories/ticketing-mcp-servers)
- [GitHub LLM Tools](https://md.getknit.dev/llm-tool/github)
- [Unified Ticketing API](https://md.getknit.dev/integration-categories/ticketing-api)
- [How Knit works](https://md.getknit.dev/how-knit-works)