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 分

    请在仓库或注册中心条目中声明许可证。