Runtime (Cloud MCP Connector)
简体中文 | English
Runtime is an MCP client that connects directly to the cloud MCP Runtime. It runs over STDIO so MCP-compatible front-ends (Claude Desktop, Chatbox, etc.) can immediately access cloud task management and knowledge-base capabilities without deploying databases or large models locally.
What You Can Do
Inside any client that speaks the MCP protocol you can invoke the following capabilities:
📋 Intelligent Task System
- Create tasks with steps and subtasks
- List tasks and inspect task status
- Delete tasks
- Keep task data decoupled from AI execution flows, ideal for automation and agent workflows
🧠 Cloud Knowledge Base
- Semantic vector search
- Power RAG, long-term memory, and document lookup workflows
- Structured entries with title / body / tags / categories
Highlights
✨ Zero Local Model Footprint
- Minimal onboarding: launch instantly via
npxoruvx. - Zero local resource usage: compute and storage live in the cloud, perfect for lightweight or mobile hardware.
- Client agnostic: works with Claude Desktop, Chatbox, Cherry Studio, and any MCP-compliant client.
- Mobile friendly: on mobile AI clients you only supply an HTTP endpoint plus key to unlock cloud features.
- Cross-platform consistency: whether you connect over STDIO on desktop or HTTP on mobile, you access the same cloud state.
🚀 Quick Start
Using uvx (Python environment)
{
"mcpServers": {
"runtime": {
"command": "uvx",
"args": ["runtime-mcp"],
"env": {
"AUTHORIZATION": "YOUR16CHARUPPERCASEKEY"
}
}
}
}
Mobile (HTTP access)
# Stream-capable HTTP (streamableHttp)
https://runtime.lincloud.cn/mcp
# KEY
AUTHORIZATION:YOUR16CHARUPPERCASEKEY
Environment Variables
| Variable | Required | Description |
|---|---|---|
AUTHORIZATION |
✅ Yes | 16-character user access key |
SERVER_URL |
Optional | Cloud MCP Runtime base URL |
RPC_PATH |
Optional | MCP RPC path, defaults to /mcp/rpc |
HTTP_TIMEOUT |
Optional | HTTP timeout in seconds, defaults to 30 |
🔑 User Access Key (mandatory)
You must supply a 16-character uppercase key that follows these rules:
- Allowed characters:
0–9,A–Z - Length must be exactly 16
- Example:
XAIMP0ETBUIXVP9X
What the key does
- Identifies your user space
- Determines which data domain you can access
- All knowledge-base, task, and state data are namespaced by this key and isolated from others
How to obtain or use a key
- Generate any 16-character string that satisfies the rules
- Keep using the same key consistently
- The system only checks length and character set; it does not validate the key’s origin or meaning
⚠️ Keep your key safe. Anyone with the key can access the corresponding data space.
Example generation (for reference)
Use OpenSSL to produce a 16-character uppercase alphanumeric key:
openssl rand -base64 12 | tr -dc 'A-Z0-9' | head -c 16
Metadata
Release files for runtime-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| runtime_mcp-0.1.2.tar.gz | 6.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| runtime_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.8 kB
Release files / runtime_mcp-0.1.2.tar.gz
| Download URL | runtime_mcp-0.1.2.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc3833bbd0cb5fc31476c71725c40cd1d801c68ee1a005a831f66f92283aea50
|
|
BLAKE2b-256 checksum How to use checksums |
4e87d0f7a3bfbb23dc727d9bcefa8ed1d9222b9016fb137e28d2fd231602393d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.16 {"installer":{"name":"uv","version":"0.9.16","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / runtime_mcp-0.1.2-py3-none-any.whl
| Download URL | runtime_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9adafb22ba8a929513360d1f457076fea7bddd11a7113afdce92099054523c43
|
|
BLAKE2b-256 checksum How to use checksums |
df735e21690633f2374270ddbaf06c93756e26b3c5072ee23558b67981666eb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.16 {"installer":{"name":"uv","version":"0.9.16","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for runtime-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.