{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-bolide-aimcp","slug":"npm-bolide-aimcp","name":"@bolide-ai/mcp","type":"mcp","url":"https://www.npmjs.com/package/@bolide-ai/mcp","page_url":"https://unfragile.ai/npm-bolide-aimcp","categories":["mcp-servers"],"tags":["bolideai","mcp","modelcontextprotocol","marketing","automation"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-bolide-aimcp__cap_0","uri":"capability://tool.use.integration.mcp.server.initialization.and.protocol.handshake","name":"mcp server initialization and protocol handshake","description":"Implements the ModelContextProtocol server specification to establish bidirectional communication with MCP clients (Claude, other LLM applications). Handles protocol version negotiation, capability advertisement, and message routing through stdio or HTTP transports. Uses JSON-RPC 2.0 message framing to serialize tool definitions and responses between client and server.","intents":["Set up a marketing automation server that Claude and other MCP clients can discover and connect to","Expose marketing tools to LLM applications without building custom API integrations","Enable Claude to call marketing functions directly within conversations"],"best_for":["Teams building Claude-integrated marketing workflows","Developers adding marketing capabilities to existing MCP-compatible LLM applications","Marketing automation platforms seeking LLM-native interfaces"],"limitations":["Requires MCP client support — not compatible with non-MCP LLM applications","Protocol overhead adds ~50-100ms per tool invocation for serialization/deserialization","No built-in authentication — relies on client-side access control"],"requires":["Node.js 16+","MCP-compatible client (Claude Desktop, or custom MCP client implementation)","@modelcontextprotocol/sdk package"],"input_types":["JSON-RPC requests","tool invocation parameters"],"output_types":["JSON-RPC responses","tool result objects with structured data"],"categories":["tool-use-integration","mcp-server"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-bolide-aimcp__cap_1","uri":"capability://automation.workflow.email.campaign.creation.and.management.via.tool.calling","name":"email campaign creation and management via tool calling","description":"Exposes email campaign CRUD operations as MCP tools that LLM clients can invoke. Implements schema-based function definitions for creating campaigns with parameters like subject, body, recipient lists, and scheduling. Routes tool calls to underlying marketing platform APIs (likely Bolide's own backend or third-party services like Mailchimp/SendGrid) and returns structured campaign metadata and status.","intents":["Create email campaigns programmatically through Claude conversations without leaving the chat interface","Let Claude draft and schedule email content based on user prompts","Retrieve campaign status and performance metrics via natural language queries"],"best_for":["Marketing teams using Claude for campaign ideation and execution","Solo marketers automating repetitive campaign setup tasks","Agencies building client-facing LLM-powered marketing dashboards"],"limitations":["Campaign complexity limited by LLM context window — large recipient lists or complex segmentation may require pre-staging","No real-time campaign editing — changes require creating new campaign versions","Dependent on underlying email service provider availability and rate limits"],"requires":["Bolide AI account or connected email service provider credentials","MCP client with tool-calling support","Valid email sender configuration in upstream service"],"input_types":["campaign name (string)","email subject (string)","email body (HTML or plain text)","recipient list (array of email addresses or segment ID)","send time (ISO 8601 timestamp or 'immediate')"],"output_types":["campaign ID (string)","campaign status (enum: draft, scheduled, sent, failed)","creation timestamp","preview URL"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-bolide-aimcp__cap_2","uri":"capability://data.processing.analysis.contact.and.audience.segmentation.via.tool.based.queries","name":"contact and audience segmentation via tool-based queries","description":"Provides MCP tools for querying, filtering, and segmenting contact databases based on attributes (demographics, engagement history, purchase behavior). Implements parameterized filtering logic that translates natural language intent (e.g., 'high-value customers who opened emails in the last 30 days') into database queries. Returns segment metadata including size, engagement metrics, and preview samples.","intents":["Ask Claude to identify target audiences for a campaign based on customer attributes","Dynamically segment contacts based on behavioral criteria without manual list building","Preview segment composition before launching a campaign to that audience"],"best_for":["Data-driven marketers who want LLM-assisted audience analysis","Teams managing large contact databases with complex segmentation rules","Marketing ops building audience-first campaign workflows"],"limitations":["Query performance depends on underlying database indexing — complex multi-attribute filters may timeout on large datasets (>1M contacts)","No real-time audience updates — segments reflect data as of last sync","Limited to pre-defined contact attributes — custom fields require schema updates"],"requires":["Contact database with indexed fields (email, created_at, engagement_score, etc.)","Bolide AI or connected CRM with query API","MCP client with structured tool parameter support"],"input_types":["filter criteria (key-value pairs or JSON query object)","attribute names (string)","comparison operators (eq, gt, lt, contains, in)","date ranges (ISO 8601 or relative: 'last_30_days')"],"output_types":["segment ID (string)","contact count (integer)","engagement metrics (JSON object with open_rate, click_rate, etc.)","sample contacts (array of contact objects, limited to 10-100)"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-bolide-aimcp__cap_3","uri":"capability://automation.workflow.sms.and.push.notification.campaign.execution","name":"sms and push notification campaign execution","description":"Extends campaign automation to SMS and push notification channels via MCP tools. Implements channel-specific schema definitions (SMS character limits, push notification title/body constraints) and routes messages through appropriate service providers (Twilio, Firebase, etc.). Handles delivery tracking, bounce management, and opt-out compliance per channel.","intents":["Create and send SMS campaigns alongside email campaigns in a single conversation","Compose push notifications with Claude and schedule delivery across mobile platforms","Track delivery status and engagement metrics across multiple channels"],"best_for":["Omnichannel marketing teams coordinating campaigns across email, SMS, and push","Mobile-first businesses prioritizing SMS and push over email","Compliance-conscious teams needing built-in opt-out and consent tracking"],"limitations":["SMS character limits (160 chars standard, 153 with encoding) constrain message length — Claude may need to iteratively shorten content","Push notification delivery is best-effort — no guarantee of delivery on all devices","Requires separate credentials/accounts for each channel provider (Twilio, Firebase, etc.)","Rate limiting per provider may queue messages rather than sending immediately"],"requires":["Twilio account (SMS) or Firebase Cloud Messaging (push notifications)","Phone numbers or device tokens in contact database","Opt-in consent records per contact per channel"],"input_types":["message content (string, max 160 chars for SMS)","recipient list (phone numbers or device tokens)","channel type (enum: sms, push_ios, push_android)","send time (ISO 8601 timestamp)"],"output_types":["campaign ID (string)","delivery status (enum: queued, sent, failed, bounced)","delivery timestamp","error details (if failed)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-bolide-aimcp__cap_4","uri":"capability://data.processing.analysis.campaign.performance.analytics.and.reporting.via.natural.language.queries","name":"campaign performance analytics and reporting via natural language queries","description":"Provides MCP tools for querying campaign metrics (open rates, click rates, conversion rates, revenue attribution) and generating reports. Implements aggregation logic that translates natural language queries ('Which campaigns had the highest ROI last month?') into analytics queries. Returns structured metrics with time-series data, comparisons, and trend analysis.","intents":["Ask Claude to analyze campaign performance and identify top performers","Generate performance reports for stakeholders without manual data export","Compare campaign variants (A/B tests) to determine statistical winners"],"best_for":["Data-driven marketers who want conversational analytics","Marketing managers creating executive reports via Claude","Teams running frequent A/B tests and needing rapid performance feedback"],"limitations":["Analytics data has latency — typically 1-4 hours behind real-time due to event processing pipelines","Attribution models are simplified — multi-touch attribution not supported","Requires event tracking infrastructure (pixel, webhook, or API) to capture conversions","Statistical significance testing for A/B tests requires minimum sample sizes (typically 100+ conversions per variant)"],"requires":["Campaign event data (opens, clicks, conversions) stored in analytics backend","Conversion tracking configured (UTM parameters, pixel, or API)","Minimum 24 hours of campaign data for meaningful metrics"],"input_types":["campaign ID or date range (string or ISO 8601)","metric names (enum: open_rate, click_rate, conversion_rate, revenue, roi)","grouping dimensions (enum: campaign, channel, variant, date)"],"output_types":["metric values (number, percentage, or currency)","time-series data (array of {timestamp, value} objects)","comparison data (baseline vs variant metrics)","statistical significance (p-value, confidence interval)"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-bolide-aimcp__cap_5","uri":"capability://text.generation.language.template.management.and.content.generation.assistance","name":"template management and content generation assistance","description":"Provides MCP tools for storing, retrieving, and managing email/SMS/push templates. Implements template variable substitution (e.g., {{first_name}}, {{discount_code}}) with validation to ensure all required variables are provided at send time. Integrates with Claude's text generation to help draft template content and suggest personalization variables based on available contact attributes.","intents":["Store reusable campaign templates and retrieve them by name or category","Ask Claude to draft email templates with appropriate personalization variables","Validate templates before saving to catch missing variables or formatting errors"],"best_for":["Teams managing large template libraries across multiple campaigns","Content teams using Claude to draft templates collaboratively","Compliance-heavy industries needing template version control and audit trails"],"limitations":["Template variable syntax is rigid — only supports {{variable}} format, not conditional logic or loops","No built-in A/B testing for template variants — requires manual campaign duplication","Template preview requires sample data — Claude cannot generate previews without contact context"],"requires":["Template storage backend (database or file system)","Contact schema definition (list of available attributes for variable substitution)","MCP client with file/text handling capabilities"],"input_types":["template name (string)","template content (HTML or plain text)","channel type (enum: email, sms, push)","required variables (array of variable names)"],"output_types":["template ID (string)","template content (string)","variable list (array of {name, type, required} objects)","preview (rendered template with sample data)"],"categories":["text-generation-language","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-bolide-aimcp__cap_6","uri":"capability://automation.workflow.webhook.and.event.based.trigger.configuration","name":"webhook and event-based trigger configuration","description":"Provides MCP tools for defining event-triggered campaigns (e.g., 'send email when contact signs up', 'send SMS when purchase exceeds $100'). Implements trigger schema with event types, conditions, and action definitions. Routes trigger configurations to a workflow engine that listens for events and executes associated campaigns automatically. Supports complex conditions (AND/OR logic, time windows) and action chaining.","intents":["Configure automated campaigns triggered by customer events without writing code","Ask Claude to suggest trigger conditions based on business goals","Set up multi-step workflows (e.g., welcome email → SMS after 2 days → push notification after 1 week)"],"best_for":["Marketing teams building behavioral automation without engineering support","E-commerce platforms automating post-purchase and abandoned cart campaigns","SaaS companies automating onboarding and engagement workflows"],"limitations":["Trigger latency depends on event processing pipeline — typically 1-5 minutes between event and action execution","Complex conditions with many AND/OR clauses may be difficult for Claude to reason about without visual representation","No built-in rate limiting — rapid-fire events may trigger duplicate campaigns (requires deduplication logic)","Debugging failed triggers requires access to event logs — limited visibility in MCP interface"],"requires":["Event source (e.g., Shopify webhook, custom API, CRM event stream)","Workflow engine with trigger evaluation logic","Campaign definitions for each trigger action"],"input_types":["event type (string, e.g., 'contact.signup', 'order.completed')","trigger conditions (JSON object with AND/OR logic)","action type (enum: send_email, send_sms, send_push, update_contact)","action parameters (campaign ID, delay, etc.)"],"output_types":["trigger ID (string)","trigger status (enum: active, paused, error)","execution count (integer)","last execution timestamp","error details (if failed)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-bolide-aimcp__cap_7","uri":"capability://data.processing.analysis.contact.data.import.and.synchronization","name":"contact data import and synchronization","description":"Provides MCP tools for importing contacts from external sources (CSV, API, CRM) and syncing contact data with upstream systems. Implements field mapping logic to translate external data schemas to internal contact model. Handles deduplication, validation, and conflict resolution (e.g., which system wins if email exists in both sources). Supports incremental syncs and batch imports with progress tracking.","intents":["Import contact lists from CSV or external CRM without manual data entry","Ask Claude to map fields from external data sources to contact attributes","Sync contact updates bidirectionally with upstream systems"],"best_for":["Teams migrating from legacy email platforms to Bolide AI","Multi-system environments needing contact data synchronization","High-volume contact imports (1000+ contacts) requiring batch processing"],"limitations":["Field mapping requires manual configuration — Claude can suggest mappings but cannot auto-detect schema mismatches","Large imports (>100k contacts) may take hours — no real-time progress updates in MCP interface","Deduplication is fuzzy-match only — exact email matches are reliable, but name-based deduplication may have false positives","No rollback capability — failed imports may require manual cleanup"],"requires":["Contact data source (CSV file, API endpoint, or CRM connection)","Field mapping configuration (source field → contact attribute)","Deduplication strategy (email, phone, or custom logic)"],"input_types":["import source (enum: csv, api, crm)","file path or API endpoint (string)","field mapping (JSON object: {source_field: contact_attribute})","deduplication strategy (enum: email, phone, custom)"],"output_types":["import ID (string)","status (enum: queued, in_progress, completed, failed)","contacts imported (integer)","contacts skipped (integer)","error details (array of {row, error_message})"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":27,"verified":false,"data_access_risk":"high","permissions":["Node.js 16+","MCP-compatible client (Claude Desktop, or custom MCP client implementation)","@modelcontextprotocol/sdk package","Bolide AI account or connected email service provider credentials","MCP client with tool-calling support","Valid email sender configuration in upstream service","Contact database with indexed fields (email, created_at, engagement_score, etc.)","Bolide AI or connected CRM with query API","MCP client with structured tool parameter support","Twilio account (SMS) or Firebase Cloud Messaging (push notifications)"],"failure_modes":["Requires MCP client support — not compatible with non-MCP LLM applications","Protocol overhead adds ~50-100ms per tool invocation for serialization/deserialization","No built-in authentication — relies on client-side access control","Campaign complexity limited by LLM context window — large recipient lists or complex segmentation may require pre-staging","No real-time campaign editing — changes require creating new campaign versions","Dependent on underlying email service provider availability and rate limits","Query performance depends on underlying database indexing — complex multi-attribute filters may timeout on large datasets (>1M contacts)","No real-time audience updates — segments reflect data as of last sync","Limited to pre-defined contact attributes — custom fields require schema updates","SMS character limits (160 chars standard, 153 with encoding) constrain message length — Claude may need to iteratively shorten content","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.26,"ecosystem":0.45,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:45.239Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-bolide-aimcp","compare_url":"https://unfragile.ai/compare?artifact=npm-bolide-aimcp"}},"signature":"Jy8cELtbCMpfJdXeHH+9xJKYtu9SApFuohphbsKuuYrctCKDb6hSjoTqVbUttiTIzfw2jKfJMfnhX7Gm0CbRCw==","signedAt":"2026-06-21T10:45:54.065Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-bolide-aimcp","artifact":"https://unfragile.ai/npm-bolide-aimcp","verify":"https://unfragile.ai/api/v1/verify?slug=npm-bolide-aimcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}