Pivotal Tracker MCP. Manage your entire agile backlog via conversation.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Pivotal Tracker connects your entire agile development workflow directly into any AI client. Use natural conversation to list, retrieve, create, and update stories, features, and bugs across all your projects.
This server gives you full control over the backlog—you can check status or change task states without ever leaving your IDE or chat window.
Retrieves a list of stories (bugs, features, etc.) based on specified project IDs or search criteria.
Generates and saves a new story record in the backlog for a specific project ID.
Changes the status of an existing story (e.g., from 'todo' to 'started').
Returns a list of all available projects and their basic metadata for quick identification.
Retrieves high-level progress data by listing associated Epics or organizational Labels within the workspace.
Returns a list of users who are members of a specific project.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Pivotal Tracker, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You connect your Pivotal Tracker workspace directly to any AI client and manage every single thing on your agile backlog using just natural conversation. This server gives you full, hands-on control over your entire project lifecycle—from the biggest Epics down to the smallest user stories—all without ever leaving your chat window or IDE.
When you hook this up via Vinkius, your AI client gains access to a set of specialized tools that talk directly to your core backlog data. You treat the whole project scope as one continuous topic; you don't need to click through menus or navigate dashboards to get what you need.
Your agent handles all the messy API calls in the background so you can focus on talking.
Story Management and Execution:
The server gives you three ways to handle stories—the core unit of work. First, if you just want to see what's going on, you use list_stories. You tell your agent which project IDs or search criteria you need, and it returns a precise list of every story—whether that’s a bug, a feature request, or some other type of chore—that matches.
Second, if the team finds something new, you don't have to go in and manually enter it; create_story lets you generate and save an entirely new story record right into the backlog for any specific project ID. Third, when work actually moves, you use update_story_state. You tell your agent which existing story needs its status changed—like moving a task from 'To Do' straight to 'In Progress.' It updates that state instantly.
Project Scope and Oversight:
You need context before you can change anything. The server lets you nail down the boundaries of work with list_projects, which returns a complete list of every project in your workspace along with basic metadata, so you're always sure what projects are even available to you. To figure out who owns what task or who needs to be looped into a discussion, you use get_project_memberships.
You give it a project ID, and it spits back a clear list of every user who’s part of that specific team.
For the big picture view, you can pull high-level progress data by calling list_epics_and_labels. This tool retrieves all the associated Epics or organizational Labels tied to your work, letting you understand how large chunks of functionality are categorized and progressing across different parts of the business. You're checking scope visibility at the highest level without running a single report.
How It Works in Practice:
After you subscribe to this server on Vinkius and plug in your Pivotal Tracker API Token, your AI client is primed with these specialized tools. Instead of writing complicated JSON payloads or making multiple manual requests, you just talk to your agent. You can say things like: 'List all active stories for Project Gamma,' or 'Update story 987654321 to started.' The agent recognizes the intent, executes the right API calls—whether it's list_stories, update_story_state, or anything else—and gives you the direct answer without fail.
You keep your focus on conversation, and the server handles the whole messy process of managing state changes across every story in the backlog.
How Pivotal Tracker MCP Works
- 1 Subscribe to the Pivotal Tracker server on Vinkius and enter your API Token.
- 2 Your AI client recognizes the available tools (e.g.,
create_story,list_stories). - 3 You give a natural language prompt, and your agent executes the correct tool calls against your Pivotal data.
The bottom line is: you manage complex agile workflows using simple conversation, eliminating context switching between tools.
Who Is Pivotal Tracker MCP For?
Product Owners who need to check story status while writing requirements. Software Engineers stuck in the IDE who can't afford to switch tabs. Project Managers monitoring dozens of projects and needing a single source of truth on team assignments.
Uses list_stories or update_story_state to verify story readiness or update the backlog status while drafting PRDs.
Calls create_story immediately after finding a bug, ensuring the issue is logged with minimal interruption to coding flow. Also uses update_story_state to move tasks through development stages.
Uses list_projects and get_project_memberships to audit team capacity or determine who is assigned to which major workstream across the portfolio.
What Changes When You Connect
- Update story states instantly. Instead of clicking into Pivotal Tracker, use
update_story_stateto mark a task as 'started' or 'finished' right from your IDE chat window. - Get instant project visibility. Use
list_projectsto see all active projects and their metadata without manually navigating the dashboard tabs. - Streamline bug reporting with
create_story. When you find a flaw, ask your agent to create the story immediately—it handles the ID generation and logging for you. - Track high-level progress. Run
list_epics_and_labelsto understand how all features fall under major Epics or organizational Labels across your board. - Know who does what. Use
get_project_membershipsto audit project roles, instantly seeing the team members assigned to any given initiative.
Real-World Use Cases
The Post-Code Bug Report
A software engineer finds a bug while testing. Instead of copying the details and manually logging into Pivotal Tracker, they simply prompt their agent: 'Create a new bug story in Project XYZ called Broken login button.' The agent runs create_story, logs the issue immediately, and gets back confirmation with the new Story ID.
The Sprint Retrospective Audit
A project manager needs to quickly verify team load. They prompt: 'Show me all active projects and who is assigned to them.' The agent uses list_projects followed by multiple calls to get_project_memberships, giving the PM a single, comprehensive report on resource allocation.
The Feature Status Check
A product owner is reviewing requirements for an upcoming release. Rather than clicking through dozens of stories in the Pivotal UI, they ask their agent to list_stories for a specific project and filter by 'active'. The list comes back instantly, allowing them to verify status before writing specs.
Mid-Sprint Goal Adjustment
A development lead realizes an Epic is stalled. They ask the agent to list_epics_and_labels for that project. The resulting data immediately shows which specific stories are lagging, allowing them to reassign resources without manual searching.
The Tradeoffs
Context Switching
Having to leave your IDE (VS Code/Cursor) to open the Pivotal Tracker web app just to update a status. This breaks flow and wastes time.
→
Keep the focus in your chat client. Use update_story_state directly through your agent's prompt, moving tasks from 'todo' to 'started' without leaving your screen.
Copy-Pasting IDs
Manually copying a story ID (like 987654321) and pasting it into the chat, only for the agent to fail if the format is wrong.
→ Let your agent handle the context. Just tell it: 'Update the login flow bug to started.' The tool knows which project and story ID you mean based on conversation history.
Asking General Questions
Prompting, 'What's going on with our projects?' without defining a scope. This results in vague or incomplete data that doesn't help.
→
Always narrow the focus. Start by calling list_projects to get context, then follow up: 'For Project Alpha, list all active stories.' Specificity is key.
When It Fits, When It Doesn't
Use this server if your team lives in an agile workflow and needs deep integration between task management (Pivotal Tracker) and where you write code/write docs. You need to treat the backlog as just another API endpoint—something you can talk to, not something you have to navigate visually.
Don't use this server if your team uses Pivotal Tracker purely for simple document archiving or non-agile task lists (e.g., 'buy milk'). If your needs are only basic CRUD operations without the ability to link status changes to project context, a simpler API wrapper might suffice. This tool is built for structured development processes and requires you to use its specialized tools like list_stories and update_story_state to get real value.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Pivotal Tracker. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Updating story status shouldn't feel like opening three tabs.
Today, updating a bug's state means navigating from your chat client into the Pivotal Tracker UI. You search for the project, find the story by ID or title, click on it, and finally hit 'Start Work.' It’s three separate applications and five clicks just to move one task.
With the Pivotal Tracker MCP Server, you just talk to your agent. Your prompt—'Move bug 987654321 to started state'—is enough. The server runs `update_story_state` and confirms it instantly. You never leave your chat window.
Pivotal Tracker MCP Server: Full Control Over Your Backlog
You stop manually running reports or copying status updates into Slack channels to track progress. The agent handles the complex logic of checking project metadata, listing epics, and retrieving membership data—all in one call.
The difference is context. Your AI client doesn't just report data; it acts on it. It lets you manage your entire development process conversationally.
Common Questions About Pivotal Tracker MCP
How do I connect Pivotal Tracker to my agent using the Pivotal Tracker MCP Server? +
You subscribe to this server and provide your Pivotal Tracker API Token in the Vinkius settings. Once connected, your AI client can automatically use tools like list_stories.
Can I list all stories for a project using the Pivotal Tracker MCP Server? +
Yes, you call the list_stories tool and provide the target Project ID. The agent will return a structured list of active features, bugs, and chores.
Does the Pivotal Tracker MCP Server handle status changes? +
Absolutely. Use the update_story_state tool to change any story's state—for example, moving it from 'todo' to 'started'—without logging into the web UI.
What if I need to see who works on a project with Pivotal Tracker? +
Use the get_project_memberships tool. You just provide the Project ID, and the server returns a list of all assigned team members.
What happens when I use the Pivotal Tracker MCP Server to run a query on an invalid Story ID? +
The server returns a clear error message stating that the specified Story ID does not exist. Your AI client receives this feedback and can then prompt the user for the correct identifier.
Is there a rate limit when I list multiple stories using the Pivotal Tracker MCP Server? +
Yes, API usage is subject to standard rate limits imposed by Pivotal Tracker. If you hit that cap while listing many records, your AI client must pause before making another request.
When I use the Pivotal Tracker MCP Server to list all projects, what metadata should I expect? +
You'll receive basic details like the project ID, name, and current status. You can then make separate calls to retrieve deeper metrics or full lists of stories for any given project.
If my Pivotal Tracker API Token expires, how do I keep the connection active with the MCP Server? +
You must refresh your API token in your Profile Settings and update the server's credentials within your AI client. The agent won't connect until it uses the new, active token.
How do I find my Pivotal Tracker API Token? +
Log in to Pivotal Tracker, click on your name in the top right, go to Profile Settings, and scroll down to the API Token section.
Can I filter stories by their current state? +
Yes! Use the list_stories tool and provide a filter like state:started or state:unscheduled to narrow down the results.
Does this support checking project memberships? +
Absolutely. Use the list_memberships tool with a Project ID to see all users associated with that specific project and their roles.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Fathom
Manage AI meeting notes via Fathom — list and search meetings, retrieve transcripts and summaries, and track action items directly from any AI agent.
Apidog
Sync your Apidog workspace with your AI agent — list projects, fetch endpoint schemas, and export full OpenAPI specifications instantly.
Picktime
Equip your AI agent to manage scheduling operations. Fetch global availabilities, list locations, and manage business bookings via chat natively.
You might also like
X Ads (Twitter)
Manage your X Ads campaigns — audit accounts, line items, and analytics via AI.
Anthropic Alternative
Access Claude models via Anthropic API — send messages, count tokens, manage batches and discover models from any AI agent.
Tesla Fleet API
Physical actuator proxy mapping explicitly native commands evaluating telemetry tracking active Tesla vehicles cleanly.