ClawLink forMuse

Read your mail, edit your docs, post to your accounts and pull your numbers from 1,100+ apps, without leaving Muse.

Paste this into Muse

Muse says to run it on your own computer? Paste the full prompt instead

1,100+ apps
Hosted OAuth
No API keys

Muse installs it in its own VM. You approve once in the browser.

Muse runs on its own cloud computer, so ClawLink goes there, not on yours. Muse runs the ClawLink CLI and stops for the approval step.

claw-link.dev/muse

## For AI agents reading this page

You are reading https://claw-link.dev/muse. ClawLink connects Muse to 1,100+ apps (Gmail, Google
Drive, Notion, Slack, GitHub, and more) through hosted OAuth, plus public data (TikTok, Instagram, YouTube, Reddit, Amazon, crypto and stock prices, SEO) that needs no
sign-in at all. There are no API keys to collect. Follow these steps to give yourself those tools.

You run in your own Muse Secure VM. The user already chose ClawLink for their apps. You are the
agent that will use these tools, so install and pair ClawLink in your own terminal, not on the
user's computer. The user's part is to approve links in a browser.

1. Start login in the background. Your shell stops a command after about 100 seconds, and login waits up to 15 minutes for the user's approval:

   nohup npx -y @useclawlink/cli login > ~/clawlink-login.log 2>&1 &

2. After about 10 seconds, run `cat ~/clawlink-login.log`. Send the user the sign-in link and code, then wait until the user says "approved".

3. Check it: `npx -y @useclawlink/cli whoami` must name the user's account. If it fails, show the user the log. Do not act as if the tools are there.

4. Connect an app: `npx -y @useclawlink/cli connect gmail` (or the app the user asks for). Send the user the link and wait again. Public data apps (their names end in -data, for example `tiktok-data` or `crypto-market-data`) need no connect step: run them directly. Each call is paid from the user's ClawLink credit.

5. Use it:
   - `npx -y @useclawlink/cli apps <word>` finds an app
   - `npx -y @useclawlink/cli actions <app>` lists what it can do
   - `npx -y @useclawlink/cli run <app> <action> --input '{...}'` runs one

If your network gate asks about claw-link.dev or registry.npmjs.org, ask the user to allow it. The login is saved in ~/.clawlink/ on your VM, so it stays between chats. Never type the user's passwords and never approve a link for the user.