
Dialfetch
com.dialfetchPublished by dialfetch.comOfficial publisherv0.1.0Updated Oct 24, 2026
Give your AI agent a phone: place calls, navigate IVRs, wait on hold, get structured answers.
Overview
Dialfetch lets an AI assistant place real phone calls to a given number with a plain-language goal and return structured answers, a transcript and a recording.
- What you can do
- Place goal-based outbound calls to a phone number, optionally with extraction fields, caller ID and duration limits, and cancel queued or in-progress calls. Check call status and outcome, wait for a call to finish, and read answers, notes, transcript and recording link. List recent calls and fetch a short-lived recording URL. List owned caller-ID numbers, per-call pricing and prepaid credit balance.
- When to use it
- Useful when an assistant must get information that only exists over the phone, such as store or pharmacy hours, flight or travel status, order or claim status, or license and insurance verification, including navigating IVR menus and waiting on hold.
- Requirements
- A remote Streamable HTTP endpoint; no local package. Authentication by API key sent as an Authorization Bearer header, or one-click OAuth for custom connectors. A Dialfetch account with prepaid credit and, for caller ID selection, owned phone numbers.
Installation
In SourceWeft
- Open Dialfetch in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.dialfetch%2Fdialfetch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"dialfetch": {
"type": "http",
"url": "https://app.dialfetch.com/api/mcp"
}
}
}README
Dialfetch MCP — give your AI agent a phone ☎️
Connect Dialfetch to Claude, Cursor, VS Code, Windsurf, Cline, the Claude Agent SDK — or any Model Context Protocol client — and your agent can place real phone calls. It navigates IVR phone trees, waits on hold, talks to humans (including after a transfer), and hands back structured answers, a transcript, and a recording.
Give it a phone number and a plain-language goal. Goal in, result out.
"Call the pharmacy at +1 305-555-0148 and tell me what time it closes today." →
{ answers: { closing_time: { value: "9:00 PM", quote: "We close at nine tonight." } } }
- 🔌 Endpoint:
https://app.dialfetch.com/api/mcp(Streamable HTTP + SSE) - 🔑 Auth: API key (
Authorization: Bearer df_…) or one-click OAuth for custom connectors - 📚 Full docs: https://app.dialfetch.com/docs/mcp
- 🌐 Industry-agnostic: retail & pharmacy hours, flight/travel status, order & claim status, license & insurance verification, government & utility lines
Quick connect
Claude Desktop
Add to claude_desktop_config.json (Settings → Developer → Edit config):
Claude.ai (web) — custom connector
Settings → Connectors → Add custom connector → paste https://app.dialfetch.com/api/mcp and
finish the one-click OAuth sign-in. No API key to paste.
Cursor
~/.cursor/mcp.json:
VS Code (Copilot agent mode)
.vscode/mcp.json:
More configs (Windsurf, Cline, Agent SDK) are in configs/.
Tools
Resource: dialfetch://calls/{id} · Prompts: check_store_hours, verify_license, get_order_status
How calls work
Calls are asynchronous (typically 2–10 minutes; longer with holds or transfers):
place_call({ phone, goal, extract })→{ call_id, status: "queued" }- Poll
get_call({ call_id })(or usewait_for_call) untilstatusiscompleted/failed/canceled - Read
answers,transcript,recording_url
Recipes
Safety
Calls disclose they are an AI by default. The agent will not read out or collect sensitive personal data (SSNs, passwords, full card numbers). Goal-screening, credit holds, and rate limits apply to every call and can't be bypassed by a client.
Links
- Product & sign-up: https://app.dialfetch.com
- MCP docs: https://app.dialfetch.com/docs/mcp
- REST API docs: https://app.dialfetch.com/docs
License
MIT — see LICENSE.
Source: README.md at commit 8b42e20
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% 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 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 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
- License10 pts