Saya
Enables agents to query team brain for memory, channels, decisions, skills, and readiness through a central remote MCP endpoint.
README
<p align="center"> <img src="assets/logo.png" alt="Saya" width="88" height="88" /> </p>
<h1 align="center">Saya plugins</h1>
<p align="center"><strong>Plug any agent into your team's Saya.</strong></p>
<p align="center"> Before you guess, ask the team brain. Saya exposes a central remote MCP endpoint so external agents can query live, trust-graded team knowledge from the workspace Saya already lives in. </p>
<p align="center"> <a href="https://saya.computer">saya.computer</a> · MCP: <code>https://saya-mcp.luke-nittmann.workers.dev/mcp</code> </p>
Install
<!-- AUTO-GENERATED:INSTALL START -->
Any MCP client (.mcp.json)
Add Saya as a Streamable HTTP MCP server at the live workers.dev origin. When your client prompts, complete browser OAuth for your team; the per-team bearer belongs in the client credential store, never in this repo.
{
"mcpServers": {
"saya": {
"url": "https://saya-mcp.luke-nittmann.workers.dev/mcp",
"transport": "streamable-http"
}
}
}
Any agent (npx skills)
Installs the secondary usage-guide skill for skill-aware agents. This teaches when to query Saya; the live MCP endpoint remains the product surface.
npx skills add creative-int/saya-plugins
Claude Code
Add the marketplace, install the Saya plugin, then complete browser OAuth before the first team-brain query.
/plugin marketplace add creative-int/saya-plugins
/plugin install saya@saya
Codex
Add this repo as a Codex plugin marketplace, install from /plugins, then authenticate the MCP connection for your workspace.
codex plugin marketplace add creative-int/saya-plugins
Cursor
Install Saya from the Cursor plugin marketplace, then authenticate the MCP connection for your workspace.
Cursor -> Settings -> Plugins -> Add marketplace -> creative-int/saya-plugins
<!-- AUTO-GENERATED:INSTALL END -->
To preview the available skills without installing:
npx skills add creative-int/saya-plugins --list
Quickstart: tap the team brain
- Add the MCP server with the generated
.mcp.jsonblock above, or install the plugin through Claude Code, Codex, or Cursor. - When the client prompts for auth, complete browser OAuth with the workspace that owns the Saya brain. The bearer is per-team and should stay in the MCP client's credential store or environment, never in a tracked file.
- Start with
saya_statusif you need to confirm the live bridge, scopes, or workspace health. - Use
saya_contextbefore making team-specific assumptions. Ask focused questions like: "What has this team decided about the Saya MCP launch? Return verified decisions first and call out candidate or deprecated notes." - Use
saya_actonly for the curated approval-first memory save path. Treat it as a write that needs user intent, not a general automation channel.
If a client exposes raw MCP calls instead of a friendly tool picker, inspect
tools/list after OAuth and follow the current input schema advertised by the
server.
MCP surface
Saya exposes one central Streamable HTTP MCP server. Team identity and access come from per-team OAuth bearer auth plus workspace membership; never put tokens in repo files.
| Tool | Scope | Purpose |
|---|---|---|
saya_context |
saya.context |
Read bounded workspace context: provenance-graded team knowledge, lifecycle status, trust grade, decisions, skills, and captured workspace memory. |
saya_act |
saya.act |
Save approved team memory through Saya's curated, idempotent, approval-first action path. |
saya_status |
saya.status |
Check live MCP readiness, tool availability, auth posture, and Convex bridge health. |
Status / readiness
The deployed endpoint is live on prod at
https://saya-mcp.luke-nittmann.workers.dev/mcp. Production OAuth and
workspace membership are required; authenticated saya_context queries return
real, trust-graded team knowledge from Saya's Convex brain. saya_act is the
approval-first save_memory path, and saya_status reports live bridge health.
The custom domain https://mcp.saya.computer/mcp is not routed yet, so this
repo intentionally points at the current workers.dev origin.
Included skill
saya-team-brain— secondary usage guidance for agents deciding when to query Saya through MCP before answering. Useful for team memory, decision history, workspace norms, channel context, and "what does this team already know?" questions. Also answers toask-teamandteam-context.
The skill lives at
skills/saya-team-brain/SKILL.md.
See docs/team-brain-agent-tap.md for the
runner-side sample flow and proof boundary.
Develop
pnpm install
pnpm generate # regenerate all adapters from saya.config.ts
pnpm verify # drift check + typecheck + build/help + MCP smoke
pnpm smoke always checks unauthenticated protected-resource metadata. Set
SAYA_MCP_BEARER to additionally assert the authenticated tools/list surface.
License
MIT © creative-int
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。
mcp-server-qdrant
这个仓库展示了如何为向量搜索引擎 Qdrant 创建一个 MCP (Managed Control Plane) 服务器的示例。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。