Connect AI Assistants to Leadping MCP Servers

Leadping provides two remote Model Context Protocol (MCP) servers:

Server	URL	Access
Documentation	`https://leadping.ai/docs/mcp`	Public, read-only documentation
Organization tools	`https://api.leadping.ai/mcp`	Authenticated organization data and lead management

Use the documentation server when you want an AI assistant to answer Leadping questions from the current docs and API reference. Use the organization-tools server when an assistant needs to inspect authenticated organization data or manage leads.

Documentation server

The documentation server gives compatible AI tools read-only access to the published documentation and API reference. Once connected, your assistant can:

Search the Leadping docs for relevant guides, API details, and examples
Read full documentation pages when it needs more context
Inspect the OpenAPI reference through the documentation filesystem
Link answers back to the relevant Leadping docs pages

Good use cases include:

Asking an agent to find the right lead intake endpoint.
Reviewing TrustedForm requirements while writing a posting integration.
Checking carrier registration setup details before launch.
Generating internal runbooks that cite the Leadping docs.
Helping a developer use the SDKs without pasting reference pages into chat.

What it does not do

The documentation server cannot:

Sign in to your Leadping account
Create, edit, or delete leads
Send SMS or place calls
Change sources, phone numbers, billing, users, or settings
Read private account data
Issue agent credentials, API keys, source keys, or user tokens

For authenticated account actions, use the Leadping application or API directly. For agent and service authentication, start with API Authentication or the machine-readable guide at https://leadping.ai/auth.md.

Organization-tools server

The organization-tools server is hosted at:

https://api.leadping.ai/mcp

It provides read-only tools for:

Reading the current organization and available organization-switch options
Listing and reading leads
Listing conversations, including conversations for a specific lead
Listing events, lead events, and event details
Listing and reading sources and source metrics

It also provides lead-management tools for:

Creating and updating leads
Archiving and restoring leads
Adding, replacing, and removing lead tags
Permanently deleting a lead after explicit confirmation

Write tools enforce the same organization access and leads:write permissions as the Leadping API. Tool annotations identify mutations and permanent deletion as consequential operations so compatible MCP clients can apply their approval policies. Creating a lead can start configured Leadping routing and automation workflows.

Authentication

The organization-tools server requires a Leadping user access token or organization API key:

Authorization: Bearer sk_example

Store the credential in your MCP client’s secret or environment-variable mechanism rather than directly in a committed configuration file. See API Authentication for credential creation, discovery metadata, and security guidance.

Transport and protocol

The organization-tools server uses stateless Streamable HTTP and supports the MCP 2026-07-28 protocol revision. Compatible clients negotiate the protocol automatically, and older MCP clients remain supported. Do not manually perform an initialization handshake, persist an Mcp-Session-Id, or pin a protocol version unless your MCP client specifically requires it. With the current protocol, capabilities and protocol information travel with each request.

What is MCP?

MCP is an open protocol that lets AI applications connect to external tools and data sources in a standard way. Instead of pasting documentation or manually wiring API calls into chat, you connect the assistant to the appropriate Leadping server.

Documentation tools

The hosted server exposes documentation-focused tools:

Tool	Use it for
`search_leadping_documentation`	Broad searches across Leadping guides, API reference content, and examples
`query_docs_filesystem_leadping_documentation`	Reading specific `.mdx` docs pages, listing the docs structure, or searching exact terms in a virtual read-only docs filesystem

Start with search for general questions. Use the filesystem tool when the assistant needs exact page content or wants to inspect the docs tree.

Documentation quick start

Add the MCP server URL to an MCP-compatible client that supports remote HTTP servers:

https://leadping.ai/docs/mcp

After connecting, restart or refresh your client if required, then ask a Leadping-specific question. To use authenticated organization tools instead, configure https://api.leadping.ai/mcp and provide a Leadping credential through the client’s supported bearer-token mechanism. Try prompts like:

“Search the Leadping docs for TrustedForm requirements.”
“How do I prepare a business for 10DLC carrier registration in Leadping?”
“Find the Leadping API endpoint for creating a lead and explain the required fields.”
“What message categories are prohibited on Leadping?”

Codex

Add the Leadping MCP server to your Codex MCP configuration:

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

Restart Codex so the server is loaded.

Cursor

Add the server to your Cursor MCP configuration:

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

Then enable the server in Cursor settings. Once connected, Cursor can use the Leadping docs while helping you write integration code.

VS Code

For VS Code clients that support MCP over HTTP, add a server entry similar to:

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

Open the MCP configuration in VS Code and start the server from the editor controls if your extension requires it.

Claude Code

If your Claude Code version supports remote HTTP MCP servers, add Leadping with:

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

Restart Claude Code, then run /mcp to confirm that the Leadping server is connected.

How the documentation server works

Your AI assistant receives a Leadping-related question.
The assistant searches the Leadping MCP server for relevant docs.
If needed, it reads the full page content from the virtual docs filesystem.
The assistant answers using the retrieved documentation context.

Ask the assistant to cite the docs page it used when you need a supportable answer.

Troubleshooting

If your assistant cannot use the Leadping MCP server:

Confirm the server URL is exactly https://leadping.ai/docs/mcp
Check that your client supports remote HTTP MCP servers
Restart the MCP client after changing configuration
Verify the server appears as connected in your client’s MCP tools list
Ask a direct docs question, such as “Search Leadping docs for carrier registration”
If a client rejects one of the examples above, use that client’s current MCP setup format and keep the Leadping server URL the same

If your client only supports local stdio MCP servers, use a supported remote-MCP bridge for that client, or check your client’s current MCP documentation. For the organization-tools server:

Confirm the URL is exactly https://api.leadping.ai/mcp
Confirm the client sends Authorization: Bearer <credential>
Use an organization API key rather than a source key; lp_src_... credentials are ingestion-only
Allow the client to negotiate the MCP protocol instead of pinning a revision

Start Here

Build Your Workflow

Prepare for Production

Build with Leadping

Security & Trust

Policies & Legal

Connect AI Assistants to Leadping MCP Servers

Documentation server

What it does not do

Organization-tools server

Authentication

Transport and protocol

What is MCP?

Documentation tools

Documentation quick start

Codex

Cursor

VS Code

Claude Code

How the documentation server works

Troubleshooting

​Documentation server

​What it does not do

​Organization-tools server

​Authentication

​Transport and protocol

​What is MCP?

​Documentation tools

​Documentation quick start

​Codex

​Cursor

​VS Code

​Claude Code

​How the documentation server works

​Troubleshooting

Documentation server

What it does not do

Organization-tools server

Authentication

Transport and protocol

What is MCP?

Documentation tools

Documentation quick start

Codex

Cursor

VS Code

Claude Code

How the documentation server works

Troubleshooting