TagMango MCP gives AI coding agents (Cursor, Claude Code, Claude Desktop, Lovable) deep knowledge of every TagMango API endpoint, authentication flow, and integration pattern — so they can write correct integration code on the first try.
The TagMango MCP server is a Model Context Protocol server — a standard protocol that lets AI agents discover and query structured knowledge.
Instead of pasting API docs into every chat, you connect your AI tool once and it can browse all TagMango APIs, look up endpoint schemas, understand auth requirements, and get integration examples — all on demand.
Add to Cursor, Claude Code, or Claude Desktop. No re-configuration needed.
Every external and core-api endpoint with schemas, examples, and integration notes.
Registry is parsed from live OpenAPI specs and continuously enriched.
Choose your tool and follow the setup steps below.
Add to ~/.cursor/mcp.json (create if it doesn't exist):
{
"mcpServers": {
"tagmango-builders": {
"url": "https://mcp.tagmango.com/mcp"
}
}
}
Restart Cursor after saving. The tools will appear automatically in Cursor Agent.
Run this command once (requires the Claude Code CLI):
claude mcp add --scope user --transport http \ tagmango-builders https://mcp.tagmango.com/mcp
Or add manually to ~/.claude/settings.json:
{
"mcpServers": {
"tagmango-builders": {
"url": "https://mcp.tagmango.com/mcp"
}
}
}
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"tagmango-builders": {
"url": "https://mcp.tagmango.com/mcp"
}
}
}
Restart Claude Desktop after saving.
Lovable supports remote MCP servers via Connectors. No config file needed.
In your Lovable project, click Connectors in the left sidebar.
Use the search bar to find Custom MCP and select it.
Enter a name (e.g. tagmango-builders), paste the server URL below, set authentication to No Authentication, and click Add & Authorize.
https://mcp.tagmango.com/mcp
Once authorized, Lovable's AI agent will have full access to the TagMango API registry.
The MCP server exposes four tools. AI agents use these to discover and look up API information.
Returns all API modules with descriptions, keywords, and use-case examples. Always call this first to discover which module covers a feature.
Returns a summary list of all endpoints in a module — method, path, auth type, and context (frontend/backend).
Returns full details for 1–5 endpoint IDs: parameters, request/response schemas, integration notes, and usage examples.
Lets AI agents report missing endpoints, inaccurate schemas, or unclear docs — and submit a session summary after completing a task.
TagMango has two API surfaces, each with different auth.
Server-to-server. Uses a static API key as a Bearer token. Suitable for backend integrations where you control the server.
Authorization: Bearer <api-key> x-whitelabel-host: yourdomain.com
User-facing SSO flow. TagMango passes a refresh token to your app URL. Exchange it for a short-lived access token.
POST /get-access-token
{ "refreshToken": "..." }
→ { "accessToken": "..." }
Full auth guides are available as MCP resources — your AI agent can read them with
tagmango://guides/auth-external and
tagmango://guides/auth-core-api.