MCP100 IndexHost
WatchlistCommunity implementation

Cyrene Agent

by Playa Cyrene

Reviewed October 5, 2026

Host

Watchlist tracking

Reviewed for relevance and future tracking value.

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track host integrations and agent-loop behavior as Cyrene develops

Reviewed · Documentation review; complete setup workflow not independently tested

Best fit

Desktop/self-hosted agent workspace with RAG, MCP, skills and messaging channels

What we know

Agent host with document knowledge base, MCP server management, skills, memory and external chat channels such as Lark, WeChat and QQ.

Maintenance / activity evidence

  • Observed (UTC)fix(模型历史):引入统一模型执行并修复跨协议历史互通

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

  • Installation and comprehensive security have not been independently audited.
  • Cyrene integrates MCP tools into a permission approval and Execution Policy system. Writes: Depends on connected MCP/tools/channels.
  • Provider/channel/MCP-specific.
  • Sensitive access: Private documents, Chat messages, Provider credentials
  • The host can aggregate documents, messaging identities and MCP tools; its approval/policy layer should remain enabled.
Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

627 repository stars

Stars observed Sep 25, 2026.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

All limitations / Review context

Which MCP servers and user workflows are currently supported?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

  • The host can aggregate documents, messaging identities and MCP tools; its approval/policy layer should remain enabled.
  • Cyrene integrates MCP tools into a permission approval and Execution Policy system.
  • Provider/channel/MCP-specific.
  • Documents, prompts and channel messages may flow to configured local/cloud models and services.
  • Reviewed write actions: Depends on connected MCP/tools/channels
  • Sensitive access: Private documents, Chat messages, Provider credentials
  • Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
  • A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
  • No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
  • The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
  • Exact install command/pricing
  • Third-party MCP stability depends on each server.
  • External channels and cloud embeddings introduce additional data flows.

Original activity observations

  • 2026-10-04T20:53:06Z: fix(模型历史):引入统一模型执行并修复跨协议历史互通
Technical identity
github.com/playa-cyrene/cyrene-agent
Reviewed resource type
Host
Repository identity
playa-cyrene/cyrene-agent

Evidence & Sources

Evidence basis
Recorded source evidence
Setup runtime verification
Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed · Latest source observation

  • GitHub repository ↗

    playa-cyrene/cyrene-agent

    Recorded repository material and project history.

    Includes references whose attribution is not established.