Chans MCP
Connect your MCP client to Chans. Get an API key from Chans Developer settings → API keys.
Connect directly over HTTP (recommended)
No package installation is needed. Use https://api.chans.ai/mcp/ and send your
API key in the Authorization header.
Cursor
Open ~/.cursor/mcp.json, paste the configuration below, and replace the API key.
If mcpServers already exists, add only the chans entry inside it.
{
"mcpServers": {
"chans": {
"url": "https://api.chans.ai/mcp/",
"headers": {
"Authorization": "Bearer YOUR_CHANS_API_KEY"
}
}
}
}
Claude Code
claude mcp add --scope user --transport http chans https://api.chans.ai/mcp/ --header "Authorization: Bearer YOUR_CHANS_API_KEY"
Run claude mcp list to check the connection, or /mcp inside Claude Code.
For JSON configuration in .mcp.json, use the Cursor example above and add
"type": "http" to the chans entry.
Claude Code setup reference.
VS Code
Run MCP: Open User Configuration from the Command Palette and paste:
{
"servers": {
"chans": {
"type": "http",
"url": "https://api.chans.ai/mcp/",
"headers": {
"Authorization": "Bearer YOUR_CHANS_API_KEY"
}
}
}
}
Save, then use MCP: List Servers to start chans.
VS Code setup reference.
Dev and custom headers
For Cursor, use this configuration. For Claude Code, add "type": "http" inside
chans-dev. For VS Code, also change mcpServers to servers.
{
"mcpServers": {
"chans-dev": {
"url": "https://dev-api.chans.ai/mcp/",
"headers": {
"Authorization": "Bearer YOUR_DEV_CHANS_API_KEY",
"CF-Access-Client-Id": "YOUR_CF_CLIENT_ID",
"CF-Access-Client-Secret": "YOUR_CF_CLIENT_SECRET",
"X-Custom-Header": "YOUR_VALUE"
}
}
}
}
Add any application headers your endpoint needs. Cloudflare's header names use hyphens as shown above; your Access policy must allow the service token. Direct connections use your MCP client's header handling. Cloudflare service-token setup.
Use npx or uvx (stdio)
Use the launcher when your client requires a local command, including the Claude Desktop Settings → Developer → Edit Config setup. You need Node.js 22+ for npx, or uv and Python 3.12+ for uvx. No global package installation is needed.
Paste one configuration below, replace the API key, save, and restart your client.
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"
}
}
}
}
Claude Desktop setup reference.
Custom headers with stdio
Use --header "Name: value" for each header. With 0.1.4+, this configuration
needs no environment variables:
{
"mcpServers": {
"chans-dev": {
"command": "npx",
"args": [
"-y", "@ai-chans/mcp",
"--url", "https://dev-api.chans.ai/mcp/",
"--header", "Authorization: Bearer YOUR_DEV_CHANS_API_KEY",
"--header", "CF-Access-Client-Id: YOUR_CF_CLIENT_ID",
"--header", "CF-Access-Client-Secret: YOUR_CF_CLIENT_SECRET",
"--header", "X-Custom-Header: YOUR_VALUE"
]
}
}
}
For uvx, use "command": "uvx" and replace the first two arguments with
"chans-mcp". The same flags work with doctor. --url overrides
CHANS_MCP_URL; it defaults to production when neither is set.
A stdio client does not forward a top-level headers field to its child process.
Use the arguments above. CHANS_API_KEY remains supported instead of an explicit
Authorization header; do not configure both. The Cloudflare environment variables
from 0.1.3 remain supported for existing configurations.
Headers are checked for valid HTTP names and printable ASCII values. Control characters (including CR/LF), duplicate names ignoring case, and HTTP/MCP transport header overrides are rejected. The limit is 64 headers and 16 KiB in total. Credentials are not printed or forwarded across origins. Header values are not HTML-escaped or otherwise rewritten; validation protects HTTP framing.
Other stdio clients
Choose stdio 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.
Both connection methods use the tools exposed by Chans Core. Your API key's scopes determine which tools are available. Keep credentials out of shared configuration files.
Metadata
Release files for chans-mcp 0.1.5
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.5.tar.gz | 52.3 kB | With provenance | Details for chans_mcp-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chans_mcp-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for chans_mcp-0.1.5-py3-none-any.whl |
Total release size: 63.4 kB
Release files / chans_mcp-0.1.5.tar.gz
| Download URL | chans_mcp-0.1.5.tar.gz |
|---|---|
| Size | 52.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6f6d48c97e95faa7ce4f0fc78c5855f7869073465460c0e1db087fefb706d666
|
|
BLAKE2b-256 checksum How to use checksums |
0ae6b1be07b442495ac82413a140b304ce33bd0316a2b27804964bf5751e05e6
|
| 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.5-py3-none-any.whl
| Download URL | chans_mcp-0.1.5-py3-none-any.whl |
|---|---|
| Size | 11.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84a1458794b931180063e2ac29497755b7cfa775bcd11557cc3c5cc5f204b312
|
|
BLAKE2b-256 checksum How to use checksums |
2d9646104ed54945c3b52be5d0f2572680d9ff10fa8176de758f823913aeca14
|
| 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.5
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.5.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.