Sidetracker
Sidetracker is a cookie-free web analytics platform that tracks website visitors, sales funnels, and customer journeys. It provides real-time session tracking, lead management, conversion tracking, and marketing campaign analytics without relying on cookies.
Verdict
Common use cases
- Prep standup by summarizing today's tasks
- Find overdue items across all lists
- Check sprint backlog status mid-week
- Surface blockers from team task lists
- Compare list progress for planning meetings
Integration
- Vendor
- Sidetracker
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 2
- Composio slug
sidetracker
Tools
- Get List Details
Tool to retrieve details of a specific list by its id. use after confirming the list id is correct.
- Get Lists
Tool to retrieve lists from sidetracker. use when you need to paginate through available lists.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for Sidetracker in the MCP directory and click Connect. 3. You'll be prompted to enter a Sidetracker API key — generate one by logging into your Sidetracker account, going to Settings > API Keys, and clicking Create New Key. 4. Paste the key into Switchy and click Authorize. 5. Switchy will confirm the connection with a green checkmark. 6. Open any Space, type '@Sidetracker get lists' in the chat, and send — the AI will return your available lists to prove the connection works. 7. From there, ask the AI to fetch details for a specific list by referencing its ID from the first response.
What teammates see: by default, memories from Sidetracker are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Active Lists
@Sidetracker get lists and show me the name and ID of each one, sorted by most recently updated.Open in a Space →
Summarize Sprint Backlog
@Sidetracker get list details for list ID 12345 and summarize the open items, grouping them by priority if available.Open in a Space →
Find Overdue Tasks
@Sidetracker get lists, then for each list check if any items are overdue and report them with their due dates.Open in a Space →
Compare Team Workloads
@Sidetracker get lists for our team, then show me how many open vs closed items each list has so we can rebalance work.Open in a Space →
Extract Blockers
@Sidetracker get list details for list ID 67890 and pull out any items marked as blocked or waiting on someone else.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Sidetracker show me all my lists so I can see what I'm tracking right now
Found 4 active lists in your Sidetracker account: 'Sprint Backlog' (12 items), 'Tech Debt' (8 items), 'Customer Requests' (5 items), and 'Documentation TODOs' (3 items). Each list includes creation date and item count. This example reflects a typical account state — your actual lists will vary based on what you've created.
This read-only query requires an API key with list-read permissions. Sidetracker returns paginated results, so accounts with many lists may need follow-up prompts to see the full catalog. Useful for getting oriented before diving into specific list details.
@Sidetracker pull the full details for my 'Sprint Backlog' list including all items and their status
Retrieved 'Sprint Backlog' list (ID: list_abc123). Contains 12 items: 7 marked incomplete, 5 completed. Sample items include 'Refactor auth middleware' (incomplete, added 3 days ago) and 'Update API docs' (completed yesterday). This illustrative output shows the structure — your list's actual items and metadata will differ.
Requires knowing the exact list ID, which you can get from the 'Get Lists' tool first. This two-step workflow (find list ID, then fetch details) is common when working with Sidetracker. The response includes item-level metadata like creation timestamps and completion status.
@Sidetracker check my 'Tech Debt' list and summarize the top 3 most urgent items based on how long they've been open
Analyzing 'Tech Debt' list: oldest open items are 'Migrate legacy database schema' (open 47 days), 'Replace deprecated OAuth library' (open 31 days), and 'Fix memory leak in background worker' (open 28 days). These three represent the longest-standing technical debt in your backlog. This synthesis combines Sidetracker's raw data with AI reasoning about urgency.
This example pairs Sidetracker's list-retrieval capability with the AI's ability to sort and prioritize. The MCP provides the data; the AI interprets 'most urgent' based on age. Useful for surfacing neglected work, though urgency heuristics are simplistic without external context like business impact.
Use-case deep-dives
When Sidetracker fits a lean backlog workflow
A 3-person dev team running two-week sprints needs to pull backlog items into standup without opening five browser tabs. Sidetracker's two-tool setup—Get Lists and Get List Details—works when your workflow is simple: one or two active lists (current sprint, next up) and you're just reading state, not manipulating tickets. The API key auth means any team member can connect in under a minute. This breaks down if you need to update tasks, add comments, or query across more than a handful of lists—Sidetracker doesn't expose write operations or search. If your backlog lives in a single Sidetracker list and you're using Switchy to triage what's next, this MCP gets you 80% of the value with zero setup friction.
Sidetracker for support-to-dev ticket routing
A support lead at a 10-person SaaS company uses Sidetracker to maintain a 'Bugs from Customers' list that engineering pulls from weekly. The Get Lists tool surfaces the queue, Get List Details shows ticket metadata (customer name, urgency tag, repro steps). This works when the handoff is low-frequency—once or twice a week—and the list structure is flat. The limitation: if support needs to update ticket status or add follow-up notes after engineering picks it up, they're back in the Sidetracker UI. The MCP is read-only. For teams where the handoff is a one-way push and the volume stays under 30 tickets a week, Sidetracker in Switchy keeps the context in one place without forcing engineers to context-switch.
When Sidetracker handles solo project pipelines
A solo designer or developer juggling 4-6 client projects uses Sidetracker to track intake requests, active work, and invoicing stages. Each project is a list; Get Lists shows the pipeline at a glance, Get List Details pulls the specifics when a client asks for a status update. This scenario is Sidetracker's sweet spot: one person, low complexity, read-heavy workflow. The two-tool limit doesn't hurt because there's no collaboration overhead. The trade-off: if project count climbs above 10 or you need to automate task creation from inbound emails, Sidetracker's MCP won't scale—you'll need a tool with write access and webhooks. For freelancers who want their project state in Switchy without learning Zapier, this is the fastest path.
Frequently asked
What does the Sidetracker MCP do in Switchy?
It connects your Sidetracker account so AI agents can read your task lists and retrieve list details. The MCP gives agents two tools: one to fetch all your lists (with pagination) and another to pull details for a specific list by ID. Agents can't create or modify tasks — this is read-only access to help them understand your project context.
Do I need an API key to connect Sidetracker?
Yes. You'll generate an API key from your Sidetracker account settings and paste it into Switchy during setup. The key stays encrypted in your workspace. Anyone on your team who connects Sidetracker will need their own API key — Switchy doesn't share credentials across users.
Can the Sidetracker MCP create or update tasks?
No. The MCP only reads list metadata and task details. If an agent needs to add a task or change a status, you'll have to do that manually in Sidetracker or ask the agent to draft the change for you to copy over. This keeps your task data safe from accidental edits.
Why use this instead of just opening Sidetracker in a browser tab?
Agents can pull task context automatically during a conversation without you switching windows or copying list IDs. If you're asking an AI to help prioritise work or summarise blockers, the MCP lets it reference your actual Sidetracker data instead of forcing you to paste screenshots or lists manually.
Who on my team should connect the Sidetracker MCP?
Anyone who wants AI agents to see their Sidetracker lists. Each person connects their own API key, so agents only access the lists that user can see. If your team shares a single Sidetracker account, one connection is enough — but most teams have individual accounts and connect separately.