# Bear 2.8 Beta: Official CLI, Claude Connector, and MCP Server

**URL:** <https://community.bear.app/t/bear-2-8-beta-official-cli-claude-connector-and-mcp-server/19040>\
**Category:** Announcement\
**Tags:** beta\
**Created:** [April 22, 2026, 9:12am UTC](https://community.bear.app/t/bear-2-8-beta-official-cli-claude-connector-and-mcp-server/19040 "2026-04-22T09:12:18Z")\
**Posts on this page:** 1\
**Showing post:** 49

<div class="post-metadata">

**Author:** ![rexikan](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/rexikan/32/4117_2.png) [@rexikan](https://community.bear.app/u/rexikan)\
**Post date:** [April 24, 2026, 3:51pm UTC](https://community.bear.app/t/bear-2-8-beta-official-cli-claude-connector-and-mcp-server/19040/49 "2026-04-24T15:51:11Z")

</div>

> [@cipher](#):
>
> > [@rexikan](#):
> >
> > > [@mugpunter](#):
> > >
> > > Is there a way to exclude certain notes from the Claude Connector? That could be quite useful. For example, all notes with tag #xyz would never be ingested by Claude.
> > 
> > Nice idea! We could consider it if people would find it useful.
> 
> I would also find something like this useful. Though i don’t know if i want granting or restricting. (i.e. Explicitly allow access to these tag trees AND/OR explicitly block access to these tag trees.)

We might frame this as focusing the API on one workspace, once we release the tag-as-workspace feature that we have previously mentioned. So it would be scoped to one tag instead of excluding tags. Does that sound good to you?

---

_[View the full topic](https://community.bear.app/t/bear-2-8-beta-official-cli-claude-connector-and-mcp-server/19040)._