500 free credits · 1 credit per successful fetch · Open-source MCP server
Server URL
https://mcp.unblockingapi.com/mcpThe app never sees your API key. Disconnect it any time under Connected apps.
Lovable reads the live page instead of guessing its layout, copy or data from a description.
Integrating an API? Lovable reads the current reference, not an outdated memory of it.
OAuth with your UnblockingAPI account: no key pasted into chat, disconnect any time.
Lovable builds best from real material. Many of the pages you'd point it at - marketplaces, property portals, competitors' sites - block automated requests or only render in a browser. UnblockingAPI fetches them through rotating residential proxies and a real browser, and returns JSON where a template covers the site.
The connector is build-time context. For your app to fetch pages at runtime, it calls the REST API - see the FAQ below.
Paste the hosted URL and approve access. No key to copy, nothing to install.
UnblockingAPI, connection Direct connection, server URL https://mcp.unblockingapi.com/mcp.Same hosted URL, authenticated by your key in a header.
Use unblockingapi to get the Google results for "best espresso machine" as structured data, then summarise the top three.unblock_fetch hands back the full rendered page. For clean fields instead - a price, a title, a whole list - build a template visually in the editor: load the page, tap what you want, done. No CSS selectors to write by hand.
Save it and it's a reusable API endpoint - same account, same key, same as the built-in templates. Build the structure once, then call it from your app - or your AI agent - forever.
Try the editorNo account needed to try it · No credit card · More about the editor
Select one item. Similar items are detected automatically.
Website
Sony WH-1000XM5
$299.99
Bose QuietComfort
$249.00
Bang & Olufsen Beoplay
$1,714.99
Extracted JSON
Tap one item, get every item - as an array.
No - a custom MCP server is a chat connector: it gives Lovable live context while you build, it is personal to you, and it is never part of the published app. To fetch pages from the app itself, call the UnblockingAPI REST API from your backend (a Supabase edge function, for example) with your key stored as a secret. Ask Lovable to wire that up - it can read our docs through the connector.
Custom MCP servers are available on all Lovable plans. If the MCP server option is greyed out, a workspace admin has turned custom servers off.
Name the connector when it matters: "Using UnblockingAPI, read https://… and build a page with the same sections", or "Using UnblockingAPI, get the Google results for … and list the top competitors' pricing pages".
Not when you sign in. Lovable gets an access token for the hosted server, and the server uses your key on its behalf, so the key itself never leaves UnblockingAPI. You can disconnect any time under Connected apps. If you connect with an API key header instead, the key is stored in Lovable's own config.
The MCP server is free and open source. Fetches run on your UnblockingAPI account: every successful fetch costs 1 credit and failed ones are free. New accounts get 500 free credits with no credit card, and plans make credits cheaper at volume. Looking up templates is free.
Three, all read-only. unblock_fetch reads any URL through rotating residential proxies and a real browser, picking a plain fetch or a browser per site by itself. It returns the page as Markdown (HTML on request), or JSON with a template. find_templates checks whether a published template covers a site. get_build_guide gives Lovable the API reference and recipes when you build an app on the API. Details on the MCP server page.
The hosted server: nothing to install or update, and most apps sign in without a key. Run it locally with npx -y @unblockingapi/mcp if you prefer to keep the process on your machine - the tools and costs are the same.
One account, every assistant. Connect as many as you like, or see them all.