Conversation
Document the built-in MCP endpoint (http://127.0.0.1:23373/v0/mcp when mcp_enabled is true), bearer auth from ~/.beeper/targets/ or BEEPER_ACCESS_TOKEN, and a claude mcp add example. Note that browser OAuth needs Desktop; Server uses the bearer header. Addresses beeper#20. A beeper mcp helper remains tracked in beeper#10 — this PR is docs-only and does not add a command.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The documented port is incorrect for managed Server targets, which normally begin at port 23374 and may use custom ports.
Review effort: Balanced
Findings: 2
Open (2)
What changed in this PR
Documents bearer-authenticated MCP access for Beeper Server and Desktop.
Changes:
- Adds MCP endpoint, authentication, and Claude Code setup guidance.
- Links headless setup documentation to the expanded README guidance.
| File | Description |
|---|---|
README.md |
Adds generated MCP documentation. |
packages/cli/README.md |
Mirrors MCP documentation for the package. |
packages/cli/scripts/generate-readme.ts |
Generates the new README section. |
packages/cli/docs/setup.md |
Adds MCP guidance to headless setup. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Author
|
Addressed the managed-Server port findings in the current head: MCP docs now use |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs-only follow-up for #20: Beeper Server already serves the same MCP endpoint as Desktop. This documents how to point an MCP client at it with a bearer token.
What
generate-readme.tsso regen stays in sync)packages/cli/docs/setup.mdDocumented wiring (from maintainer guidance on #20)
http://127.0.0.1:23373/v0/mcpwhenGET /v1/infoshowsmcp_enabled: trueAuthorization: Bearer <token>from~/.beeper/targets/orBEEPER_ACCESS_TOKENclaude mcp add beeper http://127.0.0.1:23373/v0/mcp -t http -H "Authorization: Bearer <token>"Out of scope
beeper mcpcommand (tracked with the docs/agent CLI work in Add static docs site and agent-friendly CLI output #10)Addresses #20.
Test plan
bun run readme/check:readmestill matches after reviewing generator + README pair (docs-only; no command changes)