MarcoPolo MCP
MarcoPolo MCP lets agents securely query, correlate, analyze, and act on authorized data across databases, warehouses, cloud storage, and SaaS applications.
Verdict
Common use cases
- Summarize recent team updates from channels
- Find shared files by topic or date
- Surface context from async conversations
- Track project milestones across threads
- Identify who contributed to a discussion
Integration
- Vendor
- MarcoPolo MCP
- Category
- other
- Auth
- OAUTH2
- Composio slug
marcopolo_mcp
Tools
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find MarcoPolo MCP in the directory and click Connect. 3. You'll be redirected to MarcoPolo's OAuth consent screen — sign in with your MarcoPolo account. 4. Grant the requested scopes, which typically include read access to channels, files, and user profiles. 5. After authorizing, you'll return to Switchy and see a confirmation that MarcoPolo MCP is connected. 6. Open any Project and type '@MarcoPolo' followed by a question like 'what files were shared in the design channel this week' to test the connection. 7. If the AI responds with MarcoPolo data, the integration is live and ready to use across all Projects in your workspace.
What teammates see: by default, memories from MarcoPolo MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Weekly Channel Recap
@MarcoPolo summarize the key updates and decisions from the #product channel in the last seven days.
Locate Shared Files
@MarcoPolo find all design mockups shared in the #design channel this month.
Thread Participant List
@MarcoPolo list everyone who posted in the 'Q1 planning' thread and what they discussed.
Extract Action Items
@MarcoPolo review the #engineering channel from the past three days and pull out any action items or deadlines mentioned.
Cross-Channel Search
@MarcoPolo search all channels for mentions of 'budget approval' in the last two weeks.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@MarcoPolo what's the current status of our team's active projects and any blockers we should address today?
Based on your MarcoPolo workspace, you have 4 active projects. Project Alpha is on track with 12 completed tasks this week. Project Beta has 2 blockers: waiting on design approval and a dependency on the API team. Project Gamma shows no recent activity in 5 days. Project Delta just kicked off yesterday with 3 tasks assigned. The most urgent item is resolving Beta's design approval—it's blocking 4 downstream tasks.
This example shows MarcoPolo's ability to aggregate project state across your workspace. OAuth2 scope must include read access to projects and tasks. The response reflects data visible to your authenticated account—teammates with different permissions may see different results.
@MarcoPolo create a new task in Project Alpha: 'Review Q1 analytics dashboard' assigned to Sarah, due Friday
Task created in Project Alpha. Title: 'Review Q1 analytics dashboard'. Assigned to Sarah Chen. Due date: Friday, January 17, 2025. Task ID: ALPHA-847. I've set the priority to normal by default. Sarah will receive a notification about this assignment. You can view or edit this task at marcopolo.app/tasks/ALPHA-847.
This demonstrates MarcoPolo's write capability. The MCP creates the task immediately—there's no undo within the chat. Your OAuth2 token needs project write permissions. If Sarah isn't a member of Project Alpha, the assignment will fail and you'll need to add her first.
@MarcoPolo analyze our sprint velocity over the last 3 months and suggest whether we should adjust our capacity planning
Reviewing your last 3 sprints: Sprint 12 completed 34 story points, Sprint 13 completed 29 points, Sprint 14 completed 31 points. Average velocity: 31.3 points per sprint with 8% variance. Your current Sprint 15 has 38 points planned—that's 22% above your average. Based on this trend, I'd recommend planning 30-32 points per sprint to reduce risk of incomplete work. The variance is low, which suggests your estimates are consistent. Consider whether the Sprint 15 overage accounts for team availability or if it needs adjustment.
This example pairs MarcoPolo's historical data with AI reasoning to generate actionable insights. The analysis quality depends on how consistently your team logs completed work. MarcoPolo must have read access to sprint history, and the AI interprets patterns—verify recommendations against your team's context before acting.
Use-case deep-dives
When OAuth2 matters more than the tool count
A 6-person support team split between San Francisco and Berlin needs to hand off context without Slack threads spiraling. MarcoPolo MCP uses OAuth2, which means each agent action ties to a real user identity—critical when you're auditing who approved what at 3am CET. The trade-off: we don't yet know what tools this MCP exposes, so you're betting on the auth model before the feature set is public. If your compliance or HR policy requires named actors in logs (healthcare, finance, HR tools), that OAuth2 gate is worth the early-adopter risk. If you just need fast reads with no audit trail, wait until the tool list ships.
Testing a new MCP before the docs catch up
A 3-person ops team wants to prototype an integration with a vendor API that just launched an MCP server. MarcoPolo MCP is in the directory, but the tool inventory hasn't populated yet—common for new or beta servers. The OAuth2 flow is live, so you can connect and explore what the server actually returns in real sessions. This scenario works if you're comfortable reading raw MCP responses and writing your own prompts to discover capabilities. The buying call: if your team has one person who can read JSON and iterate on agent instructions, this is a low-risk pilot. If you need polished docs and known tools before you commit, bookmark this and check back in two weeks.
When OAuth2 beats API keys for team turnover
A 12-person agency rotates contractors every quarter and needs to revoke access without regenerating shared API keys. MarcoPolo MCP's OAuth2 flow means each Switchy user authenticates individually—when someone leaves, you revoke their token in the OAuth provider, and no one else's agents break. The downside: we don't yet know if this MCP's tools justify the OAuth overhead for your workflow. If your team changes shape often (agencies, seasonal teams, internships) and you're already managing OAuth apps for Slack or Google, the auth model alone makes this worth a test connection. If your team is stable and you'd rather copy-paste one API key, wait for the tool list to prove the value.
Frequently asked
What does MarcoPolo MCP do in Switchy?
MarcoPolo MCP connects your team's MarcoPolo account to Switchy's AI workspace. Since tool details aren't finalized yet, expect it to expose MarcoPolo's core features—likely location sharing, coordination workflows, or team communication—directly to your AI agents. You'll authenticate once via OAuth2, then your team can query or act on MarcoPolo data without leaving Switchy.
Do I need admin permissions to connect MarcoPolo MCP?
You'll need whatever OAuth2 permissions MarcoPolo requires for the scopes this MCP requests. Typically that means owner or admin access if the integration touches team-wide data. If you're connecting a personal MarcoPolo account, standard user permissions should work. Check MarcoPolo's OAuth consent screen during setup to see exactly what you're granting.
Can MarcoPolo MCP send messages or update locations automatically?
That depends on which tools MarcoPolo exposes through the MCP. If the integration includes write tools, your AI agents can trigger actions like updating a location or sending a check-in. If it's read-only, you'll get data queries but no automated changes. The tool list will clarify this once the integration is live.
Should I use MarcoPolo MCP or just call the MarcoPolo API directly?
Use the MCP if you want your AI agents to interact with MarcoPolo without writing custom API code. The MCP handles OAuth refresh, rate limits, and response parsing for you. Call the API directly if you need endpoints the MCP doesn't expose yet, or if you're building a standalone integration outside Switchy.
Who on my team should connect the MarcoPolo account?
Whoever owns or administers your team's MarcoPolo account should connect it. That person's OAuth token will authenticate all requests from Switchy. If your team uses multiple MarcoPolo workspaces, connect the one your AI agents need to query most often. You can always reconnect with a different account later.