Livekit Murf
Official Murf AI Text-to-Speech integration for Livekit Agents - a framework for building voice and multimodal conversational AI applications.
Note: This integration is maintained by Murf AI. As the official provider of the TTS service, we are committed to actively maintaining and updating this integration.
Installation
pip install livekit-murf
Livekit Starter Project
from livekit.agents import JobContext, WorkerOptions, cli, JobProcess, get_job_context
from livekit.agents.voice import Agent, AgentSession
from livekit.plugins import murf, openai, silero, deepgram
class MyAgent(Agent):
def __init__(self) -> None:
super().__init__(
instructions="You are a voice agent build using Murf TTS",
stt=deepgram.STT(model="nova-3"),
llm=openai.LLM(model="gpt-4o"),
tts=murf.TTS(voice="en-US-matthew", style="Conversation"),
vad=get_job_context().proc.userdata["vad"],
)
async def on_enter(self):
await self.session.say("Hi, I am a voice agent powered by Murf, how can I help you?")
async def entrypoint(ctx: JobContext):
await ctx.connect()
ctx.log_context_fields = {
"room": ctx.room.name,
}
session = AgentSession()
await session.start(
agent=MyAgent(),
room=ctx.room
)
def prewarm(proc: JobProcess):
proc.userdata["vad"] = silero.VAD.load()
if __name__ == "__main__":
cli.run_app(WorkerOptions(entrypoint_fnc=entrypoint, prewarm_fnc=prewarm))
Pre-requisites
You'll need an API key from Murf AI. It can be set as an environment variable: MURF_API_KEY
Compatibility: Requires livekit-agents >= 1.2.18.
Metadata
Release files for livekit-murf 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 | |
|---|---|---|---|---|
| livekit_murf-0.1.1.tar.gz | 9.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| livekit_murf-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.4 kB
Release files / livekit_murf-0.1.1.tar.gz
| Download URL | livekit_murf-0.1.1.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a51efb57ebb1f686515ded57d296b11e369e345121768aca377da5a59ee3787
|
|
BLAKE2b-256 checksum How to use checksums |
3528bd8c701700d97015faa2179686f6b11c816097ca62605ae7d366a048db55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.27 {"installer":{"name":"uv","version":"0.9.27","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / livekit_murf-0.1.1-py3-none-any.whl
| Download URL | livekit_murf-0.1.1-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
392711d4955f0c40715e2d846c9d6c641d552136d4b247670571473c185761e8
|
|
BLAKE2b-256 checksum How to use checksums |
63a1be254ddd81245bafe378a66917d455c1c995246cddf087b0ba5b4bd639d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.27 {"installer":{"name":"uv","version":"0.9.27","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for livekit-murf 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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.