AI Context Flow
Overview
Description from the maker (original English)
Universal memory for AI agents and tools. Save, organize and search context anywhere.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews from signed-in users. The average shows once there are reviews
- Our basic checksi2 of 2 passedChecked from public information; code not scanned yet
- UsageiVery new★ 2
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 2 of 2 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://app.plurality.network/mcpRun this in your terminal
claude mcp add --transport http ai-context-flow https://app.plurality.network/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ai-context-flow": {
"url": "https://app.plurality.network/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"ai-context-flow": {
"type": "http",
"url": "https://app.plurality.network/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Works with ChatGPT Business, Enterprise and Edu on the web; a workspace owner or admin adds it
- Go to Plugins, press + and choose Add custom MCP server
- Give it a name, paste the address below and set up sign-in as the maker says
- Read the warning, tick to accept, then choose Create as a plugin
https://app.plurality.network/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Related guides
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 11, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain plurality.network (the registry checks domain ownership)
- ✓ Pass
Still maintained
Code last changed 2 months ago
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Search & AI memoryi
- More stars than 81% of the other 5868 servers in this category
- Published to the registry more recently than 12% of the other 5868 servers in this category
- Basic checks equal to or better than 100% of the other 5868 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is AI Context Flow safe?
It passed 2 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed 2 months ago, and the latest version (1.0.1) reached the registry 6 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT Business and above.
What can I use instead?
In the same category: Ruflo, Context7, Metabase
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Plurality MCP Server
Universal memory for AI agents and tools. Save, organize and search context anywhere.
An Model Context Protocol server that gives any MCP-compatible AI client persistent memory — documents, notes, conversations, and files stored across organized memory buckets with semantic search. Supports OAuth and Personal Access Tokens (PAT) based authentication.
Why use this?
- Memory Studio — a personal knowledge base and second brain where you organize context into memory buckets, review saved content, and manage what your AI agents know.
- Save important chats — directly from within Claude, ChatGPT, Cursor, and other AI tools into the relevant memory bucket
- Shared persistent memory across all your agents — Claude Code, Lovable, Cursor, OpenClaw and more all access the same context
- Semantic search — find relevant memories using natural language, not just keywords
- Share buckets with other people — collaborate by giving others access to your context
- Works everywhere — any MCP-compatible client can connect
We also have a Chrome extension called AI Context Flow that lets you capture and use context on any website. It comes with a built-in chat agent (30+ models) that opens as a sidebar on any page — talk to your memories, answer questions from your stored context, and surface connections across everything you've saved. You can use the MCP Server alongside the extension to get full feature set of the product.
▶️ Watch the demo
📖 Full documentation · 🌐 Website · 🧩 Chrome Extension · 🧠 Memory Studio
Quick connect (production)
Production URL: https://app.plurality.network/mcp
The server supports OAuth 2.1 with PKCE (for interactive clients) and Personal Access Tokens (for headless agents and CI). Most clients handle the OAuth flow automatically.
Works with Claude Desktop, Claude Code, ChatGPT, Cursor, and any MCP-compatible client.
→ [Step-by-step setup guides for all supported clients](https://docs.plurality.network/the-plurality-mcp-server/connect-your-agents-via-mcp)
Tools
| Tool | Description |
|---|---|
get_user_memory_buckets | List all memory buckets (organized folders) for the user |
list_items_in_memory_bucket | List stored items in a specific bucket (metadata only) |
search_memory | Semantic search across buckets with relevance scoring |
read_context | Read the full content of a stored item with pagination |
save_memory | Save text content to a specific memory bucket |
save_conversation | Save a conversation (chat history) to a memory bucket |
create_memory_bucket | Create a new memory bucket for organizing saved content |
Authentication
The MCP server accepts two auth methods:
| Method | When to use | Browser required? |
|---|---|---|
| OAuth 2.1 + PKCE | Interactive clients: Claude Desktop, Web, Code, ChatGPT | Yes (one-time) |
| Personal Access Token (PAT) | Headless agents, CI runners, custom integrations, n8n, LangChain | No |
Using a Personal Access Token
- Sign in to the dashboard, open Connect via MCP → Manage tokens
- Click Create token, give it a name and optional expiry, copy the
plur_pat_…value - Configure your client to send it as a Bearer token:
Authorization: Bearer plur_pat_...
PATs require a paid plan. They auto-revoke at expiry, can be rotated with a configurable grace period (default 7 days), and can be immediately revoked from the dashboard. They are stored hashed and never appear in logs.
OAuth details
The server uses Ory Hydra as the OAuth2/OIDC provider:
| Property | Value |
|---|---|
| Algorithm | RS256 |
| Issuer | https://app.plurality.network (prod) |
| Scope | openid offline_access mcp:tools |
| Access token TTL | 15 minutes |
| Refresh token TTL | 720 hours |
| Discovery | https://app.plurality.network/.well-known/oauth-authorization-server |
| Dynamic Client Registration | https://app.plurality.network/register |
OAuth2 flow (step by step)
- Client discovers auth server — fetches
/.well-known/oauth-protected-resourcefrom Traefik - Client registers — calls
/register(Dynamic Client Registration) to getclient_id/client_secret. The API Gateway proxies this to Hydra, injecting themcp:toolsscope - User authenticates — browser opens Hydra's login flow, which redirects to the frontend's login/consent pages
- Token issued — Hydra returns a JWT access token (RS256, 15min TTL) with the user's ID as the
subclaim andmcp:toolsscope - Authenticated requests — client includes
Authorization: Beareron all MCP requests - MCP server validates — JWT signature verified locally against Hydra's JWKS public keys (cached 1 hour),
mcp:toolsscope is checked - API Gateway access — MCP server forwards the Bearer token when calling API Gateway endpoints for data retrieval and storage
Architecture
MCP Client (Claude Code, Cursor, etc.)
│ │ OAuth2 + Streamable HTTP ▼ Traefik (:5050) ← single entrypoint for clients ├── /mcp → MCP Server (:5051) ├── /.well-known/* → API Gateway or Hydra ├── /oauth2/* → Hydra (:4444) └── /register → API Gateway (DCR proxy) │ │ Bearer token ▼ API Gateway (:5000) │ ▼ Vector Service (:8000)
Traefik is the single entrypoint. It routes OAuth traffic to Hydra and MCP protocol traffic to the MCP server. The MCP server validates JWTs locally via Hydra's JWKS keys, then forwards the Bearer token to the API Gateway for data access. The API Gateway handles authentication, DCR proxying, and routes vector/search operations to the Vector Service.
Local development setup
Prerequisites
- Python 3.11+
- uv (Python package manager)
- Docker and Docker Compose
- Running API Gateway (plurality-backend-api): Handles authentication, OAuth metadata, DCR proxying, and database access
- Running Vector Service (plurality-ai-service): Handles semantic search and vector database operations
1. Install dependencies
cd plurality-mcp-server
pip install uv uv sync
2. Configure environment
cp .env.example .env
Default values work for local development — no changes needed if the API Gateway runs on :5000:
HYDRA_ISSUER=http://localhost:5050
MCP_RESOURCE_URL=http://localhost:5050 BACKEND_API_URL=http://localhost:5000
3. Start Docker services (Hydra + Traefik)
cd ory-hydra
docker compose up -d
This starts:
| Service | Port | Purpose |
|---|---|---|
| PostgreSQL | 5433 | Hydra's database |
| Hydra | 4444, 4445 | OAuth2/OIDC provider (public + admin) |
| Traefik | 5050 | Reverse proxy / routing |
Wait for services to be healthy: docker compose ps
4. Start the MCP server
uv run uvicorn main:mcp_server --host 0.0.0.0 --port 5051 --reload
Port 5051, not 5050. Traefik listens on 5050 and proxies
/mcpto the MCP server on 5051.
5. Verify
# Health check (direct)
curl http://localhost:5051/mcp/health
OAuth metadata (via Traefik)
curl http://localhost:5050/.well-known/oauth-protected-resource
Traefik dashboard (for debugging routes)
open http://localhost:8080
Local client configuration
Claude Code
claude mcp add --transport http plurality-memory http://localhost:5050/mcp
Then authenticate via /mcp inside Claude Code.
Claude Code — VS Code Extension
Authenticate first in the terminal using the steps above. Then add .mcp.json to your project root:
{
"mcpServers": { "plurality-memory": { "type": "http", "url": "http://localhost:5050/mcp" } } }
The VS Code extension may not trigger the OAuth browser flow automatically. Complete authentication via the terminal first.
Claude Desktop
Edit your config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": { "plurality-memory": { "command": "npx", "args": ["mcp-remote", "http://localhost:5050/mcp"] } } }
Restart Claude Desktop fully, then authenticate when the browser opens.
MCP Inspector (debugging)
npx @modelcontextprotocol/inspector
Enter http://localhost:5050/mcp as the server URL. The inspector walks through the OAuth flow and lets you call tools interactively.
Note: ChatGPT is not supported for local development — it requires publicly reachable OAuth endpoints.
Project structure
plurality-mcp-server/
├── main.py # Entry point ├── pyproject.toml # Dependencies (managed by uv) ├── .env.example # Environment template ├── src/plurality_mcp_server/ │ ├── app.py # FastMCP app + middleware stack │ ├── config.py # Env vars, shared HTTP client, context vars │ ├── auth.py # JWT validation via Hydra JWKS + scope check │ └── tools.py # MCP tool definitions (read + write) └── ory-hydra/ ├── docker-compose.yml # Hydra + Traefik + PostgreSQL ├── hydra.yml # Hydra OAuth2/OIDC config ├── traefik.yml # Traefik static config └── dynamic.yml # Traefik routing rules
Troubleshooting
MCP client gets 401 Unauthorized
- Check that Hydra is running:
curl http://localhost:4444/.well-known/openid-configuration - Check that the JWT hasn't expired (15min TTL)
- Verify
HYDRA_ISSUERmatches the issuer in the token'sissclaim - Ensure the token has the
mcp:toolsscope
MCP client gets 502 Bad Gateway
- The MCP server isn't running on port 5051
- Check Traefik logs:
docker compose -f ory-hydra/docker-compose.yml logs traefik
Tools return "Error: Backend API returned status 401" </summar