LetKite (dev)

com.letkitePublished by letkite.comOfficial publisherv1.7.0-rc.2Updated Oct 24, 2026

Run commands and manage files on your own machines. Needs a LetKite account; OAuth sign-in.

VerifiedStreamable HTTPWeb executableFiles & StorageDeveloper Tools

Overview

AI-generated overview

A remote MCP server that lets an assistant run commands and manage files on your own machines, with OAuth sign-in to a LetKite account.

What you can do
Run commands on your own machines through the assistant connection. Manage files on those machines, as described in the registry entry. Connect over a remote streamable HTTP endpoint rather than a local package.
When to use it
Useful when you want an assistant to execute commands or handle files on machines you control, without installing a local package, and you are comfortable signing in with a LetKite account.
Requirements
A remote endpoint at mcp.dev.letkite.com over streamable HTTP. A LetKite account with OAuth sign-in is required. No environment variables or headers are declared.
Before you install
The server can run commands and manage files on your own machines, so actions may change or delete data; scope access carefully. Sign-in goes through OAuth to a LetKite account, and the service is hosted by a third party, so command and file activity passes through it.

Installation

In SourceWeft

  1. Open LetKite (dev) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.letkite%2Fletkite-dev/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "letkite-dev": {
      "type": "http",
      "url": "https://mcp.dev.letkite.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.7.0-rc.2LatestOct 24, 2026
  2. v1.7.0-rc.1Oct 23, 2026
  3. v1.4.0-rc.6Oct 19, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Letkite integrations

LetKite

com.letkiteOfficial publisher

LetKite is a hosted MCP endpoint that lets AI assistants on your account run commands and manage files on your own machines, including routers and the devices…

Streamable HTTPWeb executableAuth
Cloud & InfrastructureCredential requiredNov 5, 2026