Connect the Apify MCP server to Bolt, and Bolt's agent runs Actors while it builds, so your app launches with real places, products, and posts instead of placeholder data.
Bolt turns a chat into a working website or app, with hosting and databases built in. Its agent can research the web, but pulling complete, structured data from sites like Google Maps, Instagram, or Amazon takes a dedicated scraper. With Apify, the agent searches Apify Store, picks an Actor, runs it, and writes the results into your project.
You connect once with your Apify account, and there's no server to host.
- Find the right Actor. Describe the data in plain language, and the agent searches Apify Store for a matching Actor. Or name one in the prompt.
- Run Actors from the project chat. The agent starts the run and waits for it to finish, or checks back later on longer runs.
- Build the results into the app. The agent reads the dataset and saves the rows to the project (in a Bolt database, for example), so the published app loads them without calling Apify on every visit.
- Keep the data fresh. Ask the agent to re-run the Actor, or have it add a server function that runs the Actor on a schedule, using an Apify API token saved as a Bolt secret.
Niche directories. Find San Francisco coworking spaces with Google Maps Scraper and build a searchable directory with ratings, opening hours, phone numbers, and a map.
Job boards. Pull current postings for a role and location with Linkedin Jobs Scraper and let visitors filter by company and date.
Price comparison and catalogs. Collect product names, prices, and images from a set of stores with E-commerce Scraping Tool , and build a catalog with filters and detail pages.
Social and creator dashboards. Load a creator's latest posts with Instagram Scraper , then chart likes and comments per post.
Research and knowledge sites. Crawl a documentation site with Website Content Crawler or find sources on a topic with Google Search Results , then build a searchable knowledge base on top.
- Open connector settings. On the Bolt homepage, click the plus icon in the chatbox, then Connectors and Manage connectors.
- Add Apify as a custom MCP server. Click Custom MCP server, name it Apify, enter
https://mcp.apify.com, set Transport type to HTTP and Authentication to MCP OAuth, then click Connect. - Sign in to Apify. Pick your Apify account and allow access. Bolt marks the connector Connected.
- Turn it on and describe the app. In your project, switch on the Apify connector, then describe the app and the data it needs.
Actor runs bill against your Apify plan, and every run appears in Apify Console with its cost.
- Real data at build time - the agent stores Actor results in your Bolt database, and the published app reads from there
- OAuth sign-in - Bolt connects to your Apify account, with no API token to paste into the chat
- Tool-level control - turn off any Apify tool you don't want Bolt to use
- Hosting included - the app, its database, and its domain live in Bolt
Readme ends here. No "available triggers and actions" section: Bolt doesn't expose triggers.
