S
smaramwbc/statewave-connectors
Feed real-world events into Statewave.
更新 2026-11-13
在 GitHub 查看 ↗直链 · 无中转页
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
smaramwbc/statewave-connectors;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# Statewave Connectors
以下摘录自该仓库的 README(片段)
Feed real-world events into Statewave.
> Part of Statewave — the open-source memory runtime for AI agents.
> 📦 Core runtime · 🐍 Python SDK · 🟦 TypeScript SDK · 🔌 Connectors · 📘 Docs · 💡 Examples · 🖥️ Admin · 🌐 statewave.ai
> 📋 Issues & feature requests: statewave/issues (centralized tracker)
Statewave Connectors turn GitHub issues, pull requests, Slack threads, Discord questions, support tickets, docs, email, and automation events into Statewave episodes.
Your agents can then retrieve compact, relevant memory by subject — instead of stuffing raw chat history or rebuilding a custom RAG pipeline for every tool.
Connectors talk to Statewave over its HTTP API and run as a standalone service — so they work with any Statewave app regardless of language (Python, Go, Rust, TypeScript). You don't need a Node app, or even Node installed, to use them.
## Why
Most "agent memory" implementations are limited to live chat transcripts. Real teams have memory in many places: GitHub history, Slack threads, support tickets, ADRs, email threads, workflow runs. Statewave is open memory infrastructure that holds all of those as episodes, compiles them into durable memories per subject, and serves compact context to agents on demand.
This repository is the connector ecosystem for that.
## Two ways to run connectors
Connectors are independent of your application's language. Pick whichever fits your stack:
1. As a deployed service — recommended, no Node required. Run the prebuilt runner container next to your app, the same way you'd run Postgres or Redis, and point it at your Statewave instance with a small TOML config. This is the path to use when your app is Python, Go, Rust — anything that isn't itself a Node service.
sh
docker run --rm -p 3000:3000 \
-v $PWD/statewave-connectors.toml:/config/statewave-connectors.toml:ro \
-e STATEWAVE_URL=https://your-instance \
-e STATEWAVE_API_KEY=… \
statewavedev/statewave-connectors-runner:latest
Compose / Helm / Fly / Railway recipes ship in deploy/ — see docs/deployment.md.
2. As npm packages — for embedding in a Node app. This is a monorepo for development, but each connector ships as its own published package, so you install only what you need.
sh
npm install @statewavedev/connectors-github
npm install @statewavedev/connectors-gitlab
npm install @statewavedev/connectors-bitbucket
npm install @statewavedev/connectors-gitea
npm install @statewavedev/connectors-azure-devops
npm install @statewavedev/connectors-jira
npm install @statewavedev/connectors-database
npm install @statewavedev/connectors-markdown
npm install @statewavedev/connectors-slack
npm install @statewavedev/connectors-n8n
npm install @statewavedev/connectors-zapier
npm install @statewavedev/connectors-discord
npm install @statewavedev/mcp-server
You do not need to install Slack to use the GitHub connector. The convenience meta-package @statewavedev/connectors exists for the rare case where you want all official connectors at once — it is not required for normal usage.
> Using Statewave from Python? You have full connector coverage today via path 1: the container ingests GitHub / Slack / Notion / support tickets into the same instance your pip install statewave app reads from. There is no separate "Python connectors" package because connectors are a service, not an SDK binding.
> Part of Statewave — the open-source memory runtime for AI agents.
> 📦 Core runtime · 🐍 Python SDK · 🟦 TypeScript SDK · 🔌 Connectors · 📘 Docs · 💡 Examples · 🖥️ Admin · 🌐 statewave.ai
> 📋 Issues & feature requests: statewave/issues (centralized tracker)
Statewave Connectors turn GitHub issues, pull requests, Slack threads, Discord questions, support tickets, docs, email, and automation events into Statewave episodes.
Your agents can then retrieve compact, relevant memory by subject — instead of stuffing raw chat history or rebuilding a custom RAG pipeline for every tool.
Connectors talk to Statewave over its HTTP API and run as a standalone service — so they work with any Statewave app regardless of language (Python, Go, Rust, TypeScript). You don't need a Node app, or even Node installed, to use them.
## Why
Most "agent memory" implementations are limited to live chat transcripts. Real teams have memory in many places: GitHub history, Slack threads, support tickets, ADRs, email threads, workflow runs. Statewave is open memory infrastructure that holds all of those as episodes, compiles them into durable memories per subject, and serves compact context to agents on demand.
This repository is the connector ecosystem for that.
## Two ways to run connectors
Connectors are independent of your application's language. Pick whichever fits your stack:
1. As a deployed service — recommended, no Node required. Run the prebuilt runner container next to your app, the same way you'd run Postgres or Redis, and point it at your Statewave instance with a small TOML config. This is the path to use when your app is Python, Go, Rust — anything that isn't itself a Node service.
sh
docker run --rm -p 3000:3000 \
-v $PWD/statewave-connectors.toml:/config/statewave-connectors.toml:ro \
-e STATEWAVE_URL=https://your-instance \
-e STATEWAVE_API_KEY=… \
statewavedev/statewave-connectors-runner:latest
Compose / Helm / Fly / Railway recipes ship in deploy/ — see docs/deployment.md.
2. As npm packages — for embedding in a Node app. This is a monorepo for development, but each connector ships as its own published package, so you install only what you need.
sh
npm install @statewavedev/connectors-github
npm install @statewavedev/connectors-gitlab
npm install @statewavedev/connectors-bitbucket
npm install @statewavedev/connectors-gitea
npm install @statewavedev/connectors-azure-devops
npm install @statewavedev/connectors-jira
npm install @statewavedev/connectors-database
npm install @statewavedev/connectors-markdown
npm install @statewavedev/connectors-slack
npm install @statewavedev/connectors-n8n
npm install @statewavedev/connectors-zapier
npm install @statewavedev/connectors-discord
npm install @statewavedev/mcp-server
You do not need to install Slack to use the GitHub connector. The convenience meta-package @statewavedev/connectors exists for the rare case where you want all official connectors at once — it is not required for normal usage.
> Using Statewave from Python? You have full connector coverage today via path 1: the container ingests GitHub / Slack / Notion / support tickets into the same instance your pip install statewave app reads from. There is no separate "Python connectors" package because connectors are a service, not an SDK binding.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/smaramwbc-statewave-connectors-tree-main-packages-mcp-server/)
- 来源
- awesome · https://github.com/smaramwbc/statewave-connectors/tree/main/packages/m
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。