feedbug-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEEDBUG_API_URL | No | Feedbug API base URL. Only needed for self-hosting. | https://api.feedbug.app |
| FEEDBUG_PROJECT_KEY | Yes | Feedbug project key (pk_...), available on your project page at https://feedbug.app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| feedbug_list_bugsB | List bugs reported via FeedBug widget. Returns Linear identifier (e.g. PRE-13), title, status, page URL, and component path for each bug. |
| feedbug_get_bugA | Get full details of a specific bug including HTML context, screenshot URL, viewport, and user agent. |
| feedbug_get_html_contextA | Get the HTML/DOM context captured when the bug was reported. Returns CSS selector path, framework component path (Vue/React/Angular/Svelte), clicked element details (tag, classes, text, attributes), ancestor elements, and sibling elements. Use this to trace a bug back to source code. |
| feedbug_get_diagnosticsA | Get browser diagnostics for a bug: page URL, viewport size, user agent, and reporter name. |
| feedbug_resolve_bugA | Mark a bug as resolved after fixing it. Use this when you have fixed the issue reported in a FeedBug bug. |
| feedbug_add_commentA | Add a comment to a bug. Use this to provide updates, ask questions, or document your fix. |
| feedbug_get_replayA | Get the session replay URL for a bug. The replay shows the last 30 seconds of user activity before the bug was reported. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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/joffreyBerrier/feedbug-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server