FeedbackServer
Enables administrators to manage a FeedbackServer instance through MCP, including agent account configuration, admin invitations, and token revocation.
README
FeedbackServer Plugin
FeedbackServer Plugin is the public multi-agent distribution for administering a compatible FeedbackServer instance. One audited TypeScript implementation provides a shared MCP server, management Skill, and trusted-terminal account CLI for Codex and Claude Code. The repository contains no FeedbackServer source, deployment configuration, database access, or credentials.
Install for Codex
codex plugin marketplace add Rabithua/FeedbackServerPlugin --ref main
codex plugin add feedback-server@feedback-server
Start a new Codex task after installation. To update, run
codex plugin marketplace upgrade feedback-server, reinstall
feedback-server@feedback-server, and start another task.
Install for Claude Code
claude plugin marketplace add Rabithua/FeedbackServerPlugin
claude plugin install feedback-server@feedback-server --scope user
Restart or reload Claude Code after installation. The plugin starts its MCP server from the cached
bundle through ${CLAUDE_PLUGIN_ROOT} and exposes the same manage-feedback-server Skill.
Cursor and OpenCode can use the same standalone MCP bundle. See Generic MCP clients for checked configuration templates.
Configure an Agent account
The distributable CLI runs from the committed bundle and does not require node_modules:
git clone https://github.com/Rabithua/FeedbackServerPlugin.git
cd FeedbackServerPlugin
plugins/feedback-server/bin/feedback-server agent configure
The CLI hides passwords, invitation tokens, and PATs. On macOS it stores credentials under the
existing Keychain service dev.rote.feedback-server.mcp, so Codex and Claude Code reuse the same
account without copying or rotating its PAT. Non-macOS MCP processes must receive both
FEEDBACK_SERVER_BASE_URL and FEEDBACK_SERVER_API_TOKEN from a secure process environment.
Supported commands:
feedback-server agent configure
feedback-server agent disconnect
feedback-server agent revoke-token --id <uuid>
feedback-server admin invite
feedback-server admin invitations
feedback-server admin invite revoke --id <uuid>
feedback-server admin accept-invite
feedback-server admin create-local
Existing checkout workflows such as bun run agent:configure and
bun run admin:invite:revoke --id <uuid> remain available as compatibility aliases.
Invite administrators
Only an enabled super_admin may create or revoke invitations. Authentication-management routes
require a short-lived interactive session and are deliberately not exposed as MCP tools.
For a recipient-facing handoff, admin invite copies a complete Simplified Chinese handoff package
that includes the one-time invitation, a safe prompt the recipient can give to Codex or Claude Code,
and a link to the onboarding guide. The package tells
the recipient not to paste the invitation token into Agent chat; it belongs only in the hidden
terminal prompt.
admin invite creates a 7-day invitation by default, with --expires-in-days accepting 1–30. It
writes the handoff package to the macOS clipboard through stdin, reports only the invitation ID,
prefix, and expiry, and clears the package after the sharing handoff when unchanged. A clipboard or handoff
failure revokes the invitation before logout.
admin accept-invite refuses to consume an invitation when another Agent credential is configured.
It creates an ordinary administrator, verifies the account owns no Products, creates a 365-day PAT,
stores it atomically, and logs out every temporary session. If account creation committed but local
configuration failed, do not reuse the invitation: run feedback-server agent configure with the
new account. Any PAT whose compensating revocation also failed is recorded by non-secret ID in a
separate Keychain ledger and can be removed with the reported agent revoke-token command.
Each administrator owns an independent tenant. New administrators start with no Products and cannot access another owner's Product.
Security and development
Remote endpoints must use HTTPS. Plain HTTP is accepted only for exact loopback hosts
localhost, 127.0.0.1, and [::1]. Secrets are never accepted as command arguments or written to
logs, bundles, repository files, or pending-revocation metadata.
bun install --cwd=plugins/feedback-server --frozen-lockfile
bun run check
bun run validate
bun run scan
claude plugin validate --strict .
Both dist/server.mjs and dist/cli.mjs are deterministic committed bundles. FeedbackServer
Plugin is licensed under the MIT License.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。