Can octocode MCP server create GitHub issues, or is it read-only?
I'm using the octocode MCP server in Copilot and asked it to create a GitHub issue. Copilot replied that octocode is designed for searching and fetching GitHub content, not for creating issues. Is octocode read-only by design, or is there a way to enable issue creation?
Originally asked on GitHub: https://github.com/bgauryy/octocode/issues/143
3 answers
Status: explained — the maintainer confirmed on 2026-01-17 that octocode is intentionally a research tool and should only read, and the request was closed without write support being added.
A user working with octocode in Copilot asked Copilot to open a GitHub issue. Copilot refused, saying octocode is designed for searching and fetching GitHub repository content, not for creating issues. The maintainer first replied that the idea was good and that octocode supported issue creation in its initial versions, and suggested opening a discussion, saying he might add the feature soon. In a later comment he stated: "Octocode is a research tool. It should only Read :)" and the issue was closed as completed.
No configuration, flag, or version mentioned in the thread enables write operations. If your workflow must create issues, you need a separate mechanism. General advice: use the GitHub REST API or the
ghCLI with a token that hasissues:writescope, or connect an MCP server that explicitly supports write actions. Security note (general advice): since octocode only reads, give it a token with read-only scope so it cannot modify repositories.Did this work for you?What a GitHub user tried on GitHub (Didn't work)
The reporter asked Copilot to create a GitHub issue through octocode. Copilot refused, saying octocode is designed for searching and fetching GitHub content, not for creating issues.
Source: https://github.com/bgauryy/octocode/issues/143 (opens external site)
Did this work for you?What @bgauryy tried on GitHub (Outcome unclear)
The maintainer suggested opening a discussion and said he might add issue creation soon, but later decided octocode should stay read-only. The thread does not show whether the discussion was created.
Source: https://github.com/bgauryy/octocode/issues/143#issuecomment-3405072165 (opens external site)
Did this work for you?
Related questions
- octocode-mcp in Cursor: syntax error near unexpected token '(' and no tools — how was it fixed?
- Which permissions does the Octocode MCP server need in a sandboxed manifest?
- Grok-4-fast returns no text with Octocode MCP in Cursor
- Octocode appears in my agent's final status messages — how do I stop it?
- npm error EUNSUPPORTEDPROTOCOL: Unsupported URL Type "workspace:" when running npx octocode-cli