Connect
Optimize
Secure
Live 26 Actions
LeadDocket MCP Server
for AI Agents
Connect your AI agent to StackOne's LeadDocket MCP server and give it 26 MCP tools out of the box. Auth, tool execution, and security all managed.
LeadDocket MCP Server
Built by 
StackOne
StackOne 
Coverage
26 Agent Actions
Create, read, update, and delete across LeadDocket — and extend your agent's capabilities with custom actions.
Authentication
Agent Tool Authentication
Per-user OAuth in one call. Your LeadDocket MCP server gets session-scoped tokens with zero credentials stored on your infra.
Agent Auth →
Security
Agent Protection
Every LeadDocket tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.
Prompt Injection Defense →
Performance
Max Agent Context. Min Cost.
Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every LeadDocket call.
Tools Discovery →What is the LeadDocket MCP Server?
A LeadDocket MCP server lets AI agents read and write LeadDocket data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's LeadDocket MCP server ships with 26 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.
All LeadDocket MCP Tools
Every action from LeadDocket's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.
Leads
- List Leads
Retrieve a paginated list of leads filtered by status ID with optional sub-status filtering and sort order
- Get Lead
Retrieve full details of a single lead by ID including contact info, notes, messages, files, and custom fields
- Update Lead
Update properties of an existing lead such as case type, summary, incident date, office, and source
Contacts
- Create Contact
Create a new contact with name, address, phone, email, and other details
- Get Contact
Retrieve a single contact by ID with full details including custom fields and tags
- Search Contacts
Search for contacts by name, email, or phone number
- Update Contact
Update an existing contact's name, address, phone, email, and other properties
Users
- List Users
Retrieve a list of all LeadDocket users with their roles and permissions
- Get User
Retrieve a single user by ID with roles and permissions
Tasks
- Create Task
Create a new task on a lead with summary, start date, assigned user, and type
- Get Task
Retrieve a single task by ID
- Update Task
Update an existing task's summary, start date, assigned user, type, or completion status
- Delete Task
Delete a task by ID
Other (13)
- Add Lead Note
Add a new note to a specified lead
- List Leads Updated Since
Retrieve all leads updated since a given date, covering both status changes and edit events
- Get Lead Basic
Retrieve basic information for a single lead without notes, messages, and other nested lists
- List Contacts Updated Since
Retrieve all contacts updated since a given date with pagination
- Get Opportunity
Retrieve full details of an opportunity by ID including contact info, status, and custom fields
- List Unprocessed Opportunities
Retrieve all opportunities that have not been processed into leads
- List Opportunities Created Since
Retrieve all opportunities created since a specific date with pagination
- List Opportunities Updated Since
Retrieve all opportunities updated since a specific date with pagination
- List Users By Role
Retrieve users assigned to a specific role by role ID
- List Statuses
Retrieve all lead statuses with their sub-statuses and configuration
- Get Status
Retrieve a single status by ID with its sub-statuses and configuration
- List Tasks By Lead
Retrieve all tasks for a specific lead
- Change Lead Status
Change the status of a lead with optional sub-status, severity level, assigned users, and notes
LeadDocket AI Agent Use Cases
Connect your AI agent to LeadDocket and help your team scale the sales operations they run by hand today.
Post-Demo Follow-Up
Use StackOne to connect your AI agent to your CRM, email, and calendar tools to automate post-demo follow-up.
View Deal Risk Scoring
Use StackOne to connect your AI agent to your CRM, email, and calendar tools to automate deal risk scoring and pipeline alerts.
View Outbound Prospecting
Use StackOne to connect your AI agent to your CRM, sales engagement, and messaging tools to automate outbound prospecting.
ViewSet Up Your LeadDocket MCP Server in Minutes
One endpoint. Any framework. Your agent is talking to LeadDocket in under 10 lines of code.
Agent Frameworks
JSON{
"mcpServers": {
"stackone": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://api.stackone.com/mcp?x-account-id=<account_id>",
"--header",
"Authorization: Basic <YOUR_BASE64_TOKEN>"
]
}
}
}Check More crm-sales MCP Servers
Capsule CRM
127+ actions
Bloomerang
104+ actions
Pipeliner CRM
59+ actions
Filevine
53+ actions
SPS Commerce
24+ actions
Platform Resources
MCP Code Mode: Keeping Tool Responses Out of Agent Context
Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.
11 min
Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery
Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.
10 min
Indirect Prompt Injection Defense for MCP Tools: A Technical Guide
MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.
12 min
MCP vs A2A: Architecture, Security, and When to Use Each
MCP vs A2A: what each protocol standardizes, how they differ, their shared security risks including indirect prompt injection, and when to use one, both, or a hybrid architecture.
12 min
MCP vs API: What 200+ Connector Builds Taught Us
MCP wraps APIs, it doesn't replace them. After building 200+ connectors that serve both, here's when each approach wins.
14 min read
LeadDocket MCP Server FAQ
Does StackOne have a LeadDocket MCP server?
Yes. StackOne offers a hosted LeadDocket MCP server with 26 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
LeadDocket MCP server vs direct API integration — what's the difference?
A LeadDocket MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling LeadDocket. A LeadDocket MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling LeadDocket at runtime. StackOne provides both.
How does LeadDocket authentication work for AI agents?
LeadDocket authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own LeadDocket account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via
origin_owner_id.Are LeadDocket MCP tools vulnerable to prompt injection?
Yes — LeadDocket MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a LeadDocket agent and how do I avoid it?
Context bloat happens when LeadDocket tool schemas and API responses eat your LeadDocket agent's memory, preventing it from reasoning effectively. A single LeadDocket query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my LeadDocket agent can access?
Yes — you can limit which actions your LeadDocket agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my LeadDocket MCP server?
Yes — you can create custom agent actions for your LeadDocket MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research LeadDocket's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a LeadDocket MCP server?
Skip a LeadDocket MCP server if your integration is purely software-to-software — direct LeadDocket API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call LeadDocket actions at runtime.
What AI frameworks and AI clients does the StackOne LeadDocket MCP server support?
The StackOne LeadDocket MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.
Put your AI agents to work
All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.