AI Context Flow

network.pluralityPublished by plurality.networkOfficial publisherv1.0.1Updated Oct 24, 2026

Universal memory for AI agents and tools. Save, organize and search context anywhere.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

A remote MCP server that gives AI assistants persistent memory: save, organize and semantically search documents, notes, conversations and files in memory bins.

What you can do
List and create memory buckets that organize saved context, and list the items stored in a bucket with metadata only. Save text content or a whole conversation into a chosen bucket. Run semantic search across buckets with relevance scoring and read the full content of a stored item with pagination. Share buckets with other people so several agents and collaborators draw on the same context.
When to use it
Useful when you want an assistant to remember context across sessions and across different clients, such as Claude, ChatGPT or Cursor, or to keep a searchable personal knowledge base of notes, chats and documents. Also fits teams that want to share saved context with others.
Requirements
A remote endpoint at app.plurality.network over streamable HTTP; no local package. Authentication is required: OAuth 2.1 with PKCE for interactive clients (one-time browser sign-in) or a Personal Access Token sent as a Bearer token for headless agents and CI. A Plurality account is needed, and PATs require a paid plan.
Before you install
Saved content is stored on Plurality's servers and sent to its backend and vector service, so avoid putting sensitive material in memory buckets. Write tools save text and conversations and create buckets, which changes stored data. A Personal Access Token grants access to your memory and requires a paid plan; keep it secret and revoke or rotate it if exposed. Buckets can be shared with other people, so check who has access.

Installation

In SourceWeft

  1. Open AI Context Flow in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/network.plurality%2Fai-context-flow/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ai-context-flow": {
      "type": "http",
      "url": "https://app.plurality.network/mcp"
    }
  }
}

README

Plurality MCP Server

Universal memory for AI agents and tools. Save, organize and search context anywhere.

[MCP Registry] [Smithery] [Version] [Python]


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]

▶️ 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


Tools

ToolDescription
get_user_memory_bucketsList all memory buckets (organized folders) for the user
list_items_in_memory_bucketList stored items in a specific bucket (metadata only)
search_memorySemantic search across buckets with relevance scoring
read_contextRead the full content of a stored item with pagination
save_memorySave text content to a specific memory bucket
save_conversationSave a conversation (chat history) to a memory bucket
create_memory_bucketCreate a new memory bucket for organizing saved content

Authentication

The MCP server accepts two auth methods:

MethodWhen to useBrowser required?
OAuth 2.1 + PKCEInteractive clients: Claude Desktop, Web, Code, ChatGPTYes (one-time)
Personal Access Token (PAT)Headless agents, CI runners, custom integrations, n8n, LangChainNo

Using a Personal Access Token

  1. Sign in to the dashboard, open Connect via MCP → Manage tokens
  2. Click Create token, give it a name and optional expiry, copy the plur_pat_… value
  3. 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:

PropertyValue
AlgorithmRS256
Issuerhttps://app.plurality.network (prod)
Scopeopenid offline_access mcp:tools
Access token TTL15 minutes
Refresh token TTL720 hours
Discoveryhttps://app.plurality.network/.well-known/oauth-authorization-server
Dynamic Client Registrationhttps://app.plurality.network/register
OAuth2 flow (step by step)
  1. Client discovers auth server — fetches /.well-known/oauth-protected-resource from Traefik
  2. Client registers — calls /register (Dynamic Client Registration) to get client_id/client_secret. The API Gateway proxies this to Hydra, injecting the mcp:tools scope
  3. User authenticates — browser opens Hydra's login flow, which redirects to the frontend's login/consent pages
  4. Token issued — Hydra returns a JWT access token (RS256, 15min TTL) with the user's ID as the sub claim and mcp:tools scope
  5. Authenticated requests — client includes Authorization: Bearer <token> on all MCP requests
  6. MCP server validates — JWT signature verified locally against Hydra's JWKS public keys (cached 1 hour), mcp:tools scope is checked
  7. 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

bash
cd plurality-mcp-serverpip install uvuv sync

2. Configure environment

bash
cp .env.example .env

Default values work for local development — no changes needed if the API Gateway runs on :5000:

HYDRA_ISSUER=http://localhost:5050MCP_RESOURCE_URL=http://localhost:5050BACKEND_API_URL=http://localhost:5000

3. Start Docker services (Hydra + Traefik)

bash
cd ory-hydradocker compose up -d

This starts:

ServicePortPurpose
PostgreSQL5433Hydra's database
Hydra4444, 4445OAuth2/OIDC provider (public + admin)
Traefik5050Reverse proxy / routing

Wait for services to be healthy: docker compose ps

4. Start the MCP server

bash
uv run uvicorn main:mcp_server --host 0.0.0.0 --port 5051 --reload

Port 5051, not 5050. Traefik listens on 5050 and proxies /mcp to the MCP server on 5051.

5. Verify

bash
# 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
bash
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:

json
{  "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
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)
bash
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_ISSUER matches the issuer in the token's iss claim
  • Ensure the token has the mcp:tools scope
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"
  • The API Gateway needs to accept Hydra JWTs — ensure jwks-rsa is installed and the OAuth auth middleware is deployed
OAuth flow redirects to localhost:3000 but nothing is there
  • Hydra is configured with login: http://localhost:3000/login — this points to the Plurality frontend. Start the frontend or update hydra.yml URLs.
DCR returns unexpected scope or missing mcp:tools
  • The API Gateway's DCR proxy injects mcp:tools into the allowed scopes. Ensure the API Gateway is running and the /register route is reachable.

Links


Source: README.md at commit fd5db47

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.