Changelog
Jul 4
NewImproved
Slack integration is live
Pipe new feedback into Slack, then vote and comment without leaving the channel.
128Slack integration
128 subscribers
Will be notified on publish
Manage feedback, roadmap, and changelog over MCP.
Let the coding agent that knows the codebase read and update feedback, roadmap items, and changelog drafts.
The coding agent can read feedback, update roadmap items, and prepare changelog entries with workspace-scoped tools.
- 01
Connect one workspace
Authorize an MCP client with workspace-scoped credentials.
- 02
Choose tool scopes
Grant only the feedback, roadmap, or changelog permissions the client needs.
- 03
Review public changes
Review roadmap and changelog changes before they become public.
claude — glean-feed
Claude Code · connected to glean-feed
Triage today's new feedback and tag it by area.
On it — pulling today's new requests and grouping them by area.
glean-feed::list_feedback6 new requests
glean-feed::set_feedback_status5 approved · 1 spam
Done — 5 approved, 1 spam, grouped by area.
Move the top-voted request to In Progress.
glean-feed::list_feedbacktop voted: “Dark mode” · 128 votes
glean-feed::move_roadmap_stageplanned → in_progress
Moved. It's live on the public roadmap.
Draft a changelog for what shipped this week and publish it.
glean-feed::list_roadmap2 items shipped this week
glean-feed::create_changelog_entrydraft ready
Dark mode is here
The dashboard now follows your system theme, with a manual toggle in settings. Thanks to everyone who voted.
Looks good. Publish it.
glean-feed::publish_changelog_entrypublished · 128 subscribers emailed
Published. Everyone who voted just got the email.
Included in Glean Feed
- JSON-RPC MCP endpoint
- Workspace-scoped authentication
- Read and write scopes
- Feedback, roadmap, changelog, tag, and workspace tools
- REST API alongside MCP
When this is not the right fit
MCP tools still enforce workspace permissions, and public changes remain subject to review.
Ways to use it
MCP and API access are included on Free. Individual operations still require the appropriate read or write scopes.
Workspace-scoped credentials
Connect with a Glean Feed API key or supported OAuth flow; every call remains pinned to one workspace.
Resource-specific scopes
Limit the agent to approved read or write operations for each resource.
Review before publication
Let the agent triage and draft, then review roadmap or changelog changes before publication.
Works with
- Cursor
- Claude Code
- Codex
- Any compatible MCP client
- REST API tooling
Common questions
Does MCP access bypass workspace permissions?
No. Credentials are workspace-scoped and tools require the corresponding API scopes.
Can any MCP client connect?
Compatible clients can connect to the documented JSON-RPC endpoint using supported authentication.
Related pages
Connect your coding agent.
Let the coding agent that knows the codebase read and update feedback, roadmap items, and changelog drafts. Start on Free.