
Lead Friendly
com.leadfriendlyPublished by leadfriendly.comOfficial publisherv1.0.0Updated Oct 24, 2026
AI phone calls, SMS and CRM records in one Lead Friendly account, compliance-checked on every send
Overview
A remote MCP server that connects an assistant to a Lead Friendly account for AI phone calls, SMS and CRM records, with compliance checks on every send.
- What you can do
- Work with AI phone calls, SMS messaging and CRM records held in one Lead Friendly account, with compliance checked on every send. Access is scoped by the API key's permission level: read only, read plus setup, or read plus write. No individual tools are listed in the supplied material, so exact operations are not documented here.
- When to use it
- Useful when an assistant should work with a Lead Friendly account's calling, messaging and CRM data, for example to look up records or prepare outreach, and the account owner wants compliance-checked sending.
- Requirements
- A remote endpoint at leadfriendly.com over streamable HTTP. A Lead Friendly account is required, and an owner or admin must create an API key under Settings > API keys with one of the permission levels. The key is passed in the Authorization header as a bearer token.
Installation
In SourceWeft
- Open Lead Friendly in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- 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.leadfriendly%2Flead-friendly/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": {
"lead-friendly": {
"type": "http",
"url": "https://www.leadfriendly.com/api/mcp/v1",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v1.0.0LatestSep 25, 2026
Score
67% 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
- Auth declaredRequired10 pts
- 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.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.