Particl MCP
Particl MCP gives agents read-only access to authorized market intelligence covering companies, products, pricing, sales estimates, and marketing activity.
Verdict
Common use cases
- Audit marketplace listing performance across sellers
- Monitor wallet balances before vendor payouts
- Pull transaction logs for compliance reviews
- Check escrow status on pending orders
- Summarize weekly blockchain activity for reports
Integration
- Vendor
- Particl MCP
- Category
- other
- Auth
- OAUTH2
- Composio slug
particl_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Browse MCP Servers. 2. Search for 'Particl' and click Connect. 3. You'll be redirected to Particl's OAuth consent screen — log in with your Particl account credentials. 4. Review the requested scopes (typically read access to wallet data and marketplace listings) and click Authorize. 5. Switchy redirects you back and confirms the connection is live. 6. Open any Project and type '@Particl' in the chat to verify the integration responds. 7. Try a test query like '@Particl show my wallet balance' to confirm data flows correctly. 8. If the MCP doesn't respond, return to Settings > Integrations, disconnect Particl, and reconnect to refresh the OAuth token.
What teammates see: by default, memories from Particl 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
Wallet Balance Check
@Particl show me the current balance for all wallets in my account, broken down by currency type.
Recent Transaction Summary
@Particl list my 20 most recent transactions, including date, amount, and counterparty address.
Active Listings Overview
@Particl retrieve all my active marketplace listings with current prices and stock levels.
Escrow Status Report
@Particl show me all orders currently in escrow, with buyer info and expected release dates.
Weekly Activity Digest
@Particl generate a summary of my account activity for the last 7 days, including total transaction volume and new listings.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Particl search for recent customer feedback mentions about our mobile checkout flow from the last 30 days
Found 47 feedback items mentioning mobile checkout across support tickets, app reviews, and social mentions. Top themes: 18 users reported confusion at the payment method selection step, 12 mentioned slow load times on older Android devices, 8 praised the new Apple Pay integration. Average sentiment score: 3.2/5. This is an illustrative example—actual results depend on your connected data sources and feedback volume.
This example assumes Particl aggregates feedback from multiple channels. OAuth scope must include read access to all relevant sources (support system, review platforms, social APIs). Response time varies with dataset size—large accounts may see 5-10 second delays on broad searches.
@Particl create a new insight report titled 'Q1 Feature Requests' and tag all feedback items mentioning 'dark mode' or 'offline access'
Created report 'Q1 Feature Requests' with 34 tagged items. Breakdown: 21 requests for dark mode (12 from iOS users, 9 from web), 13 requests for offline access (mostly from field sales team). Report is now available in your Particl dashboard under Custom Reports. This is an illustrative example—actual tagging accuracy depends on your feedback data structure.
This write action modifies your Particl workspace. OAuth scope must include write permissions for reports and tags. The MCP cannot undo report creation—verify your prompt before running. Tagging logic uses keyword matching, so ambiguous terms may produce false positives.
@Particl analyze sentiment trends for our 'onboarding' feature over the past 6 months and draft a summary for the product team
Sentiment analysis shows onboarding feedback improved from 2.8/5 (Oct-Nov) to 4.1/5 (Feb-Mar). Key driver: the tutorial video added in December correlates with a 32% drop in 'confusing' mentions. Remaining pain point: 9% of users still report difficulty connecting third-party tools. Draft summary: 'Onboarding sentiment up 46% since Q4. Video tutorial a clear win. Next focus: streamline integrations setup—current friction point for 1 in 11 new users.' This is an illustrative example based on hypothetical trend data.
This synthesis example pairs Particl's data with the AI's summarization. Accuracy depends on feedback volume and tagging consistency in your account. The AI cannot verify statistical claims—treat the draft as a starting point requiring human review before sharing with stakeholders.
Use-case deep-dives
When OAuth2 access matters more than tool count
A 3-person startup doing customer discovery interviews needs a shared workspace where everyone can pull data without passing API keys around Slack. Particl MCP uses OAuth2, which means each team member authenticates once and the workspace inherits those permissions cleanly. This matters when you're moving fast and don't want to onboard a junior PM by handing them a .env file. The trade-off: we don't yet know what tools this MCP exposes, so you're betting on the vendor's roadmap. If your workflow depends on specific integrations today, wait until the tool list populates. If you need secure multi-user access to *something* Particl connects and can adapt as they ship, this is the right foundation.
OAuth2 for teams that can't share service accounts
A 6-person ops team at a healthcare SaaS needs to query internal systems without violating their SOC2 audit requirements around shared credentials. Particl MCP's OAuth2 flow means each action in Switchy traces back to an individual user, not a bot token floating in a shared doc. This is the scenario where auth method trumps feature depth: if your compliance officer says 'no shared API keys,' you need OAuth2 even if the MCP's tool surface is still growing. The boundary: if Particl doesn't connect to your specific system yet, OAuth2 alone won't help. Check their integrations list first, then decide if the auth model justifies the wait for missing tools.
When you need shared access, not shared secrets
A 5-person growth team—PM, designer, two engineers, one marketer—runs weekly campaign retros in Switchy and needs to pull metrics from three different platforms. Particl MCP's OAuth2 setup means the marketer authorizes their ad account, the PM authorizes the analytics tool, and everyone sees the same data without credential sprawl. This works when your team is small enough that individual auth makes sense but large enough that passing tokens is a security risk. The catch: we don't know which platforms Particl supports yet. If your stack is standard (Google, Meta, Stripe), odds are good. If you're on niche tools, confirm coverage before committing.
Frequently asked
What does Particl MCP do in Switchy?
Particl MCP connects your Particl account to Switchy's AI workspace, letting your team query and interact with Particl data through natural language. Since the specific tools aren't documented yet, expect typical read/write operations once the integration matures. You authenticate once via OAuth2, then any team member can use it in shared conversations.
Do I need admin rights to connect Particl MCP?
You'll need whatever Particl account permissions OAuth2 requires during the authorization flow. Most OAuth2 integrations ask for user-level consent, not admin, but Particl may request elevated scopes if it touches org-wide data. Check the permission screen when you click Connect — if you can't grant the scopes, loop in someone who can.
Can Particl MCP write data back to my Particl account?
That depends on which OAuth2 scopes Particl grants and which tools the MCP exposes. Many MCPs start read-only, then add write operations later. Until Switchy documents the available tools, assume read access and test carefully before relying on mutations in production workflows.
Why use Particl MCP instead of Particl's API directly?
Particl MCP wraps the API in a conversational interface, so your team asks questions in plain English instead of writing code. You skip authentication boilerplate, rate-limit handling, and response parsing. Trade-off: you're limited to the tools the MCP exposes, so complex custom workflows still need the raw API.
Does connecting Particl MCP count against my Switchy plan limits?
MCP connections themselves don't count as seats. You pay for the team members using Switchy, not the number of integrations. However, heavy usage of Particl MCP in conversations consumes your plan's message or token allowance, just like any other AI interaction in the workspace.