Set up Lovable
Lovable’s AI app builder ($200M ARR, fastest-growing vibe-coding tool). Connect Agentcy as a personal connector so the Lovable Agent has live marketing context while it builds your app. Custom MCP servers require a paid Lovable plan.
- 01
Sign up at app.goagentcy.com and create an API key
- 02
In Lovable, go to Settings → Connectors → Personal connectors
- 03
Scroll to the custom server section and click New MCP server
- 04
Name: Agentcy
- 05
Server URL: https://data.goagentcy.com/mcp
- 06
Authentication: choose OAuth (Lovable’s default — works with Agentcy’s Dynamic Client Registration), or use Bearer token / API key with your agcy_... key
- 07
Click Add & authorize. Complete the auth flow when prompted.
- 08
Agentcy appears in your list of personal connectors. The Lovable Agent now has access to Agentcy tools when building in any project (until you turn it off in Settings).
path: Settings → Connectors → Personal connectors → New MCP server
# Remote MCP Server (OAuth)
# No config file needed — connect through your client's UI
Server URL: https://data.goagentcy.com/mcp
Authentication: OAuth
When prompted, enter your Agentcy API key (agcy_...)
Find your key at: app.goagentcy.com → Settings → API KeysIMPORTANT — Personal Connectors are USED DURING BUILD ONLY. Agentcy data enriches the Lovable Agent’s context AS IT BUILDS your app, but the Agentcy connection is NOT bundled into the deployed app. If you need Agentcy data in a deployed Lovable app, you’d build the API call into the app itself (using the Agentcy /api/query REST endpoint with your API key). Custom MCP servers require a PAID Lovable plan — prebuilt connectors are available on all plans but custom servers are paid only. Personal connectors are PER-USER (not shared across the workspace). On Business and Enterprise plans, workspace admins can enable/disable individual MCP servers organization-wide via Settings → Connectors → Personal connectors → Admin settings, or block all MCP server access via Settings → Privacy & security.
Stuck or want to verify these instructions yourself? These are the documentation sources we used. If something here doesn't match what you see in your client, the vendor may have updated their UI — and we'll get this page updated.