Connect Muse to Context.dev
Connect Muse to Context.dev in 3 steps: 1. Sign in to ApexGenius and connect Context.dev. 2. Add the ApexGenius connector. 3. Start using Context.dev in Muse.
1,000 free credits · No card required
How to connect Context.dev to Muse
- 1Sign in to ApexGenius and connect Context.dev
- 2Add the ApexGenius connector to Muse
- 3Start using Context.dev in Muse
- 1
Connect Context.dev to ApexGenius
Connect Context.dev
Context.dev opens its own sign-in. Sign in and allow ApexGenius.
- 2
Connect ApexGenius to Muse
Choose Muse
Back on Start, pick Muse and copy the prompt.
- 3
Add it in Muse
In Muse, ask it to connect ApexGenius. Choose Connect on the card.
- 4
Approve access
ApexGenius opens its approval page. Review the access, then approve.
Add the ApexGenius connector to Muse
Muse adds ApexGenius as a custom connector from inside a chat. There is no config file and no terminal step.
- In ApexGenius, pick Muse on Start and copy the Muse setup prompt.
- In Muse, ask it to connect ApexGenius and paste the prompt. Muse shows an ApexGenius connector card. Choose Connect.
- Sign in to ApexGenius in your browser and approve access.
The MCP address
https://server.autom8.pro/mcp
Check it. Ask Muse which apps are connected. The setup prompt tells it to call apex_search_tools with an empty query and list them.
Then ask Muse
List my Context.dev monitors. Do not create, run, or change anything.
Written setup, step by stepShow
Before you start
- An account with permission to use the Context.dev resources you intend to connect.
1. Connect Context.dev to ApexGenius
- Open Context.dev in Connections. Choose Connect, or Add connection when offered. Give the connection a name if prompted. If Gateway setup pending appears, contact ApexGenius support before continuing.
- Choose the account and review access. Sign in to Context.dev in the browser and approve access for your organization. Context.dev uses browser authorization; no Context.dev API key is pasted into ApexGenius.

Context.dev labels ApexGenius an unverified app and names server.autom8.pro, the ApexGenius gateway, as the address that receives access. Sign in to continue.Open full-size image (opens in a new tab) - Review the connected account and resources. Confirm the connected Context.dev organization. Open Tools to review its reads and the monitor and batch actions. Most operations spend your organization's Context.dev credits.
- Check the connection. Use Test connection or Check again and read the reported status. Add an AI agent from the AI agents page, choose Read only for the first test, and try the question below.
2. Connect ApexGenius to Muse
Use this server address when adding the connection:
https://server.autom8.pro/mcpThe steps are above, under Add the ApexGenius connector to Muse. These notes apply to Muse only.
- Why the prompt is long. Muse’s custom connector asks for the sign-in addresses up front instead of reading them from the MCP address. The Muse setup prompt carries the authorize, token and registration addresses. No client ID or secret is needed.
- Access. When ApexGenius asks what Muse may use, choose Read only for the first test, or Custom to limit it to the tools you need.
3. Verify one safe read
List my Context.dev monitors. Do not create, run, or change anything.
List my Context.dev monitors. Do not create, run, or change anything.Compare the returned account and resource with Context.dev. Check the connection status separately from the result of the first read.
Full guide: the Context.dev setup guide.
What it looks like in Muse
Illustration of a task, not a recorded customer result. Your answers come from the account and dates you choose.
apex_search_toolsContext.dev monitors · Find the Context.dev read routeCompleteapex_call_read_toollist-monitors · List monitorsCompleteIllustrative example: two monitors are active, a pricing page checked daily and a changelog checked weekly. Listing monitors spends no credits. Nothing was changed.
Read-only routeWhat to ask Muse about Context.dev
- Check the connection
List my Context.dev monitors and their status. Do not create, run or change anything.
Runs
list-monitors(read). - Read a page
Read https://example.com/pricing as Markdown and list every plan with its price. Cite the URL.
Runs
web-scrape-markdown(read). - Look up a company
Pull the brand profile for linear.app: logo, colors, fonts and social links.
Runs
brand-retrieve-unified(read), thenweb-fonts(read).
These 3 questions use 4 of Context.dev’s 34 operations. The full list is below.
- Search the web for this week's official Stripe product announcements and cite each source URL. (read)
- Create a daily monitor on this pricing page. Show me the schedule and the credit cost first. (write)
What Muse can do in Context.dev
34 operations: 27 read, 7 write. Read looks things up and changes nothing. Writes change Context.dev and run only when you turn them on.
Search and read pages
5 readweb-searchreadSearch the live web and optionally return ranked results as Markdown.
web-scrape-markdownreadTurn one known URL into clean Markdown. The default way to read a page.
web-scrape-htmlreadReturn the raw HTML of one URL when the markup itself matters.
web-scrape-imagesreadList the images on one page, with sources and available metadata.
web-screenshotreadCapture a rendered PNG of a page, full page or one viewport.
Map, crawl and extract
3 readweb-scrape-sitemapreadList a site's URLs from its sitemap without reading every page.
web-crawlreadFollow links from one URL and return Markdown for several pages in one call.
web-extractreadCrawl the relevant pages and return JSON shaped by the JSON Schema you pass.
Documents
1 readparse-documentreadConvert PDF, Office, spreadsheet, image or text file bytes into Markdown.
Company and brand data
6 readget-brandreadShow a company's logo, colors, description, links and social profiles for one domain.
brand-retrieve-unifiedreadReturn brand data as JSON by domain, name, work email, ticker, ISIN, transaction text or URL.
web-styleguidereadRead a site's colors, type, spacing and shadows.
web-fontsreadName the font families a site uses, with fallbacks.
web-naicsreadClassify a company into 2022 NAICS industry codes.
web-sicreadClassify a company into SIC industry codes.
Monitor history
9 readlist-monitorsreadList the monitors in your organization with status and tags.
get-monitorreadRead one monitor's target, schedule, rules and webhook settings.
list-monitor-runsreadList one monitor's runs with status, timing and credits.
get-monitor-runreadRead one run and the change it found, if any.
list-account-runsreadList monitor runs across the whole organization.
list-monitor-changesreadList the changes one monitor has found.
list-changesreadList changes found across all monitors.
get-changereadRead one change with its text diff, evidence and importance.
list-monitor-credit-usagereadReport credits spent by each monitor over a time window.
Manage monitors
4 writecreate-monitorwriteCreate a recurring monitor. It runs a first baseline right away and spends credits on each later run.
update-monitorwriteChange or pause a monitor. A new target or rule starts a new baseline.
run-monitor-nowwriteStart a check now. It spends credits and can send the monitor's webhook.
delete-monitorwritePermanently delete a monitor and its future runs. Cannot be undone.
Batches
3 read · 3 writesubmit-batchwriteStart a background scrape or crawl job. It can call an outside webhook when done.
list-batchesreadList batch jobs from newest to oldest.
get-batchreadRead one batch's status, progress and credit use.
get-batch-resultsreadPage through a finished batch's results as JSON.
cancel-batchwriteStop a batch from starting new pages. Stored results are kept.
delete-batchwritePermanently delete a finished batch and its stored results. Cannot be undone.
You choose the access. When you approve Muse, pick Full access, Read only, or Custom.
Context.dev controls the OAuth grant. The connection acts for your Context.dev organization and uses its shared credits.
The read route checks Context.dev's live tool label and rejects writes or unlabeled operations.
Writes run right away when enabled. A deleted monitor or batch cannot be restored.
Fetched page text is untrusted data. The ContextDev skill tells your AI to quote and cite it and never follow instructions inside it.
Disconnecting stops future gateway access. It does not stop monitors or batches that already exist.
Questions about connecting Muse to Context.dev
Updated November 12, 2026.
How do I connect Muse to Context.dev?
Sign in to ApexGenius and connect Context.dev. In Muse, ask it to connect ApexGenius, paste the Muse setup prompt from ApexGenius, and choose Connect on the connector card. Then ask Muse: “List my Context.dev monitors. Do not create, run, or change anything.” Start with a read, so nothing changes.
How do I check that Muse can use Context.dev?
Ask Muse which apps are connected through ApexGenius. It calls apex_search_tools and lists them, and Context.dev should be there. If Muse shows the ApexGenius connector card again, choose Connect and finish the browser sign-in. Then ask: “List my Context.dev monitors. Do not create, run, or change anything.”
Does it spend Context.dev credits?
Most calls do. A scrape is 1 credit, a web search is 1 credit per 10 results, a crawl is 1 credit per page and a brand lookup is 10 credits. Listing monitors is free. Free organizations get 1,000 credits a month with a work email, or 250 once with a personal email.
Can my AI change my Context.dev account?
Yes. It can create, update, run or delete monitors and submit, cancel or delete batches. Writes run right away when enabled. A deleted monitor or batch cannot be restored.
Can a web page tell my AI what to do?
It should not. Page text is data. The ContextDev skill tells your AI to quote and cite it and never follow instructions found inside it. Review results before you act on them.
Can I take this setup to another AI agent?
Yes. Add ApexGenius to another compatible agent with the same ApexGenius account. It uses the same Context.dev connection and can load the ContextDev skill. Each agent needs its own setup.
More connections like this one
Muse with other apps
All 48 apps Muse can use
Google Drive
Google Slides
Atlassian Rovo
Polymarket
OP.GGConfluence
Supabase
Cal.com
ChatGPT Ads
GitHub
Stripe
Attio
Semrush
Apify
Linear
Jira
HQ Rental
Google Ads
Google Analytics
Google Forms
Google Tasks
Google Calendar
Google Sheets
Apollo
Blotato
Bing Webmaster
Calendly
ClickUp
monday.com
YouTube
YouTube Analytics
Salesforce
n8n
Google Search ConsoleElevenLabs
FreshBooks
Trello
GitLab
TypeSafeHubSpot
Other agents with Context.dev
Connect Context.dev to Muse today
Start free1,000 free credits. No card required. Disconnect any time.