Skip to content
Back to search

keyboard-local

One MCP Server, All Your Apps, Privacy First

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/keyboard-dev--keyboard-local/badge.svg)](/listings/keyboard-dev--keyboard-local)

HTML

<a href="/listings/keyboard-dev--keyboard-local"><img src="/api/listings/keyboard-dev--keyboard-local/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 234 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. <a href="https://www.keyboard.dev/">
  3. <picture>
  4. <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/keyboard-dev/keyboard-local/main/images/kbwhite.png">
  5. <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/keyboard-dev/keyboard-local/main/images/blacktextkb.png">
  6. <img alt="Keyboard Logo" src="https://raw.githubusercontent.com/keyboard-dev/keyboard-local/main/images/blacktextkb.png" width="400">
  7. </picture>
  8. </a>
  9. ### Your AI Client can now actually DO things, not just talk about them
  10. *Connect any tool that has a REST API, CLI or SDK to your Claude, Cursor, VS Code, or any other AI Client that supports MCP (Model Context Protocol)*
  11. [![Docs](https://img.shields.io/badge/docs-keyboard.dev-blue)](https://docs.keyboard.dev/) [![License](https://img.shields.io/badge/license-Apache%202.0-green)](LICENSE) [![Discord](https://img.shields.io/badge/discord-join-7289da)](https://discord.gg/UxsRWtV6M2) [![Website](https://img.shields.io/badge/website-keyboard.dev-orange)](https://www.keyboard.dev/)
  12. </div>
  13. <img src="https://raw.githubusercontent.com/keyboard-dev/keyboard-local/main/Gif4readme.gif" width="1000">
  14. ## Before Keyboard ❌
  15. - **You:** "Send an email to my team about tomorrow's meeting"
  16. - **Claude:** "Here's how you would write that email..."
  17. - *You manually copy, paste, send*
  18. ## With Keyboard ✅
  19. - **You:** "Send an email to my team about tomorrow's meeting"
  20. - **Claude:** "I'll send that email for you" → *[You approve]* → **Email sent** ✓
  21. ## 🔥 What Can Your AI Client Actually Do Now?
  22. - **📧 Send emails** through Gmail
  23. - **📅 Schedule meetings** in Google Calendar
  24. - **📊 Create surveys** with Typeform
  25. - **🎫 Create tickets** in Linear, Jira, Asana, your task manager
  26. - **📝 Edit documents** in Google Drive, Notion, Confluence, your internal knowledgebase
  27. - **💬 Send messages** in Slack
  28. - **📈 Manage** your CRM
  29. - **🔗 Any API you connect** - Twitter, Stripe, GitHub, anything
  30. All running securely in YOUR GitHub with YOUR API keys.
  31. ## See It In Action (30 seconds)
  32. <div align="center">
  33. <a href="https://app.supademo.com/embed/cmd6bnb3t5xwac4kjx91usuv3">
  34. <img src="https://raw.githubusercontent.com/keyboard-dev/keyboard-local/main/images/demo-preview.png" alt="Interactive Demo" width="800">
  35. <br>
  36. <strong>🎬 Click for Interactive Demo</strong>
  37. </a>
  38. </div>
  39. ## Get Started (5 minutes)
  40. See [Quickstart](https://docs.keyboard.dev/getting-started/quickstart) to start using Keyboard in Claude Desktop.
  41. ## When Should I Use Keyboard?
  42. When you want your AI client (Claude, Cursor, ChatGPT, etc.) to actually execute tasks instead of just suggesting code.
  43. Connect your tools to your secure GitHub environment, ask Claude to do something, and Keyboard handles the execution with your approval. No need to install separate MCP servers for each app, or rely on a third party to maintain their plug ins - any API-enabled service can connect through Keyboard.
  44. ## The Secret: You Stay In Control
  45. Every action shows you the exact code BEFORE it runs:
  46. ```markdown
  47. // Claude wants to run this:
  48. await gmail.send({
  49. to: "team@company.com",
  50. subject: "Tomorrow's meeting",
  51. body: "Hi team, ..."
  52. })
  53. [Approve] [Reject] [Edit]
  54. ```
  55. Your data never leaves your GitHub. Keyboard can't see your API keys. Always secure, always private.
  56. ## Example Automations
  57. - "Check my calendar and email everyone in my next meeting"
  58. - "Find all unread customer emails and create support tickets"
  59. - "Post this update to Twitter and LinkedIn"
  60. - "Create a Typeform survey from this list of questions"
  61. - "Find that document about Q3 planning and summarize it"
  62. ## Key Features
  63. - **Connect Your Tools:** One MCP, all your tools. Provide Keyboard access to third party tools in your own GitHub environment.
  64. - **Private:** Keyboard doesn't have access to your API keys, it only has access to the GitHub Codespace.
  65. - **Secure Workflows:** Run code safely within your own controlled environment with human oriented approval workflows.
  66. - **Human Control:** You approve what code is executed, you also approve what data is sent is back to MCP clients like Claude.
  67. ## How Keyboard Works
  68. Keyboard creates a seamless bridge between AI conversations and actual code execution through a simple approval-based workflow.
  69. ### How it works in 3 steps:
  70. 1. **Ask your AI** to execute a task using your connected tools
  71. 2. **Review & approve** the explanation and generated code in the Keyboard desktop app
  72. 3. **Watch it execute** safely in your own GitHub Codespace
  73. ### Full Breakdown
  74. ```mermaid
  75. flowchart LR
  76. A[👤 User] -->|Chat| B[🤖 Claude Desktop]
  77. B -->|Generated Code| C[📋 Keyboard App<br/>Receives Script]
  78. C -->|Review & Approve| D[✅ User Decision]
  79. D -->|Approved| E[⚡ Executes in<br/>GitHub Codespace]
  80. E -->|Results| F[📊 Back to User]
  81. F -->|Continue| A
  82. D -->|Rejected| G[❌ Process Ends]
  83. G -.->|Try Again| A
  84. style A fill:#FFD700,stroke:#B8860B,stroke-width:3px,color:#000
  85. style B fill:#32CD32,stroke:#228B22,stroke-width:3px,color:#000
  86. style C fill:#4169E1,stroke:#191970,stroke-width:3px,color:#fff
  87. style D fill:#FF69B4,stroke:#C71585,stroke-width:3px,color:#000
  88. style E fill:#1E90FF,stroke:#0000CD,stroke-width:3px,color:#fff
  89. style F fill:#9370DB,stroke:#4B0082,stroke-width:3px,color:#fff
  90. style G fill:#FF4500,stroke:#8B0000,stroke-width:3px,color:#fff
  91. ```
  92. The process is straightforward:
  93. 1. **User Interaction**: You chat with Claude (or any MCP-compatible AI client) normally
  94. 2. **Code Generation**: Claude generates the code needed to accomplish your task in your connected apps
  95. 3. **User Approval**: Keyboard presents the generated code for your review and approval
  96. 4. **Secure Execution**: Once approved, the code runs safely in an isolated GitHub Codespace
  97. 5. **Results**: You get real results, not just code suggestions
  98. This architecture ensures you maintain full control while enabling your AI to actually execute tasks rather than just providing instructions.
  99. ## Documentation
  100. Full docs can be found at https://docs.keyboard.dev/ but see below for direct links to a few docs that will help you use Keyboard after you get set up:
  101. * [Learn how to connect your third party apps](https://docs.keyboard.dev/getting-started/thirdpartyapps)
  102. * [Tips for using Keyboard with Claude](https://docs.keyboard.dev/guides/claude)
  103. ## Run & Contribute to Keyboard
  104. If you want to run the whole codebase and contribute to both the MCP server and the desktop client see the instructions below.
  105. 1️⃣ Clone the monorepo (with submodules)
  106. ```bash
  107. git clone --recursive https://github.com/keyboard-dev/keyboard-local.git
  108. cd keyboard-local
  109. ```
  110. 2️⃣ Start Approver Client (Electron Desktop App)
  111. ```bash
  112. cd apps/approver-client
  113. git checkout main
  114. git pull origin main
  115. npm install && npm run dev
  116. ```
  117. 3️⃣ Start Keyboard MCP Server
  118. In a separate terminal:
  119. ```bash
  120. cd apps/keyboard-mcp
  121. git checkout main
  122. git pull origin main
  123. npm install && npm run build
  124. ```
  125. ## 🔥 Important: How to Contribute
  126. ✅ DO THIS:
  127. * Make changes in apps/approver-client/ or apps/keyboard-mcp/
  128. * Create branches and commits like normal
  129. * Submit PRs to the individual repos:
  130. Approver Client changes → https://github.com/keyboard-dev/approver-client
  131. Keyboard MCP changes → https://github.com/keyboard-dev/keyboard-mcp
  132. ❌ DON'T DO THIS:
  133. * Don't submit PRs to this monorepo (unless changing this README)
  134. * Don't worry about "updating submodules" - handled automatically
  135. That's It! Work like you normally would. This repo just saves you from cloning multiple repositories.
  136. ---
  137. ## ⚠️ Disclaimer
  138. Keyboard executes code in your GitHub Codspace environment. While we've designed it with security in mind, you should:
  139. - Review all code before approving execution
  140. - Only connect trusted applications
  141. - Understand that API calls may have real-world effects
  142. - Don't give Keyboard or by extension your GitHub codespace permissions that could in general ruin your life or career
  143. This software is provided "as is" without warranty of any kind, express or implied.
  144. ---
  145. **⭐ If Keyboard helps you work more securely with AI, please give us a star!**
  146. Join our [Discord](https://discord.gg/UxsRWtV6M2) if you have any questions. We'd love to hear from you.
  147. *Built with ❤️ by the Keyboard team*

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.