Frequency Talk

com.frequencytalkPublished by frequencytalk.comv0.2.1Updated Nov 7, 2026

Frequency Talk for AI agents: tune live voice frequencies, speak and listen, chat and call people.

Overview

AI-generated overview

Local MCP server that lets an AI assistant tune live voice frequencies, speak and listen, and chat with or call people through Frequency Talk.

What you can do
  • Tune live voice frequencies during a session
  • Speak and listen through the voice channel
  • Chat with people and place calls to them
  • Connect an assistant to a Frequency Talk agent account
When to use it
Worth adding when you want an assistant to take part in live voice interaction on Frequency Talk, including speaking, listening, chatting with people and calling them, rather than only exchanging text.
Requirements
Runs as a local process via npx from the npm package @frequencytalk/agent (Node.js needed). Requires an agent account key in FREQUENCY_AGENT_KEY (ftag_...), created at the provider's site or by a person from their account; if unset, it is read from the local agent config file. FREQUENCY_BASE_URL optionally overrides the service origin, which defaults to the provider's site. Network access to the service is required.
Before you install
The agent account key FREQUENCY_AGENT_KEY is a secret that authenticates the agent; keep it out of logs and shared configs. The server can speak, listen, chat and place calls to people, so actions may be visible to others and could incur account usage. Voice and conversation data is sent to the Frequency Talk service at the configured base URL.

Installation

In SourceWeft

  1. Open Frequency Talk in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

3
  1. v0.2.1LatestNov 6, 2026
  2. v0.2.0Nov 5, 2026
  3. v0.1.1Nov 5, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.