Feeduna MCP connector
OfficialThis server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Feeduna MCP connector
Version 0.1.1. Bring contextual feedback from your Feeduna app into a compatible local MCP host. Read installation guidance, list and export feedback, or submit feedback when you explicitly grant write access. Node.js 22 or later is required. This is a local stdio connector, not a hosted HTTP MCP endpoint or remote OAuth integration.
Install the MCP bundle
Sign in at https://app.feeduna.com/review and add your app.
In App setup → Connect your tools, create an expiring access key for that app. Grant only the scopes you need.
setup:readreads setup instructions;reports:readreads feedback;reports:writepermits feedback submission.Open the reviewed
feeduna-mcp-0.1.1.mcpbfile in a host that supports MCPB Node bundles. Enter the key into the host's private Feeduna access-key field. The bundle includes its production JavaScript dependencies. Your host must provide Node.js 22 or later. Other MCP hosts can run the bundledsrc/cli.mjsdirectly with Node andFEEDUNA_API_TOKENin a private environment.Refresh the host's tool list. Only tools allowed by your key are returned.
Never put the key in source control, a prompt, a URL or shared configuration. Revoke it in Feeduna when you no longer need the integration. This bundle fixes the API destination to https://app.feeduna.com. No API key is included.
Related MCP server: supportbridge-customer
Tools
Tool | Scope | Effect |
|
| Read app details and installation guidance |
|
| Read one bounded page of feedback |
|
| Read one receipt by UUID |
|
| Read one bounded export page |
|
| Create a feedback receipt |
Tool discovery and every call recheck the key. Expiry, revocation, app scope, trial/subscription state and service allowances remain enforced by Feeduna. Pagination is explicit. A submission uses a stable receipt UUID: after a timeout, retry only the same UUID and identical content. A timeout does not prove failure. No automatic write retries are performed.
The connector never installs code, sends issues to Linear, implements changes, manages keys or changes billing. Feeduna's Linear delivery requires an owner to review and send the issue in the app. Website, feature, data-record and data-result context are supported by the feedback API; see https://app.feeduna.com/docs for the request schema and examples.
Trial and pricing
Feeduna offers an open 14-day trial without a card or automatic charge. The site displays an approximate USD price; the paid subscription is invoiced and charged at EUR25 per month. Paid checkout currently supports US businesses. Connector source licensing does not grant a Feeduna subscription or waive service terms.
Data and security
Using this connector makes feedback available to your chosen MCP host and model. Choose an appropriate provider and grant only the permissions it needs. Treat reporter text, links and context as untrusted data, not instructions or authority for downstream actions. The connector marks returned content accordingly and does not follow reported links. Privacy: https://app.feeduna.com/privacy.
Credentials are sent only to the configured API origin, and redirects are refused. API calls time out after 12 seconds; responses are capped at 4 MiB, inbound MCP messages at 64 KiB and concurrent operations at four. Errors are sanitized. No tokens, report bodies or raw API error bodies are logged by the connector. Standard output is reserved for MCP protocol traffic, which includes requested feedback. Your host controls its own storage and logging.
Dependencies and licence
This thin connector is licensed under MIT; see LICENSE. That licence covers only
the connector, not the Feeduna backend, hosted service, brand or customer data.
Bundled production dependencies retain their own licences:
@modelcontextprotocol/server 2.4.0 and @modelcontextprotocol/core 2.4.0
(Apache-2.0), and zod 4.6.7 (MIT). Their licence files are retained in
node_modules. Dependency versions and integrity hashes are in npm-shrinkwrap.json.
The SDK handles MCP stdio and protocol negotiation. This release candidate was checked with a synthetic local API fixture; that is not evidence of installation in a particular customer MCP host. See the publisher's release evidence for exact validation scope.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Unofficial remote MCP server for Less Annoying CRM: OAuth 2.1, read-only grants, 10 tools.
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
Related MCP Servers
FlicenseNot gradedqualityCmaintenanceA remote MCP server that lets MCP clients self-register over OAuth 2.1 and call read-only tools for organization identity, place and region browsing, dashboards, metrics, and ranking, forwarding the caller's own Auth0 token so each service still sees the real user. It also exposes a bearer pass-through surface for first-party apps holding an existing token.-- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to discover and invoke tools for fictional customer lookup and simulated USD refunds, with strict argument validation, business-rule checks, and SQLite-backed audit persistence.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to sign in, list workspaces, and inspect workspace-scoped review findings and hosted runs. It can also prepare and, after explicit user confirmation, start or rerun an existing hosted pull-request review without exposing raw diffs, full reports, artifacts, credentials, or prompt text.2 npm-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to securely connect to your data through a remote deployment with OAuth 2.1 and PKCE, configurable sign-in, read/write consent, and audit logging. It exposes public tools without sign-in and authenticated tools that respect each user's permissions while validating arguments and recording every call.Apache 2.0