FeedbackServer
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FeedbackServerinvite a new admin with 7-day expiry"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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-serverStart a new Codex task after installation. To update, run
codex plugin marketplace upgrade feedback-server, reinstall
feedback-server@feedback-server, and start another task.
Related MCP server: feedback-mcp
Install for Claude Code
claude plugin marketplace add Rabithua/FeedbackServerPlugin
claude plugin install feedback-server@feedback-server --scope userRestart 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 configureThe 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-localExisting 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.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseBquality-maintenanceEnables AI agents to administer MetaMCP instances by managing servers, namespaces, endpoints, and API keys across multiple deployments. Supports full CRUD operations, bulk server imports, cross-instance cloning, and granular tool management through MetaMCP's tRPC API.Last updated261
- Alicense-qualityAmaintenanceMCP server for Open Feedback, enabling AI assistants to submit, list, get, update status of, and analyze product feedback via a local HTTP API and JSONL storage.Last updated628Apache 2.0
- Flicense-qualityBmaintenanceAdmin MCP server that exposes Kubernetes CRD state and live broker status as MCP tools and a browser-renderable UI resource, enabling platform engineers to manage the mcp-gateway without kubectl.Last updated
- AlicenseAqualityAmaintenanceMCP server for reading public Featurebase feedback boards, enabling agents to query user feedback, posts, comments, and statistics.Last updated726MIT
Related MCP Connectors
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
Remote MCP server for the Hackle Admin API: experiments, feature flags, remote config, messaging.
Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Rabithua/FeedbackServerPlugin'
If you have feedback or need assistance with the MCP directory API, please join our Discord server