Integrations
No need to open a browser. Operate PlainHub from your terminal or AI IDE. PlainHub fits naturally into your developer workflow.
CLI — One command from your terminal
During code review, thinking "I want to check this doc in the browser"? One command from your terminal opens PlainHub.
You can also specify theme and font size, making it useful as a shareable team URL.
See all CLI options in the CLI Reference →
MCP Server — Natural language from your AI IDE
Just talk to Claude Code or Cursor, and PlainHub launches. No commands to memorize.
Works alongside gh CLI
Already using gh CLI? PlainHub is ready to go. Shared authentication means almost no extra setup.
If gh CLI is "the tool for operating GitHub," PlainHub is "the tool for editing GitHub files." Different strengths, natural to use together.
For example: check an Issue with gh CLI → fix the related doc in PlainHub → save (Git commit). Seamlessly move between terminal and browser.
Claude Code Integration
Claude Code + PlainHub covers both code and documentation. See MCP Server / CLI sections above for details.
Writing a CLAUDE.md for your repo? See CLAUDE.md: what to write and where to put it.
Want your team to see what your coding agents are doing and approve their decisions? See How to share your AI coding agents' work and approvals with your team.
Workflow examples
- Code + Docs — Fix code in Claude Code → update docs in PlainHub → both committed to Git
- Bug investigation — Investigate the cause in Claude Code → visually review changes with
plainhub diff - Team collaboration — Non-engineers write meeting notes in PlainHub → engineers reference them in Claude Code
Claude Code is where you write code. PlainHub is where you write documents. MCP/CLI connects them seamlessly.
Flexible combinations
PlainHub's CLI, MCP, browser, and AI panel all connect to the same GitHub data. Access the same files from any channel — combine them however you like.
No restrictions on how you use it. If you have GitHub and a browser, it fits into any workflow.