AI Context Flow

network.plurality由 plurality.network 發布官方發布者v1.0.1更新於 Oct 24, 2026

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

已驗證Streamable HTTP可網頁執行效率與工作流知識與記憶

概覽

AI 產生的概覽

一個遠端 MCP 伺服器,為 AI 助理提供持久記憶:在記憶桶中儲存、整理並以語意搜尋文件、筆記、對話和檔案。

可以做什麼
列出並建立用來整理已存上下文的記憶桶,並僅以中繼資料列出桶內項目。將文字內容或整段對話儲存到指定的記憶桶。跨記憶桶進行帶相關性分數的語意搜尋,並分頁讀取某筆已存內容的完整正文。可將記憶桶分享給他人,讓多個代理與協作者共用同一份上下文。
適用情境
適合希望助理跨工作階段、跨不同用戶端(例如 Claude、ChatGPT、Cursor)記住上下文,或維護可搜尋的筆記、聊天與文件個人知識庫的情況。也適合需要與他人共享已存上下文的團隊。
執行需求
透過 streamable HTTP 連線到 app.plurality.network 的遠端端點,不需在本機安裝套件。必須驗證:互動式用戶端使用 OAuth 2.1 + PKCE(一次性瀏覽器登入),無介面代理與 CI 使用以 Bearer 權杖送出的個人存取權杖。需要 Plurality 帳號,且個人存取權杖需要付費方案。
安裝前請注意
儲存的內容放在 Plurality 的伺服器上,並會傳送到其後端與向量服務,因此不要在記憶桶中放入敏感資料。寫入類工具會儲存文字與對話並建立記憶桶,會變更已存資料。個人存取權杖可存取你的記憶且需要付費方案,應妥善保密,外洩後立即撤銷或輪替。記憶桶可分享給他人,請確認存取權限。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 AI Context Flow,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/network.plurality%2Fai-context-flow/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "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


來源:README.md,提交 fd5db47

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.0.1最新Sep 16, 2026

評分

已滿足適用檢查項的 75%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。