Before getting started:
- Visit the quickstart guide to ensure you have Keyboard installed with the proper permissions
- Connect Keyboard to the third-party apps you want to give Claude access to (see here if you haven’t already)
Key execution requirements
- Sign in to Keyboard
-
Open Claude and ensure Keyboard is connected.
Tip: ask Claude if it is connected to Keyboard
- Keep the Keyboard desktop app open so you can approve the workflows as they come up
Executing tasks with Keyboard
You’re ready to get started! Go into Claude and start asking it to perform tasks in the various apps you connected.Initial prompt requirement
Important: When interacting with the system, always begin your prompt with the word ‘keyboard’. This signals the system that you want to use Keyboard not accidentally trigger another tool. Example:Approval app workflow
When prompted to execute a task Claude will create a GitHub codespace, ensure it’s connected to the necessary third-party apps and then write code to execute the task. By default, you will need to approve the code before Claude executes the code to undertake the task at hand. You will see a notification in the Keyboard desktop app to approve or deny the requestTip: Check the Keyboard desktop app if Claude seems to be stuck before executing a task. You may have to approve it before it gets executed.
Save and re-use scripts
Claude will write a new script for each task it is asked to execute. Keyboard has the functionality to save successful scripts so that Claude can recall them to save time when you need similar tasks in the future. To save a script after a task was successfully executed, ask Claude to save it for future use. You can give it any name you want. Example: If you successfully created a Google Slides presentation with Claude, you can tell Claude: “Save this script in Keyboard and call it ‘Create Google Slides’” To use a saved script: The next time you want to create a Google Slides presentation. For example, simply add “Keyboard use the Create Google Slides script” in your prompt. To see your saved scripts: Ask Claude “What scripts do I have saved in Keyboard?” or “Show me my saved Keyboard scripts”Best practices
- Always verify your WebSocket connection is stable
- Start prompts with ‘keyboard’ to ensure proper context
- Use the Claude Desktop client for integrated experiences
Troubleshooting
- If a connected app isn’t working you can always ask Keyboard to list what environment variables it has access to
- Verify WebSocket connection status by clicking into the Keyboard desktop app mcp-notification-app
- Validate GitHub PAT permissions