Skip to main content
Glama

Maqui Analytics

by io.github.luis-fuentes
OverviewDiscussionsAdmin

Server Details

Marketing analytics for local businesses — Instagram, ads, web traffic, SEO and reviews.

Ownership verified

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.0% over 38 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
Repository
somosmaqui/maqui-mcp
GitHub Stars
0

TDQS

A3.9/5.0

Scored across 19 tools

Disambiguation5/5

Each tool has a distinct domain prefix (ga4_, gads_, gsc_, ig_, meta_) and description that clearly differentiates it from similar tools. Descriptions include explicit warnings against confusion (e.g., gads_keywords vs gads_search_terms, ga4_pages vs gsc_pages). No ambiguity.

Naming Consistency4/5

Tools follow a consistent prefix_noun pattern within each domain (e.g., ga4_pages, gads_keywords). However, there is a mix of verb_noun (get_leads) and prefix_noun conventions, and summary tools use different prefixes (ga4_summary, gads_summary, ig_summary). Overall, naming is predictable and clear.

Tool Count5/5

19 tools cover multiple analytics domains (GA4, Google Ads, GSC, Instagram, Meta Ads, CRM, reviews, sales). Each domain has a summary and several detail tools, well-scoped for an analytics MCP server serving small businesses and restaurants. The count is appropriate for the breadth.

Completeness4/5

Core CRUD and lifecycle operations are provided for each domain: summary, detail exploration, and growth trends. Minor gaps exist (e.g., missing GA4 events, Google Ads ad groups), but essential queries (pages, sources, campaigns, keywords, search terms, posts, followers) are covered. No dead ends for basic analytics tasks.

Tool Schema Changelog

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

  1. 19 tool updates
    • First observedga4_pages
    • First observedga4_sources
    • First observedga4_summary
    • First observedgads_campaigns
    • First observedgads_keywords
    • First observedgads_search_terms
    • First observedgads_summary
    • First observedget_leads
    • First observedget_reviews
    • First observedget_sales
    • First observedgsc_pages
    • First observedgsc_queries
    • First observedgsc_summary
    • First observedig_followers_growth
    • First observedig_hashtags
    • First observedig_summary
    • First observedig_top_posts
    • First observedmeta_campaigns
    • First observedmeta_summary

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources