# Connect GitHub to ChatGPT with OpenAI models and the Agent200 SDK

> ChatGPT cannot send an API key to a custom MCP server, so this guide builds GitHub into your own agent with OpenAI's models and the Agent200 SDK.

- Page: https://www.agent200.com/tools/github/framework/chatgpt/
- Connector: [GitHub](https://www.agent200.com/tools/github.md)
- Framework: ChatGPT
- Updated: 2026-11-15

## Instructions for AI agents

Goal: connect GitHub to ChatGPT with Agent200.
Guide: https://www.agent200.com/tools/github/framework/chatgpt/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Make sure GitHub is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Give every request a stable id for the end user. Agent200 uses only that user's own connections.
5. Connect the user's GitHub account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on GitHub.
6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "github" in the tools. The model decides when a GitHub tool is needed; Agent200 executes the call.
7. Check it works with this request: "List the open bugs assigned to me"
   What should come back:
   - An answer in `result.output`, built from the user's own GitHub data.
   - Behind the scenes, the model calls a GitHub tool, such as `github_search_issues`, and Agent200 runs it.
8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in GitHub, then retry.

The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## Overview

ChatGPT can add custom MCP servers, but it signs in to them only with OAuth or with no sign-in, and cannot send an API key. Agent200's MCP server uses your API key, so this guide takes the SDK route: you build GitHub into your own agent with OpenAI's models, through Agent200.

Your agent then calls the GitHub tools with each user's own GitHub connection: Agent200 runs the OAuth flow, stores the tokens and keeps them fresh.

- **Connector:** [GitHub](https://www.agent200.com/tools/github/)
- **Works with:** ChatGPT · Your own agent code
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [4 tools](https://www.agent200.com/tools/github/framework/chatgpt/#tools)
- **Model in examples:** `openai/gpt-5.6-sol`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **GitHub enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a GitHub account.** They approve access once, on GitHub's own page.
- **A model for your agent.** The examples use openai/gpt-5.6-sol, through the same Agent200 API key.

## Connect GitHub to ChatGPT

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. Copy the key and store it as an environment variable, AGENT200_API_KEY, or in your secrets manager. One key covers GitHub and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.

Create an API key: https://agent200.com/platform/apikeys/

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Set up the Agent200 SDK

Add the SDK to your project and create a client with the key from the environment.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Let your user connect GitHub

Each end user authorizes their own GitHub account once, through managed OAuth. If the user has not connected yet, Agent200 returns an authorization link: show it to them, and they approve access on GitHub's own page. Agent200 handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own GitHub account, once.
const connection = await agent200
  .user("user_123")
  .connect("github");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 4: Run with the GitHub tools

Name the user, the model and GitHub in the tools. The model decides when a GitHub tool is needed, and Agent200 executes the call with the user's own connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "List the open bugs assigned to me",
    tools: ["github"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Test your connection

Ask: "List the open bugs assigned to me"

What should come back:

- An answer in `result.output`, built from the user's own GitHub data.
- Behind the scenes, the model calls a GitHub tool, such as `github_search_issues`, and Agent200 runs it.

If Agent200 returns an authorization link instead, the user has not connected GitHub yet. Go back to the connect step.

## GitHub tools ChatGPT can call

- **Search issues** (`github_search_issues`, read): Find issues and pull requests.
- **Create an issue** (`github_create_issue`, write): Open an issue in a repository.
- **Read a file** (`github_get_content`, read): Read a file from a repository.
- **Comment** (`github_create_comment`, write): Comment on an issue or pull request.

## How it works

1. **Your app sends the request.** It calls Agent200 with the model, instructions, the input, the end user's id and the GitHub tools.
2. **The model picks a tool.** The model decides whether a GitHub tool is needed, and with which arguments.
3. **Agent200 runs the call.** It uses that user's own GitHub connection, within the endpoints and scopes your project allows, and returns the result to the model.
4. **Your app gets the result.** Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's GitHub account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and GitHub enforces what its API grants.

## Troubleshooting

### Why not add Agent200 to ChatGPT as an MCP server?

ChatGPT’s custom MCP servers sign in with OAuth or with no sign-in, and cannot send an API key. Agent200’s MCP server uses your API key, so for ChatGPT users the SDK route on this page is the one that works.

### The request says GitHub authorization is required

The end user has not connected GitHub yet, or the connection needs to be approved again. Agent200 returns an authorization link: show it to the user, let them approve access on GitHub's own page, then run the request again.

### ChatGPT does not use the GitHub tools

Check that GitHub is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming GitHub in the request, or in the instructions, also helps the model choose the right tool.

### A tool call is refused or returns less than expected

Agent200 runs only what your project allows (services, endpoints and scopes), and GitHub returns only what the end user authorized. Widen the endpoints or scopes in the dashboard if the agent needs more, then ask the user to connect GitHub again so they can approve the new access.

### The results come from the wrong account

Every request names an end user (`user_123` in the examples). Pass the id of the person your agent is working for: Agent200 then uses only that user's GitHub connection, never another user's.

### The API key was pasted into a chat or committed

Create a new key on the [API keys page](https://agent200.com/platform/apikeys/), update `AGENT200_API_KEY` wherever your app reads it, and stop using the old one. Keep keys in environment variables or a secrets manager, never in prompts, chats or source control.

## Use GitHub with another framework

- [GitHub + OpenAI Agents SDK](https://www.agent200.com/tools/github/framework/openai-agents-sdk.md)
- [GitHub + Claude](https://www.agent200.com/tools/github/framework/claude.md)
- [GitHub + Claude Code](https://www.agent200.com/tools/github/framework/claude-code.md)
- [GitHub + Muse](https://www.agent200.com/tools/github/framework/muse.md)
- [GitHub + Grok Bot](https://www.agent200.com/tools/github/framework/grok-bot.md)
- [GitHub + OpenAI Dots](https://www.agent200.com/tools/github/framework/openai-dots.md)
- [GitHub + Claude Duet](https://www.agent200.com/tools/github/framework/claude-duet.md)
- [GitHub + Hermes Agent](https://www.agent200.com/tools/github/framework/hermes-agent.md)
- [GitHub + OpenClaw](https://www.agent200.com/tools/github/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
