Other · Remote MCP server
Otakit
Inspect, upload, release, monitor, and revert OtaKit Capacitor OTA updates.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.OtaKit/otakit- Version
- 1.9.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- OtaKit (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/OtaKit) · how
- Repository
- github.com/OtaKit/otakit
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://console.otakit.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @otakit/cli | 1.9.0 | stdio |
How to connect Otakit
Otakit is a remote MCP server: there is nothing to install. Its endpoint is https://console.otakit.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @otakit/cli version 1.9.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @otakit/cli@1.9.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"otakit": {
"command": "npx",
"args": [
"-y",
"@otakit/cli@1.9.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Osrm MCPDriving, cycling, and walking routes and nearest road lookups via OSRM. No key required. | Local · stdio |
| Oss AutopilotOpen source contribution manager with PR tracking, issue discovery, and CI diagnosis. | Local · stdio |
| ossfindSafety-ranked open-source component discovery for agents across six package ecosystems. | Local · stdio |
| OT AIopsGoverned OT tap (57 tools): OPC-UA/Modbus/S7/MC/MTConnect/MQTT/EtherNet-IP/EtherCAT. | Local · stdio |
| Otp MCPGenerate and verify time based one time passwords locally. No network and no key. | Local · stdio |
| Otp MCP ServerPublic MCP for OTP (orgtp.com). Query cross-org best practices, learnings, publishers, patterns. | Local · stdio |
| Otr ProtocolMerchant trust verification for AI agents. One call = trust score, badge, and purchase safety. | Local · stdio |
| OttasiaWhere to watch X in Y? 30 Asian and Middle Eastern streaming markets, via Claude. | Remote & Local · HTTP, stdioLive check: ✓ handshake |