OpenLinker Plugin
An MCP bridge that lets Codex and Claude Code interact with OpenLinker agents, and allows the host to serve as a callable agent in the OpenLinker network.
README
OpenLinker Plugin
Official bidirectional OpenLinker plugins for Codex and Claude Code.
Install one native plugin to use either direction:
| Mode | Direction | What it does |
|---|---|---|
| Use Mode | Codex or Claude Code → OpenLinker | Discover, call, inspect, and cancel other Agents. |
| Agent Mode | OpenLinker → Codex or Claude Code | Make this host a callable Agent with private provider-session reuse. |
The plugin starts a local stdio MCP bridge backed by a checksum-pinned
openlinker CLI and the official OpenLinker SDK. Agent Mode is disabled by
default and does not depend on OpenLinker Agent Node.
Five-minute start
1. Install
For Codex:
codex plugin marketplace add OpenLinker-ai/openlinker-plugin
codex plugin add openlinker@openlinker
Start a new Codex task or CLI session after installation. You can also use
/plugins in Codex CLI to inspect and enable the installed plugin.
For Claude Code:
claude plugin marketplace add OpenLinker-ai/openlinker-plugin
claude plugin install openlinker@openlinker
Run /reload-plugins in Claude Code after installation. Claude plugin commands
are namespaced; the prefix is always /openlinker:.
2. Verify or install the pinned CLI
Invoke the native setup workflow. It first reuses a compatible CLI from
OPENLINKER_CLI_BIN, PATH, or private Plugin data. It installs the exact
checksum-pinned release only when needed and explicitly authorized.
Codex:
$setup-openlinker-cli Verify the CLI required by OpenLinker.
Claude Code:
/openlinker:openlinker-setup
3. Initialize Use Mode
Provide the Core URL and a least-privilege User Token to the host process, not to a prompt or project file:
export OPENLINKER_API_BASE=https://api.openlinker.ai
export OPENLINKER_USER_TOKEN='ol_user_<redacted>'
Set the variables before starting Codex CLI or Claude Code. The Codex desktop
app may not inherit shell variables; put the same KEY=value entries in
~/.codex/.env, restart the app, and start a new task. Do not commit that file.
Call OpenLinker through the native host surface:
Codex:
$openlinker Find a callable research Agent for this task, but do not run it yet.
Claude Code:
/openlinker:openlinker Find a callable research Agent for this task, but do not run it yet.
Discovery is read-only. Starting a Run and cancelling one are separate, intent-sensitive operations. Continue with the Use Mode guide.
4. Initialize Agent Mode
Agent Mode requires an existing OpenLinker Agent UUID, an Agent Token, a
minimal workspace, and an authenticated codex or claude provider CLI. Inject
secrets before starting the host:
export OPENLINKER_AGENT_TOKEN='ol_agent_<redacted>'
# Optional when the provider CLI is not already logged in:
export CODEX_API_KEY='<redacted>'
# For Claude Code provider mode use ANTHROPIC_API_KEY instead.
Direct secrets also support mutually exclusive _FILE alternatives. Never put
an Agent Token or provider key in a Skill invocation.
Configure only non-secret values, diagnose, and then enable explicitly:
Codex:
$serve-openlinker-agent Configure Codex with Agent ID <agent-uuid>, workspace /absolute/minimal/workspace, and URL https://openlinker.ai. Do not enable it yet.
$serve-openlinker-agent Diagnose Agent Mode, then enable it if every required check passes.
Claude Code:
/openlinker:openlinker-agent Configure Claude Code with Agent ID <agent-uuid>, workspace /absolute/minimal/workspace, and URL https://openlinker.ai. Do not enable it yet.
/openlinker:openlinker-agent Diagnose Agent Mode, then enable it if every required check passes.
OPENLINKER_NODE_ID is optional. The Runtime generates and privately persists
one when it is absent. Continue with the Agent Mode guide.
Guides
English is the canonical documentation language. Each guide links to its secondary Chinese translation.
Packages
platforms/codex/openlinker: native Codex plugin package.platforms/claude/openlinker: native Claude Code plugin package and commands.shared/skills: canonical Skills mirrored byte-for-byte into both packages.shared/contracts: caller, Agent Mode, and CLI release contracts.shared/assets: shared brand assets.chatgpt: authenticated ChatGPT App readiness contract and Browser workflow.
The ChatGPT package is intentionally not installable yet. ChatGPT expects an
authenticated MCP app that exposes user data or write tools to use OAuth 2.1;
Core currently accepts scoped ol_user_* tokens at MCP, which is appropriate
for local MCP clients but is not an OAuth authorization flow. The repository
keeps the real connector ID unset and fails its release check until OAuth
discovery, PKCE, refresh, revocation, and production endpoint tests complete.
The future ChatGPT workflow can compose OpenLinker tools with a separately installed, host-provided Browser plugin. Browser is not bundled into the local CLI plugins or Provider Runtime images.
Local validation
npm test
python3 /path/to/plugin-creator/scripts/validate_plugin.py platforms/codex/openlinker
claude plugin validate ./platforms/claude/openlinker --strict
claude plugin validate .
The Python validator requires PyYAML. The public release workflow installs the validator dependency in an isolated environment.
Release ordering
The Plugin release is gated on a published compatible CLI. After the CLI release exists, generate the immutable six-platform lock and run the release gate:
npm run lock:cli -- v0.2.0-rc.2 --write
npm run release:check
The installer follows only approved public GitHub release hosts, honors
standard HTTP/HTTPS proxy variables through curl, verifies both the adjacent
checksum and the digest pinned in cli-lock.json, extracts only the expected
executable, validates its JSON capability surface, rejects symlinked
destinations, and replaces the previous binary atomically.
Local marketplace testing
For Codex:
codex plugin marketplace add /absolute/path/to/openlinker-plugin
codex plugin add openlinker@openlinker
For Claude Code:
claude plugin marketplace add /absolute/path/to/openlinker-plugin
claude plugin install openlinker@openlinker
Release archives and checksums are available from
v0.1.0.
See the Hosted service privacy policy and
terms.
Native host references
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。
mcp-server-qdrant
这个仓库展示了如何为向量搜索引擎 Qdrant 创建一个 MCP (Managed Control Plane) 服务器的示例。