Connect Leadping MCP Servers

Connect AI assistants to public Leadping documentation or authenticated organization tools through MCP.

Leadping provides two remote Model Context Protocol (MCP) servers. Choose the server based on whether the assistant needs public documentation or private organization access.

Server	URL	Access
Documentation	https://leadping.ai/docs/mcp	Public, read-only docs and API reference
Organization tools	https://api.leadping.ai/mcp	Authenticated Leadping organization data and lead actions

Do not give an organization credential to the public documentation server. Use the organization-tools server only when the assistant needs private account data or actions.

Documentation server

Use the documentation server to let an assistant:

• search Leadping guides and API reference content;
• read complete documentation pages;
• inspect the read-only documentation tree; and
• cite the relevant Leadping pages in its answer.

It cannot sign in, read private data, create or change leads, send messages, place calls, modify settings, or issue credentials.

The server exposes:

Tool	Purpose
search_leadping_documentation	Search guides, API reference content, and examples
query_docs_filesystem_leadping_documentation	Read pages, list the docs tree, or search exact terms

Start with search for broad questions. Use the filesystem tool when exact page content or structure matters.

Organization-tools server

Use the authenticated server when an assistant needs to work with one Leadping organization.

Read tools include:

• current organization and organization-switch options;
• leads and conversations;
• events and event details; and
• sources and source metrics.

Lead-management tools include:

• creating and updating leads;
• archiving and restoring leads;
• adding, replacing, and removing tags; and
• soft-deleting a lead after explicit confirmation.

Write tools enforce the same organization access and leads:write permissions as the API. Creating a lead may start configured routing and automations. Deleting a lead removes it from user-facing lists and workflows while retaining its lead and conversation records.

Authenticate organization tools

Provide a Leadping user access token or organization API key through the MCP client’s supported Bearer-token mechanism:

Authorization: Bearer sk_example

Store the credential in the client’s secret or environment configuration. Do not commit it to a repository.

Source keys beginning with lp_src_ are not valid organization-tools credentials. See API Authentication.

Add the documentation server

Use this URL in any MCP client that supports remote HTTP servers:

https://leadping.ai/docs/mcp

After configuring the server, restart or refresh the client if required.

Codex

[mcp_servers.leadping]
url = "https://leadping.ai/docs/mcp"

Cursor

{
  "mcpServers": {
    "leadping": {
      "url": "https://leadping.ai/docs/mcp"
    }
  }
}

VS Code

{
  "servers": {
    "leadping": {
      "url": "https://leadping.ai/docs/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http Leadping https://leadping.ai/docs/mcp

Use the current configuration format documented by your client if it differs from these examples.

Test the connection

Try a direct request:

• Find the TrustedForm requirement for external leads.
• Explain how to authenticate a source intake request.
• Show the Leadping carrier-registration checklist.
• Find the endpoint for creating a lead and cite the API reference.

For organization tools, begin with a read-only request such as listing sources or reading a known lead. Confirm the organization context before approving write actions.

Protocol behavior

The organization-tools server uses Streamable HTTP. Let the MCP client negotiate the protocol and transport behavior unless that client requires explicit configuration.

Troubleshooting

Problem	Check
Server does not appear	Confirm the exact URL and restart the client
Tools are unavailable	Confirm the client supports remote HTTP MCP servers
Documentation search returns nothing	Ask a direct Leadping question and verify the docs server is connected
Organization request is unauthorized	Confirm the Bearer credential and organization access
Source key is rejected	Replace it with a user token or organization API key
Protocol error	Let the client negotiate instead of pinning a revision
Client supports only local stdio	Use a remote-MCP bridge supported by that client

For authenticated setup, use https://api.leadping.ai/mcp; for public documentation, use https://leadping.ai/docs/mcp.