cochl

The Cochl MCP Server exposes an integration point between Cochl Sense results and a Model Context Protocol (MCP) based workflow. It runs the Cochl MCP server executable and provides an MCP-compatible endpoint that can be consumed by compatible clients or LLM-based tooling. This enables easy analysis by integrating Cochl Sense results with an LLM, so you can query and reason about audio analyses within your larger context pipelines.

The included tooling focuses on Cochl Sense capabilities, notably the analyze_audio command which accepts an absolute file path to an audio file (mp3, ogg, wav). By starting the server with the configured environment (base URL for Cochl Sense results and your project key), you can send MCP requests to retrieve structured results, context blocks, and insights derived from the audio analysis, which can then be fed into your prompts or chained with other MCP-enabled tools. Ensure the server is reachable by your MCP consumer and that the COCHL_SENSE_BASE_URL and COCHL_SENSE_PROJECT_KEY are correctly configured in the environment for proper authentication and project scoping.

Prerequisites:

• Go (Golang) toolchain installed (Go 1.18+ recommended)
• Git installed if building from source
• Optional: access to the internet to download dependencies

Option 1: Build from source

git clone https://github.com/cochlearai/cochl-mcp-server.git
cd cochl-mcp-server

go build -o cochl-mcp-server cmd/cochl-mcp-server/main.go

# Optionally install to PATH
# go install github.com/cochlearai/cochl-mcp-server/cmd/cochl-mcp-server@latest

• Place the executable file in your system's PATH so it can be found by your MCP clients.

Option 2: Download pre-built binary

• Visit Releases page: https://github.com/cochlearai/cochl-mcp-server/releases
• Download the appropriate version for your OS/arch
• Place the executable file in your system's PATH

Configuration (example):

• Create or update your MCP configuration to include the cochl server as shown in the mcp_config example.
• Ensure the environment variables COCHL_SENSE_BASE_URL and COCHL_SENSE_PROJECT_KEY are set, either in your shell or via your orchestration system, before starting the server.

export COCHL_SENSE_BASE_URL=https://api.cochl.ai
export COCHL_SENSE_PROJECT_KEY=<your project key>

Then start the server binary as needed by your setup (the exact startup command will depend on how you integrate it into your environment).

Tips and notes:

• The server relies on two environment variables: COCHL_SENSE_BASE_URL (base API endpoint for Cochl Sense) and COCHL_SENSE_PROJECT_KEY (authentication/identification for your project). Keep these secure and rotate keys as recommended.
• If you encounter connectivity issues, verify that the COCHL_SENSE_BASE_URL is reachable from the host where the MCP server runs and that any required network access (firewalls, proxies) is configured.
• When using with Claude Desktop or Cursor IDE, ensure your MCP configuration references the cochl server name and that the environment vars are injected in the runtime environment where the MCP client executes.
• The Tools section highlights Cochl Sense capabilities like analyze_audio. Ensure audio file paths supplied to analyze_audio are absolute paths and that the file types (mp3, ogg, wav) are supported by the Cochl Sense service.
• If you plan to run multiple MCP servers, keep unique server names under mcpServers to avoid naming conflicts and clearly document per-server environment requirements.