Skip to main content
Glama

Server Details

MCP server for customer-io

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.1% over 22 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-customer-io
GitHub Stars
0
Server Listing
mcp-customer-io

TDQS

A3.5/5.0

Scored across 40 tools

Disambiguation2/5

Many tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve querying/discovery, and there are six polymarket edge/fill/arbitrage tools that heavily overlap. An agent will struggle to pick the right one without reading long descriptions.

Naming Consistency3/5

Most tools use snake_case with some consistent prefixes (cio_, polymarket_, pipeworx_), but verb patterns vary widely (ask_, list_, get_, scan_, validate_, entity_profile, company_facts). The mix of verb-first and noun-phrase names creates a somewhat inconsistent feel, though not chaotic.

Tool Count2/5

40 tools is a heavy surface for a server that mixes Customer.io operations, data lookup, prediction-market analysis, and memory. Many are meta-tools that could be consolidated (e.g., multiple ask_pipeworx variants, multiple polymarket edge detectors). The count exceeds typical well-scoped servers and adds selection overhead.

Completeness3/5

The server covers a wide domain: Customer.io metrics (campaigns, messages, segments), structured data lookup, prediction markets, memory, and utility tools. However, there are gaps—no create/update/delete operations for Customer.io campaigns, no direct action on most data sources beyond querying, and some tools (like generate_llms_txt) feel peripheral. The breadth is impressive but incomplete in lifecycle operations.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 40 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcio_campaign_metrics
    • First observedcio_list_campaigns
    • First observedcio_list_messages
    • First observedcio_list_segments
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.