Development distribution of the ByteRover search, read, and whole-file upload plugin for AI agents.
- MCP server:
https://dev-mcp.byterover.ai/mcp - OAuth server:
https://dev.byterover.ai
The development server requires OAuth. The host opens the sign-in and consent flow when the plugin first calls ByteRover.
Paste this prompt into Claude Code, Claude Desktop, Codex, or Cursor:
Install and connect the development distribution of ByteRover from:
https://github.com/campfirein/byterover-plugin
Inspect the repository, detect the current host, use its native installation path, complete every step you can, and verify the connection.
Start ByteRover MCP OAuth automatically only if the current host and its permission policy allow that action. Do not bypass, change, or work around the permission policy.
When browser OAuth opens, I will complete sign-in and consent myself; do not complete them for me. Wait for me to finish, then resume and verify the ByteRover MCP connection.
After installation and OAuth, restart the host or open a new conversation if the current conversation does not reload newly connected tools. In the new conversation, explicitly ask the host to use ByteRover and verify a real ByteRover tool call.
If the host blocks, denies, or does not support automatic MCP OAuth, report the exact blocked action and provide the exact host-specific manual step to start it. If you cannot determine that step for this host, say so instead of guessing.
Do not overwrite existing configuration.
Agents must follow the packaged installation contract for every host. The user-facing prompt needs only this repository URL.
codex plugin marketplace add campfirein/byterover-plugin
codex plugin add byterover@byteroverComplete OAuth when Codex opens the browser, then verify search.
claude plugin marketplace add campfirein/byterover-plugin --scope user
claude plugin install byterover@byterover --scope userPaste the installation prompt above into Claude Desktop. Let its native plugin manager add ByteRover, approve the plugin when the app asks, and complete OAuth. The prompt does not bypass native approval or consent.
Follow the packaged installation contract. It merges only the ByteRover server entry, preserves other servers, and stops on local rule changes.
Open Grok Connectors, choose New Connector > Custom, add https://dev-mcp.byterover.ai/mcp as byterover, then complete OAuth.
Grok Bot receives MCP tools but not the host skill. Open a new conversation and explicitly ask it to use ByteRover.
Do not repeat OAuth unless the connector settings report an authentication error.
In ChatGPT Plugins, choose Add > Add custom MCP server and enter https://dev-mcp.byterover.ai/mcp. Complete OAuth, create
ByteRover as a plugin backed by that remote MCP server, then enable ByteRover under Customize > Plugins in the Dot.
Do not upload the desktop plugin ZIP. Start a new Dot conversation and explicitly ask it to use ByteRover.
This repository contains generated distribution files. The private source repository owns the plugin, skill,
generator, and tests. SOURCE.json records the source commit used for this development package.
Do not edit generated files here. Change the source, rebuild the package, and publish it with a
plugin-v<version> source tag. The release workflow opens a generated pull request in this repository.
The default branch is the release stream. Hosts detect updates from the version in the plugin manifests. Users do not install a versioned repository tag.