Skip to content
Murf AI logo

Murf AI MCP server

Give your AI assistant 5 tools it can call in Murf AI, over one server URL.

Murf AI is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
5
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
September 2026

About the Murf AI MCP server

Connect Murf AI once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Murf AI and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Murf AI tools your AI can run

Once connected, your assistant can call any of these Murf AI actions by asking in plain language.

  • List Voices

    Get the list of available voices for text-to-speech

    2 fields

  • Translate Text

    Translate one or more texts to the target language.

    2 fields

  • Voice Changer

    Convert an input audio file to a different voice using Murf Voice Changer.

    9 fields

  • Text to Speech

    Converts input text into speech using Murf AI.

    16 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Murf AI

Connect Murf AI once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Murf AI MCP, answered.

No. That is the point of it. One Activepieces server exposes Murf AI alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Murf AI in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 5 tools, including List Voices, Translate Text, Voice Changer, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.