Can I use AssemblyAI as a CLI?

Yes. KosmoKrator exposes a AssemblyAI CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose AssemblyAI through MCP?

Yes. The KosmoKrator MCP gateway can expose selected AssemblyAI tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are AssemblyAI credentials stored?

AssemblyAI credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for AssemblyAI MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

AssemblyAI MCP Integration for LangChain

Connect AssemblyAI to LangChain through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

6 functions 4 read 2 write API key auth

Submit AssemblyAI feedback View package source

Connect AssemblyAI to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

AssemblyAI MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

{
  "mcpServers": {
    "kosmokrator-assemblyai": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=assemblyai",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=assemblyai --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only AssemblyAI instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

AssemblyAI Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the AssemblyAI integration catalog.

MCP tool	Source function	Type	Description
`integration__assemblyai__assemblyai_transcribe`	`assemblyai.assemblyai_transcribe`	Write	Submit an audio or video file URL for AI transcription. Supports speech-to-text, speaker diarization, summarization, sentiment analysis, and more. Returns a transcript ID to poll for results.
`integration__assemblyai__assemblyai_get_transcript`	`assemblyai.assemblyai_get_transcript`	Read	Retrieve a transcript by ID. Returns the transcription text, status (queued, processing, completed, error), confidence score, and any enabled AI features like speaker labels, chapters, or sentiment analysis.
`integration__assemblyai__assemblyai_list_transcripts`	`assemblyai.assemblyai_list_transcripts`	Read	List transcripts with optional filtering by status, date range, and pagination. Returns transcript IDs, statuses, and metadata.
`integration__assemblyai__assemblyai_upload`	`assemblyai.assemblyai_upload`	Write	Upload a local audio or video file to AssemblyAI. Returns an upload URL that can be passed to the transcribe tool as the audio_url parameter. Supports most common audio and video formats.
`integration__assemblyai__assemblyai_get_lemons`	`assemblyai.assemblyai_get_lemons`	Read	Retrieve lemons (billing credits and usage information) from your AssemblyAI account.
`integration__assemblyai__assemblyai_get_current_user`	`assemblyai.assemblyai_get_current_user`	Read	Get the authenticated user's profile, including email, subscription plan, and API usage details.

Related AssemblyAI Pages

AssemblyAI CLIUse direct JSON commands instead of MCP discovery. AssemblyAI MCPFull gateway reference and MCP tool names. KosmoKrator for LangChainClient-level gateway setup.