Product and engineering

The GitHub connector.

Repositories, pull requests, issues, commits. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.

How access is governed

6

Read tools

Open by default. They run when called, and every call is logged with the endpoint, tool and capability.

0

Write tools

GitHub exposes no write tools. Nothing it does mutates external state.

0

Destructive tools

GitHub defines no destructive tools. Nothing here deletes data.

Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.

Every GitHub tool

6 tools, named as the agent sees them.

  • list_reposread

    List repositories the token can access, most recently pushed first.

  • list_issuesread

    List issues in a repository (pull requests are excluded).

  • get_issueread

    Get one issue with its full body.

  • list_pull_requestsread

    List pull requests in a repository.

  • get_pull_requestread

    Get one pull request with its full body, mergeability, and diff stats.

  • list_commitsread

    List recent commits on a repository branch.

Use it from any agent

The same GitHub tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.

.mcp.json · works for Cursor and Claude Desktop too
{
  "mcpServers": {
    "growth": {
      "type": "http",
      "url": "https://app.notara.ai/mcp/g/acme/growth",
      "headers": {
        "Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

The URL and token are placeholders. Real endpoints are issued per group from the dashboard.

Setup

  1. 01

    Create a GitHub Personal Access Token in your GitHub account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.

  2. 02

    Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.

  3. 03

    The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.

More in product and engineering

LinearCursorSentryAsanaClickUpNotion

Connect GitHub once. Use it everywhere.

Use Notara directly, or bring us the workflow that needs to be redesigned and built.

Book a callSign in