Name: Maqui Analytics
Author: somosmaqui

LABSCO SUMMARY

The cross-channel comparison is the query worth having.

Every one of these platforms has its own dashboard and its own export. What none of them can answer is "how many leads came from Meta Ads versus organic in January" — that is the question this exists for, and it is one sentence here. The per-client token model is the second thing to notice if you run an agency: ending a client relationship is a revoke, not a config migration, and the other clients keep working.

What it is

A hosted MCP server for Maqui, a marketing analytics platform aimed at local businesses and the agencies running them. It syncs daily from the channels a small business actually uses and makes them queryable in plain language, so a cross-channel question is one question rather than seven tabs.

What you get

Instagram reach, engagement rate, top posts, follower growth and hashtag performance
Google Ads spend, CTR, CPC, conversions, CPA and ROAS by campaign and keyword; Meta Ads spend, reach, leads, messages and purchases across Facebook and Instagram
Google Analytics 4 sessions, users, bounce rate, top pages and traffic sources, alongside Search Console clicks, impressions, rankings and top queries
Google Business and Facebook ratings, response rate and recent reviews — including the ability to ask for only the one-star ones from a period
CRM pipeline leads by status and source, and Fudo restaurant POS sales split by channel: dine-in, delivery, counter
Per-account isolation: every client account has its own dataset and its own token, with no cross-account access

Requirements

A Maqui account with the channels connected. Modern clients connect to https://app.somosmaqui.com/api/mcp over OAuth 2.0 with the full PKCE flow and handle login themselves. Claude Desktop and manual setups use a bearer token from the Maqui admin panel instead; tokens are issued per account, are valid for one year, and can be revoked from the dashboard with access cut off immediately and no effect on any other account's token. Agencies configure one entry per client, each with that client's token.

Setup effort

Paste a URL with a key — add the endpoint to your client

See installation options

USE CASES

01

Comparing channels against each other

Ask which source produced the leads or the sales in a period, across ads, organic and reviews, without exporting from each platform.

02

Finding the campaign that is actually paying

Ask for ROAS by campaign over a quarter rather than reading the Ads dashboard column by column.

03

Catching bad reviews quickly

Ask for the one-star reviews from the last thirty days, across Google Business and Facebook at once.

04

Reporting for several clients from one setup

Configure one server entry per client with that client's token, so the data stays isolated while the workflow stays the same.

05

Connecting sales back to marketing

Pull POS sales by channel alongside the ad and organic numbers for the same period, which is the join a restaurant actually cares about.

BEFORE YOU INSTALL

What to know first

Requires

A client that can reach a remote MCP server over HTTP

INSTALLATION

Connect your client

Add the endpoint to your client.

Server setup

Claude.ai, ChatGPT

ENDPOINT URL

https://app.somosmaqui.com/api/mcp

MCP Clients

Any MCP client — several accounts

ANY MCP CLIENT — SEVERAL ACCOUNTS · JSON

{
  "mcpServers": {
    "maqui-cliente-a": {
      "url": "https://app.somosmaqui.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN_CLIENT_A>"
      }
    },
    "maqui-cliente-b": {
      "url": "https://app.somosmaqui.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN_CLIENT_B>"
      }
    }
  }
}

Maqui Analytics