Connect Codex to GitHub MCP for a Read-Only Issue Check

This is an advanced builder lesson. It uses Codex MCP support and GitHub’s official MCP server documentation to set up a bounded, read-only check. The example is illustrative. It does not claim that this connection was run by Cihan or that a particular issue was returned.

What you need

You need Codex CLI or the Codex IDE extension, access to a GitHub repository, and permission to configure an MCP server. OpenAI documents STDIO and Streamable HTTP MCP servers, including bearer or OAuth authentication. GitHub documents a hosted remote MCP server and a Codex installation guide. Availability, scopes, and prompts can change, so read the current provider pages before setup.

If you do not need a live connection, use GitHub’s web interface and copy one issue into a normal chat. That is the no-code alternative and avoids granting an MCP client account access.

Safe sample task

Use a repository you own or a test repository. Ask for issue number 12 in example-org/example-repo. Do not begin with write actions, private repositories, or production automation.

Steps

Read the current Codex MCP documentation and GitHub’s Codex installation guide linked below.
In Codex, add GitHub using the documented remote server configuration for your current client. Do not paste a personal access token into a prompt or commit it to a file.
Complete the provider’s authentication flow. Review the repository and operation scopes before accepting.
Confirm that the GitHub server appears in Codex’s MCP list. If it does not, stop and troubleshoot the configuration instead of widening permissions.
Run one read-only request for issue 12. Ask Codex to return the issue title, state, labels, author, and URL, with no edits, comments, assignments, or status changes.
Open the issue in GitHub and compare each returned field. Disconnect the server when the check is complete if you do not need the connection again.

Copyable read-only instruction

Use the connected GitHub MCP server for one read-only lookup.

Repository: example-org/example-repo
Issue: 12

Return only:
- title
- state
- labels
- author
- web URL

Do not create, edit, comment on, assign, close, reopen, merge, or delete anything.
If the repository or issue cannot be read, report the exact limitation and stop.
Do not infer missing fields.

Acceptance checks

The returned repository and issue number must match the request. The title, state, labels, author, and URL must match the GitHub issue page. The activity log must show a read operation only. If any write tool is exposed or the scope is broader than you intended, stop, remove the connection, and review the provider settings.

Troubleshooting

If Codex lists no GitHub tools, confirm that the server configuration uses the current documented transport and that authentication completed for the same client.
If authentication succeeds but the repository is unavailable, check account access and repository spelling before changing scopes.
If the server exposes write tools, do not rely on the prompt alone. Use the client or provider controls to restrict access, or use the no-code GitHub web alternative.

Limits and privacy

MCP connects a model to external tools. A read-only instruction is useful, but it is not a substitute for account scopes, client approvals, or human review. Use test data first, keep secrets out of prompts, and never assume that a connected server is safe for unattended changes.

Evidence label: Documentation-based guide with a fictional repository and illustrative result. Codex, GitHub MCP, authentication, and issue access were not executed for this article.