Chans MCP
Copy the configuration for your app below. Replace YOUR_CHANS_API_KEY with a key
from Chans Developer settings → API keys.
Use npx with Node.js 22+, or uvx with uv and Python 3.12+. No global package installation is needed. Keep your API key private.
Claude Desktop and Cursor
- Claude Desktop: open Settings → Developer → Edit Config.
- Cursor: open
~/.cursor/mcp.jsonfor your personal configuration.
Paste one of these configurations, save, and restart the app. If mcpServers
already exists, add only the chans entry inside it.
With npx
{
"mcpServers": {
"chans": {
"command": "npx",
"args": ["-y", "@ai-chans/mcp"],
"env": {
"CHANS_API_KEY": "YOUR_CHANS_API_KEY"
}
}
}
}
With uvx
{
"mcpServers": {
"chans": {
"command": "uvx",
"args": ["chans-mcp"],
"env": {
"CHANS_API_KEY": "YOUR_CHANS_API_KEY"
}
}
}
}
Setup references: Claude Desktop and Cursor.
Claude Code
Run one command in your terminal:
npx:
claude mcp add --scope user --env CHANS_API_KEY=YOUR_CHANS_API_KEY --transport stdio chans -- npx -y @ai-chans/mcp
uvx:
claude mcp add --scope user --env CHANS_API_KEY=YOUR_CHANS_API_KEY --transport stdio chans -- uvx chans-mcp
Run claude mcp list to check the connection. Inside Claude Code, use /mcp to
inspect the server. Claude Code setup reference.
VS Code
Open the Command Palette and run MCP: Open User Configuration. Paste this
configuration, save, then use MCP: List Servers to start chans.
{
"servers": {
"chans": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@ai-chans/mcp"],
"env": {
"CHANS_API_KEY": "YOUR_CHANS_API_KEY"
}
}
}
}
For uvx, change "command" to "uvx" and "args" to ["chans-mcp"].
VS Code uses servers instead of mcpServers.
VS Code configuration reference.
Other MCP clients
Choose stdio as the transport and enter:
| Field | npx | uvx |
|---|---|---|
| Command | npx |
uvx |
| Arguments | -y, @ai-chans/mcp |
chans-mcp |
| Environment | CHANS_API_KEY=YOUR_CHANS_API_KEY |
CHANS_API_KEY=YOUR_CHANS_API_KEY |
On Windows, use npx.cmd if your app cannot launch npx. If a command cannot be
found, use its full executable path. Chans connects to https://api.chans.ai/mcp/;
your API key's scopes determine which tools are available.
Metadata
Release files for chans-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 |
|---|---|---|---|---|
| chans_mcp-0.1.1.tar.gz | 50.4 kB | With provenance | Details for chans_mcp-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chans_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for chans_mcp-0.1.1-py3-none-any.whl |
Total release size: 59.1 kB
Release files / chans_mcp-0.1.1.tar.gz
| Download URL | chans_mcp-0.1.1.tar.gz |
|---|---|
| Size | 50.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd84692e1376052acf3673ceadee58bb11e3e87ef6960440a110c603557945db
|
|
BLAKE2b-256 checksum How to use checksums |
44f0ee294458bda25c02843512f674d9ca5d234264575bb665ae0ada341f8e79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logRelease files / chans_mcp-0.1.1-py3-none-any.whl
| Download URL | chans_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
30ce5041ae54e07c0fa8d39faf797bc4ab3eed380b05c8c67882551735a63dbf
|
|
BLAKE2b-256 checksum How to use checksums |
34e6ab61df009927d0a548f90453ea37379aa4049e413bb29bb74c04ab7e4c29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logSecurity for chans-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
Both files in this release have been uploaded with provenance metadata.
Attestation for chans_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 Nov 10, 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.