Maqui

Name: Maqui
Author: luis-fuentes

by luis-fuentescommunityv1.0.0

An MCP server for querying Maqui marketing analytics data through a conversational AI client. It exposes account-scoped metrics from Instagram, Google Ads, Meta Ads, Google Analytics 4, Search Console, reviews, CRM leads, and POS sales.

From the registry: Marketing analytics for local businesses — Instagram, ads, web traffic, SEO and reviews.

GitHub Repository

Install & configure

Prerequisites

optional
Obtain a Maqui API token for manual authentication
Generate a per-account API token from the Maqui dashboard/admin panel if your MCP client does not support OAuth 2.0 or if you want to configure authentication manually. Tokens are scoped to a single account and are valid for one year.
https://somosmaqui.com/
optional
Use an MCP client with OAuth 2.0 support
For clients that support OAuth 2.0, you can connect using the server URL only and complete login via the client's built-in OAuth PKCE flow.
https://app.somosmaqui.com/.well-known/oauth-authorization-server

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `maqui` MCP server into my current AI client (that's you).

Optional prerequisites:
- Obtain a Maqui API token for manual authentication — Generate a per-account API token from the Maqui dashboard/admin panel if your MCP client does not support OAuth 2.0 or if you want to configure authentication manually. Tokens are scoped to a single account and are valid for one year. (https://somosmaqui.com/)
- Use an MCP client with OAuth 2.0 support — For clients that support OAuth 2.0, you can connect using the server URL only and complete login via the client's built-in OAuth PKCE flow. (https://app.somosmaqui.com/.well-known/oauth-authorization-server)

Canonical MCP server config (HTTP transport):
- url: `https://app.somosmaqui.com/api/mcp`
- headers:
  - `Authorization`: `Bearer <your-api-token>`

Note: HTTP MCP server. Authentication supports either OAuth 2.0 with PKCE (recommended for modern clients) or a manual Bearer token header. For OAuth-capable clients, use the server URL and let the client handle login automatically; no static header is required. OAuth endpoints: discovery https://app.somosmaqui.com/.well-known/oauth-authorization-server, authorization https://app.somosmaqui.com/oauth/authorize, token https://app.somosmaqui.com/oauth/token.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: HTTP MCP server. Authentication supports either OAuth 2.0 with PKCE (recommended for modern clients) or a manual Bearer token header. For OAuth-capable clients, use the server URL and let the client handle login automatically; no static header is required. OAuth endpoints: discovery https://app.somosmaqui.com/.well-known/oauth-authorization-server, authorization https://app.somosmaqui.com/oauth/authorize, token https://app.somosmaqui.com/oauth/token.