Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
S

smaramwbc/statewave-connectors

Independent directory — not the official site. Details below come from the project's public repository.

Feed real-world events into Statewave.

Before you install: no copy-paste command · license Apache-2.0

First step: nothing runnable here yet - start from the repository: https://github.com/smaramwbc/statewave-connectors/tree/main/packages/mcp-server

updated 2026-11-13
View on GitHub ↗Direct link · no redirect page

We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →

Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
Score
score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository smaramwbc/statewave-connectors;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.
README excerpt (English, untranslated) · Read the full README on GitHub →

# Statewave Connectors

Excerpted from the repository README (abridged)

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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/smaramwbc-statewave-connectors-tree-main-packages-mcp-server/)
Source
awesome · https://github.com/smaramwbc/statewave-connectors/tree/main/packages/m
Browse by field
MCP servers
Listed by
3 independent sources
added
today

More MCP servers

All 6,555 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index