Skip to main content

creolecentric-mcp

Stdio MCP proxy for the CreoleCentric remote MCP server.

CreoleCentric exposes its developer API as MCP tools at https://creolecentric.com/mcp/ over the Streamable HTTP transport. Most modern MCP clients (Claude Desktop, Claude Code, Cursor) can talk to that URL directly. This package is for the stdio-only clients — it spawns locally, speaks stdio MCP, and forwards every request to the remote server.

Install

pip install creolecentric-mcp

Use

export CREOLECENTRIC_API_KEY=cc_<keyid>_<secret>
creolecentric-mcp        # speaks MCP on stdio; quit with Ctrl-D

Generate an API key at https://creolecentric.com/api-keys.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on your platform:

{
  "mcpServers": {
    "creolecentric": {
      "command": "creolecentric-mcp",
      "env": {
        "CREOLECENTRIC_API_KEY": "cc_<keyid>_<secret>"
      }
    }
  }
}

Restart Claude Desktop. The 24 CreoleCentric tools (TTS, translation, dictionary lookup, STT, account/credits) appear in the tool picker.

Pointing at a different server

creolecentric-mcp --url https://staging.creolecentric.com/mcp/ --api-key cc_...
# or via env
CREOLECENTRIC_MCP_URL=https://staging.creolecentric.com/mcp/ creolecentric-mcp

What it does

Claude Desktop  ──stdio MCP──>  creolecentric-mcp  ──Streamable HTTP MCP──>  https://creolecentric.com/mcp/

Each tools/list and tools/call from the local stdio peer is forwarded to the remote server with your API key in the Authorization header. All auth, scope checks, rate-limits, and credit deduction happen on the server side — this binary is a thin transport adapter and stores nothing.

Why not just use the remote URL directly?

If your MCP client supports remote (HTTP / Streamable HTTP) servers, you should use https://creolecentric.com/mcp/ directly with an Authorization: Bearer cc_... header — no shim required. See the setup page.

This package exists for clients that haven't shipped remote-MCP support yet.

Metadata

Release files for creolecentric-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for creolecentric-mcp 0.1.0
File Size Uploaded Provenance Actions
creolecentric_mcp-0.1.0.tar.gz 4.5 kB With provenance Details for creolecentric_mcp-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for creolecentric-mcp 0.1.0
File Interpreter ABI Platform Actions
creolecentric_mcp-0.1.0-py3-none-any.whl Python 3 none any Details for creolecentric_mcp-0.1.0-py3-none-any.whl

Total release size: 9.9 kB

Release files / creolecentric_mcp-0.1.0.tar.gz

Download URL creolecentric_mcp-0.1.0.tar.gz
Size 4.5 kB
Tags Source
SHA-256 checksum
How to use checksums
3e2ade77581a892a93e89c160590eecc6c052c4863ec7a7c05341d6765493733
BLAKE2b-256 checksum
How to use checksums
2a623ea8c662dfdda3e072cb6d653bf580325b3a28488d2e936e3ee4da20f5aa
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 5, 2026.

Transparency log

Release files / creolecentric_mcp-0.1.0-py3-none-any.whl

Download URL creolecentric_mcp-0.1.0-py3-none-any.whl
Size 5.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
be734d3fd7f452571b623b7516d5d5104dc6aa0b21d3e0c2a4e1027aff0a8fad
BLAKE2b-256 checksum
How to use checksums
62b282c4603ac1b00d8def3053ca7d6f1439576d3bacbeb0c4474e156c3422dd
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 5, 2026.

Transparency log

Security for creolecentric-mcp 0.1.0

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.

Select from 2 files

Attestation for creolecentric_mcp-0.1.0.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 5, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page