The server exposes 47 tools, all prefixed kodlo_. Claude picks them for you; you rarely need to name one.
How to read the tables
- Changes data: the tool writes to your workspace. Read-only keys cannot call it, and it counts toward the write limit.
- Costs: 💲 means the tool spends AI budget from your workspace’s plan. See Costs.
- Async: the tool returns an operation id and finishes in the background.
client_request_id: an optional field on create tools that makes them safe to retry. A retry with the same id returns the first result instead of creating a duplicate.
untrusted: text written by third parties or imported from the web (contact bios, posts, documents, report text) comes back inside an untrusted object. Claude treats it as data, never as instructions.
Lists are paged. When a result has next_cursor, Claude passes it back with the same filters to get the next page.
| Tool |
What it does |
Changes data |
kodlo_whoami |
Called first. Returns you and your workspace, your role and plan, AI budget used, which capabilities are available (with a reason when one isn’t), and any runs in progress. |
No |
kodlo_get_workspace_profile |
The company profile written by your workspace’s admins. It is edited in the web app. |
No |
kodlo_get_tone_of_voice |
Your own tone-of-voice prompts and sample messages, default first. It never returns a teammate’s. |
No |
| Tool |
What it does |
Changes data |
kodlo_list_campaigns |
Lists campaigns with contact counts per status. Filter by status. |
No |
kodlo_get_campaign |
A campaign’s overview, ICP, offering, contact counts and recent discovery runs. |
No |
kodlo_create_campaign |
Creates a campaign. Names are unique in the workspace. |
Yes |
kodlo_update_campaign |
Renames a campaign, changes its status or replaces its overview. Status moves: active ↔ paused, → completed, completed → archived (final). Campaigns are never deleted. |
Yes |
kodlo_set_campaign_icp |
Writes the structured ICP: what you sell, target companies, personas, signals, disqualifiers, notes. |
Yes |
kodlo_set_campaign_section |
Writes or removes the Offering or Outreach Playbook section. An empty body removes it. |
Yes |
| Tool |
What it does |
Changes data |
kodlo_search_contacts |
Free-text search over name, company, title and location. Filter by campaign and status, and sort. |
No |
kodlo_get_contact |
The full contact record, its 10 latest timeline events and its open tickets. |
No |
kodlo_create_contacts |
Adds 1–50 contacts, each with a campaign and a first name. Duplicates (same LinkedIn URL, or same full name and company) are reported, not created. |
Yes |
kodlo_update_contact |
Changes the fields you pass. An empty string clears a field. Do Not Contact contacts cannot be edited. |
Yes |
kodlo_set_contact_status |
Sets the pipeline status: contact, prospecting, engaged, nurturing, qualified, meeting_scheduled or rejected. It cannot set or lift Do Not Contact. |
Yes |
kodlo_copy_contact_to_campaign |
Copies a contact into another campaign as a new record. |
Yes |
Discovery is a five-step flow. Nothing is added to your CRM until the import step.
| Tool |
What it does |
Changes data |
Costs |
kodlo_discovery_prepare |
Step 1. Checks that the campaign’s ICP is ready and returns questions to answer if not, plus warnings and your budget. |
No |
Free |
kodlo_discovery_start |
Step 2, async. Searches the web for people who match the campaign and your focus. Takes a few minutes, up to about an hour. Creates a review set only. |
Yes |
💲 |
kodlo_discovery_review |
Step 3. Candidates with their fit and whether they can be imported, plus the people the search excluded. |
No |
Free |
kodlo_discovery_decide |
Step 4. Records accept and reject decisions. Rejected people are excluded from future searches for that campaign. |
Yes |
Free |
kodlo_discovery_import |
Step 5. Adds the accepted candidates as contacts, each with a timeline note. Safe to call again. |
Yes |
Free |
Only the person who started a run, or an admin or owner, can review, decide on or import it.
| Tool |
What it does |
Changes data |
Costs |
kodlo_research_start |
Async. A deep web investigation of a person, company, market or topic that returns a cited Markdown report. Depth: economy (about 5 min), standard (about 10–20 min) or thorough (up to 30 min). The report is filed in the workspace’s shared Deep Research Reports folder, which every member can read. |
Yes |
💲 |
kodlo_research_get_report |
Reads a report, 20,000 characters per page. |
No |
Free |
kodlo_lookup_contact |
Async, about 15 seconds. Searches the public web for a contact already in your CRM: profile and recent public posts (LinkedIn and X by default). It adds one timeline event and proposes profile fields without writing them. You approve them, and Claude applies them with kodlo_update_contact. |
Yes |
💲 cents |
kodlo_enrich_contact |
Async, about a minute. Pulls partner data for a contact: profile, follower counts and posts with engagement. With scope: account it covers the contact’s employer, optionally with web-traffic estimates. It fills empty fields only and never overwrites a value. Pass up to 25 contact_ids for one cheaper batch run. |
Yes |
💲 tens of cents per contact |
Lookup and enrichment need either a LinkedIn URL or a first name, last name and company. They refuse Do Not Contact contacts before spending anything. Run a lookup first, and enrich only when you need more.
| Tool |
What it does |
Changes data |
Costs |
kodlo_list_knowledge_projects |
The projects you can see: your own, shared ones, and the Deep Research Reports and Slide Decks folders. |
No |
Free |
kodlo_create_knowledge_project |
Creates a folder, either private (only you) or public (the whole workspace). |
Yes |
Free |
kodlo_add_knowledge_document |
Adds a document to one of your projects: Markdown (up to 2 MB), a public URL (kōdlo fetches it), or a file (PDF, DOCX, XLSX, PPTX, CSV, TXT or MD, up to 10 MB). It is indexed in the background. |
Yes |
Free |
kodlo_get_knowledge_file |
A document’s processing status (READY means searchable), and optionally its extracted text, 20,000 characters per page. |
No |
Free |
kodlo_search_knowledge |
Semantic search with 1–5 queries. It returns excerpts. |
No |
💲 a little |
| Tool |
What it does |
Changes data |
kodlo_list_tickets |
Tickets, newest first. Filter by status, assignee or creator (an id or me), source or text. |
No |
kodlo_get_ticket |
A ticket with its content, comments, assignee and linked contact. |
No |
kodlo_create_ticket |
Creates a task, linked to a contact through a timeline event or at workspace level. The assignee (you by default) is notified. |
Yes |
kodlo_update_ticket |
Changes the title, content, status (pending, in_process, done), priority, deadline or assignee. A ticket’s owner can change anything; its assignee can change only the status. |
Yes |
kodlo_comment_ticket |
Adds a comment. @mentions notify people. |
Yes |
kodlo_delete_ticket_comment |
Deletes a comment. Allowed for its author or an admin or owner. |
Yes, destructive |
kodlo_delete_ticket |
Deletes a ticket. Owner only. It disappears at once and is purged after your workspace’s retention period. |
Yes, destructive |
| Tool |
What it does |
Changes data |
kodlo_get_timeline |
A contact’s events, newest first. Archived events are left out unless you ask for them. |
No |
kodlo_list_event_types |
Your workspace’s active event types. |
No |
kodlo_add_event |
Logs a call, meeting, email or note on a contact, credited to you. Markdown, up to 10,000 characters. |
Yes |
kodlo_update_event |
Edits an event’s title, content or type. Allowed for its author or an admin or owner. Every edit is kept as a version. |
Yes |
kodlo_comment_event |
Adds a comment of up to 1,000 characters. @mentions notify people. |
Yes |
kodlo_create_event_type |
Adds an event type. Admins and owners only. |
Yes |
These tools cover your own kōdlo chat history only, never a colleague’s.
| Tool |
What it does |
Changes data |
Costs |
kodlo_search_conversations |
Keyword search, plus search by meaning when long-term memory is on for your workspace. |
No |
💲 a little (meaning search) |
kodlo_get_session |
Opens one of your conversations, with the documents it produced. |
No |
Free |
| Tool |
What it does |
Changes data |
kodlo_get_operation |
The status of a background run: queued, running (with progress), succeeded (with ids and a suggested next step), failed or canceled. |
No |
kodlo_list_operations |
Your recent runs, newest first. Filter by kind. |
No |
kodlo_cancel_operation |
Cancels a run. A queued run is cancelled with nothing spent. A running one stops within about 30 seconds, and the work done so far stays billed. |
Yes, destructive |
The server also offers three ready-made prompts. In clients that support MCP prompts, they appear in the prompt or slash-command menu.
| Prompt |
What it does |
find_leads: Find new leads for a campaign |
Walks through the whole discovery flow and leaves every decision to you. Optional argument: campaign name. |
research_brief: Prepare a deep research brief |
Asks for each part of a research brief and reminds you that the report goes to the shared folder. Optional argument: subject. |
daily_pipeline: My pipeline today |
Due tickets, next steps, and engaged or qualified contacts that have gone quiet. Asks before changing anything. |
Clients that support MCP resources can attach these directly. They follow the same permissions as the tools.
| URI |
Content |
kodlo://reports/{artifact_id} |
One of your research reports, in Markdown |
kodlo://campaigns/{campaign_id} |
A campaign, as JSON |
kodlo://contacts/{contact_id} |
A contact, as JSON |
kodlo://knowledge/files/{file_id} |
A Knowledge Hub document, in Markdown (up to 200,000 characters) |