Amplifier — the issue tracker where your agents do the work
Amplifier — the issue tracker where your agents do the work
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · amplifier.app
101tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://amplifier.app/mcp
Skill page: https://www.mcpbundles.com/skills/amplifier-mcp-d5d6cc57f9
Explore capabilities (101)
read 15
write 10
Showing 25 of 101
Showing 25 of 101 tools from the public preview. Connect the server to inspect the full live tool list.
List9
Get4
Create3
Update3
Delete2
Other capabilities4
Search
read
search
Search Amplifier issues, wiki pages and uploaded document filenames. This is the standard ChatGPT connector search action; use fetch with a returned id for the full record.
Search — Search Amplifier issues, wiki pages and uploaded document filenames. This is the standard ChatGPT connector search action; use fetch with a returned id for the full record.
Fetch — Fetch a single Amplifier record returned by search. Accepts ids like issue:STR-42, wiki:12 or doc:34.
List Workspaces — List every Amplifier workspace the connected user belongs to, marking the one this connection is currently bound to. Use switch_workspace to move the connection to another one. Run this the moment issues or pages you were just working with stop being found: the binding can be changed by any session sharing this credential, and things that look deleted are usually just in a workspace you are no longer bound to.
Switch Workspace — Re-bind this MCP connection to a different workspace the user belongs to. The switch persists on the connection's credential, so every later tool call — and every other session sharing that credential, including agents running right now — operates in the new workspace. Issue identifiers, teams, projects and wiki pages from the previous workspace are no longer reachable until you switch back, so switch back when you are done rather than leaving the connection parked somewhere else.
List Teams — List all teams in the workspace. Each team has a key (e.g. STR) used to prefix issue identifiers like STR-42.
List Workflow States — List the workflow states (Backlog, Todo, In Progress, In Review, Done, Canceled) for a team. Use these names as the `status` for issues.
List Projects — List projects in the workspace.
Get Project — Get a project's details, progress and issue count.
Create Project — Create a new project.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
What is the Amplifier — the issue tracker where your agents do the work MCP server?
Amplifier — the issue tracker where your agents do the work is an MCP server at amplifier.app. MCPBundles discovered 101 tools on the live endpoint.
How do I connect Amplifier — the issue tracker where your agents do the work to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
Operate this server?
Request removal if you do not want Amplifier — the issue tracker where your agents do the work listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Amplifier — the issue tracker where your agents do the work?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
Delete Project — Delete a project. Its issues are kept but unlinked from the project.
List Issue Views — List saved issue views — named, shareable filter + display presets over the workspace's issues. A workspace view opens at /views/<id>; a project view is a tab on its project, at /projects/<project>?view_id=<id>.
Get Issue View — Get one saved issue view: its scope, URL, filters (resolved to readable names) and display options.
Create Issue View — Create a saved issue view — a named set of filters plus display options over the workspace's issues, with its own shareable URL. Pass `project` to make it a saved-view tab on that project (filtered to that project's issues); pass `team` to narrow a workspace view to one team; pass neither for a workspace-wide view. Filter values are matched by name, not id: a status by workflow-state name (e.g. 'In Progress' — on a workspace view it matches that state in every team), an assignee by 'me'/email/me
Update Issue View — Update a saved issue view. Only the keys you pass change; pass an empty array for a filter to clear it. Filter values are matched by name, not id: a status by workflow-state name (e.g. 'In Progress' — on a workspace view it matches that state in every team), an assignee by 'me'/email/member name, a priority by urgent/high/medium/low/no_priority, a label by name, and a project by name or id.
Delete Issue View — Delete a saved issue view. The issues it showed are untouched.
List Labels — List labels available for tagging issues.
List Todos By Tag — List non-completed todos tagged with one or more labels. Use this when the user asks for open todos by tag/label.
List Issues — List/search issues (todos). Returns identifier, title, status, priority, assignee and due date.
List Project Issues — Pull issues grouped by project — narrow to specific projects, to specific statuses, or a combination of the two. Both `project` and `status` accept one value or a list, so you can ask for e.g. Todo + In Progress across the Rails App and iOS App projects in one call. Omit `project` to cover every project (plus a 'No project' group); omit `status` to default to open issues.
Get Issue — Get full details of a single issue including its parent, sub-issues, description and comments.
Get Issue Prompt — Render an issue as a ready-to-work prompt — the exact text the web app's "Copy as prompt" button produces. Fills a prompt template (the workspace's default Issue template, or one you name with `template`) with the issue's title, description and metadata, and rewrites any pasted-image URLs to absolute links you can fetch. Use this to pick up an issue as a self-contained task rather than assembling the prompt yourself from get_issue.
Create Issue — Add a new issue (todo). Returns the new identifier. Only `title` is required. To create a sub-issue, pass `parent` — the new issue is filed under it and inherits its team unless you name one.
Update Issue — Update an existing issue. Pass the identifier plus any fields to change. Set `parent` to turn it into a sub-issue (or move it under a different parent), or 'none' to detach it back to the top level.
Set Claude Session — Attach a Claude Code session to an issue and record when work started/finished. Attaching a session id automatically marks the issue as being actively worked on (its row flashes in the list) unless you pass started_at explicitly — so just attaching your session at the start is enough. Call this again with finished_at:'now' when you're done to stop the indicator. Pass 'now' to stamp the current time, an ISO8601 timestamp to set an exact time, or 'none' to clear a field.
Showing the first 25 tools — full list and schemas: Directory API.
How many tools does Amplifier — the issue tracker where your agents do the work provide?
MCPBundles probed 101 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Amplifier — the issue tracker where your agents do the work require?
Amplifier — the issue tracker where your agents do the work may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.