01
Connect the approved remote MCP server
Use the URL and credential shown on the Developers page. The server exposes only the approved catalog for that credential; it does not grant unrestricted platform control.
Dialfyne exposes a remote MCP server for an approved, workspace-scoped catalog. Current credentials and permissions determine available actions. Prepare team campaigns and open click-to-dial in a human-led browser flow; verify connector and tool support in the Developers page before building against it.
Power Dialer / shared campaign
Claim the account before the next call.
Current account
Northstar Labs
VP Sales / account context attached
Ask how the team handles follow-up after discovery calls.
Team queue
Claim and lockMCP workflows, scoped per workspace
Approved, workspace-scoped actions can be prepared from an MCP client. Permissions and review boundaries still apply, and a rep remains on every Dialer call.
Use the URL and credential shown on the Developers page. The server exposes only the approved catalog for that credential; it does not grant unrestricted platform control.
Where the catalog permits it, prepare a lead list, import a CSV, scrub numbers against DNC, and prepare a team campaign. The exact actions depend on current credentials and workspace permissions.
An approved click-to-dial action opens a link into the browser softphone. A human rep completes the call; the client supplies a handoff rather than call execution.
When exposed by the current catalog, retrieve coaching, scorecards, or rep progress for the workspace. Confirm the available reports and permissions in Developers.
Only connectors and tools shown as supported and permitted for the workspace should be used. Verify the current catalog and credential scope before relying on data from another system.
Workspace credentials and permissions constrain the available actions. The Developers page is the source of truth for the current credential, catalog, and scope; permissions do not silently expand.
How it works
Open the Developers page for the workspace-scoped MCP URL, current credential details, and available catalog.
Use the current credentials and permissions shown for the workspace. The catalog determines which actions are available to the client.
Prepare an approved team campaign or other supported workflow. Click-to-dial opens the browser flow for a human rep; verify any coaching or reporting action before use.
Plain-English answer
The Dialfyne MCP server is a remote Model Context Protocol server for an approved, workspace-scoped catalog. Current credentials and permissions determine available actions. Supported workflows may prepare lists and team campaigns, retrieve enabled reports, or open click-to-dial in a browser for a human rep. Verify connector and tool support in Developers.
How it compares
| Dialfyne | Other dialers / roleplay / email tools | |
|---|---|---|
| MCP server | Approved remote server, workspace-scoped | Verify current support |
| Supported client | See current Developers catalog | Verify current support |
| Use connected tools | Only supported and permitted connectors | Verify current support |
| Campaign workflow | Prepare approved team campaigns | Verify current support |
| CRM boundary | On-demand import and matched outcome writeback | Verify current integrations and writeback |
Details, without the pitch
MCP, the Model Context Protocol, is an open standard for connecting clients to external tools and data through a server. Dialfyne provides a remote MCP server with an approved, workspace-scoped catalog; the Developers page is the source of truth for the current surface.
Use an MCP-capable client supported by the current Developers page. Client support and exposed actions can change, so verify the current catalog, credentials, and permissions before relying on a workflow.
The remote MCP surface is workspace-scoped. Current credentials and permissions determine which approved actions are available, and the Developers page shows the current scope. It does not silently grant access to another workspace or expand permissions.
The approved catalog may support list preparation or import, DNC scrubbing, team campaign preparation, enabled coaching or reporting, and click-to-dial handoff. Exact actions depend on current credentials and workspace permissions. Click-to-dial opens a browser softphone for a human-led call.
Use another system only where its connector or tool is currently supported and permitted. Verify the Developers catalog and credential scope before using it as an input to an approved Dialfyne workflow; coverage is workspace-specific.
MCP support and exposed actions vary by vendor and change over time. Dialfyne provides a remote MCP server for approved, workspace-scoped workflows; verify current scope against each alternative before choosing.
Ready when you are
Open Developers to see the current MCP connection details, approved tool catalog, API references, and permissions for your workspace.