Integration · Automate and collaborate

GitHub and Meteor AI agents

Connect GitHub to a WhatsApp Met: search and create issues, comment, review pull requests and check releases with GitHub's official MCP.

Book a demo See every integration

How does GitHub connect to Meteor?

With the GitHub ready connector, your Met uses GitHub's official MCP server with a personal token the admin creates. It searches repositories, reads files, commits, branches, tags and published releases, and reviews issues and pull requests with their comments and checks. It also creates or updates issues and comments on them. That way the bug a customer reports on WhatsApp becomes an issue in the right repository, and the Met can tell them which release shipped the fix. It works with the token's permissions: what the token cannot see, the Met cannot see either.

What it automates

What a Meteor Met does with GitHub

Log the bug a customer reports

When a customer says on WhatsApp that something fails in your app or site, the Met checks whether an issue with that problem already exists and, if not, creates one in the repository with what the customer said.

Say which release shipped a fix

If the customer asks whether it was fixed, the Met reviews the issue, the pull request that closed it and the published releases, and tells them which one shipped the change.

Add repeated reports

If another customer reports the same thing, the Met comments on the existing issue instead of duplicating it, so the team sees how many people have the problem.

Tell the owner what changed

When the owner asks what was published this week, the Met lists the repository's commits and pull requests and sums up the changes in plain words.

20 tools

Everything your Met can ask GitHub for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`get_me`	Gets the profile of the GitHub user who owns the connected token.
`search_repositories`	Searches repositories with GitHub's advanced search syntax.
`get_file_contents`	Gets the contents of a file or a folder in a repository.
`list_branches`	Lists the branches of a repository.
`list_commits`	Lists a repository's commits, with filters by author, file and dates.
`get_commit`	Gets a commit's details, with the files it changed.
`search_code`	Searches code in repositories with GitHub code search.
`list_tags`	Lists the tags of a repository.
`list_releases`	Lists the published releases of a repository.
`get_latest_release`	Gets the latest published release of a repository.
`get_release_by_tag`	Gets a published release from its tag name, for example v1.0.0.
`list_issues`	Lists a repository's issues, with filters by state, labels and date.
`search_issues`	Searches issues with a natural language query, in one repository or in general.
`issue_read`	Gets an issue with its details, comments, sub-issues or labels.
`issue_write`	Creates or updates an issue or a pull request.
`add_issue_comment`	Adds a comment or a reaction to an issue or a pull request.
`list_issue_types`	Lists the issue types available in a repository or an organization.
`list_pull_requests`	Lists a repository's pull requests, with filters by state and branch.
`search_pull_requests`	Searches pull requests with GitHub's pull request search syntax.
`pull_request_read`	Gets a pull request with its details, diff, files, commits, reviews or checks.

The limits

What the GitHub integration does NOT do

We would rather say it here than have you find out during rollout.

It does not ask you for confirmation in the chat before writing. The admin decides in Connections which actions stay on.
The server has more tools than this page. Writing or pushing files, creating or forking repositories, merging pull requests and deleting a file or a repository start turned off until the admin turns them on. Creating branches and opening or editing pull requests arrive on; if the Met does not need them, the admin turns them off.
It does not see more than the token. It works with the permissions of the personal token you pasted: if the token only has access to two repositories, the Met only sees those two.
It does not include the Actions, security, notifications or projects tools. The address Met uses serves the default group: context, repositories, issues, pull requests and users.
It does not pay your GitHub plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect GitHub

1

A GitHub account with access to the repositories

The account your team uses for the app's or site's repositories. The token comes from that account.
2

A personal GitHub token pasted in Met

In GitHub, open Settings → Developer settings → Personal access tokens and create a token with access only to the repositories the Met will use. In Met, open Connections → GitHub → Connect and paste it. Then you choose which actions stay on.

Frequently asked questions

Questions about GitHub and Meteor

A personal GitHub token created in Settings → Developer settings → Personal access tokens, with access only to the repositories the Met needs. That limits what it can see and touch.

The server has those tools, but merging pull requests, pushing files and creating or updating files start turned off until the admin turns them on in Connections. This page does not use them; if your Met only serves customers, leave them off.

Yes, if the token has access to them. The Met sees exactly the repositories the token allows, not one more.

You do, with your GitHub account and plan. Meteor does not resell GitHub or charge for the actions your Met takes there.

Step by step