Before you connect

Sign in to Citera and open Settings → API & MCP → MCP. Select Connect another assistant. Choose your client, or Other client when it is not listed, and copy the server URL. API and MCP access are open to all Citera accounts.

Open Citera API & MCP settings

The current server URL is https://mcp.citeralabs.ai/mcp. Browser sign-in lets you select the brands your assistant may read without creating an API key. The connection is read-only; it does not grant content generation or publishing access.

Add the custom chat connector

1. Open Lovable’s Connectors catalog, select Add custom and choose MCP server.

2. Name the server Citera. Keep Direct connection unless your organization requires another supported route.

3. Enter https://mcp.citeralabs.ai/mcp as the Server URL and choose OAuth authentication.

4. Select Add & authorize, sign in to Citera and select the brands Lovable may read.

5. Use Citera in your project chat or Chats and send the verification prompt.

Optional manual-key connection

If you choose the manual-key route in Citera, Lovable also offers bearer-token or API-key authentication. Supply the MCP-enabled key in the credential field so requests use Authorization: Bearer. Do not put the key into chat, project source code or the URL.

Verify the connection

Enable Citera in your client and send this first request. Inspect the Citera tool result: it should list only brands you authorized. A written answer without a Citera tool call does not verify a connection.

Use the Citera MCP tools to list the brands I authorized. Show their names and IDs. Then ask which brand I want to review. Do not change, generate or publish anything.

Permissions, limits and troubleshooting

Lovable’s custom MCP servers are chat connections and are personal to the connected user. They do not become an integration inside your published app. A workspace administrator can disable custom MCP servers; if the option is unavailable, check with the administrator.

A brand with no completed scans may have little visibility data to report. If a brand is missing, check the account used for sign-in and the brands selected during consent. Reconnect when needed. You can revoke the connection under AI assistants in Citera’s MCP settings. API and MCP share the account’s applicable usage allowance.

Client menus, plan requirements and connection capabilities can evolve. These instructions describe configuration and a verification step; they do not guarantee that every client version or workspace policy allows the connection.

Try a complete workflow

Weekly AI visibility brief

White label client report

Find pages losing visibility

Client reference

Official Lovable documentation