nano-easm-mcp
Stdio <-> HTTPS bridge for the Nano EASM MCP server.
Lets MCP clients (Claude Desktop, Cursor, VS Code) that speak stdio
connect to the hosted MCP endpoint at mcp.nanoeasm.com.
Install
pip install nano-easm-mcp
Configure
- Sign in at https://nanoeasm.com and go to Settings -> API Keys -> MCP keys.
- Click Generate Key, copy the
mcp_sk_...value (shown only once). - Wire your MCP client.
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or
%APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"nano-easm": {
"command": "nano-easm-mcp",
"args": ["--url", "https://mcp.nanoeasm.com",
"--key", "mcp_sk_..."]
}
}
}
Env vars (alternative)
export NANO_EASM_MCP_URL=https://mcp.nanoeasm.com
export NANO_EASM_MCP_KEY=mcp_sk_...
nano-easm-mcp
What this package is (and isn't)
This package is a transport shim. It contains no business logic. Every
JSON-RPC frame received on stdin is forwarded to the configured hosted
endpoint with Authorization: Bearer <your-key>, and the response is
written back to stdout.
If your MCP client supports MCP over HTTP directly, you can point it at
https://mcp.nanoeasm.com without this bridge.
License
MIT.
Metadata
Release files for nano-easm-mcp 0.1.1
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 | Actions |
|---|---|---|---|---|
| nano_easm_mcp-0.1.1.tar.gz | 3.9 kB | With provenance | Details for nano_easm_mcp-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nano_easm_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for nano_easm_mcp-0.1.1-py3-none-any.whl |
Total release size: 8.2 kB
Release files / nano_easm_mcp-0.1.1.tar.gz
| Download URL | nano_easm_mcp-0.1.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a0f6ac280a35432d98395b5819a1bd58634a96a77ce5d2f8fadb3304fc5d7a98
|
|
BLAKE2b-256 checksum How to use checksums |
5b6203af35dcfcdaed0bddb15c4da7d0164fe0f5456e120f3be71f3e5d033f43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 20, 2026.
Transparency logRelease files / nano_easm_mcp-0.1.1-py3-none-any.whl
| Download URL | nano_easm_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
983878a7188480a68d5ad98fce3095c8b3f5b63ed9c7f9412bbf50288a8eec04
|
|
BLAKE2b-256 checksum How to use checksums |
5057010b4f5ec6aee6ba452122b071fabfb853865173dbb236d6ba30eb7ddfb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 20, 2026.
Transparency logSecurity for nano-easm-mcp 0.1.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for nano_easm_mcp-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 20, 2026.
Transparency logA 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.