Skip to main content
This reference describes common Octolane MCP tools by category. On connection, use tools/list to discover the current tools and input schemas. Tool availability can depend on your access and the server version. Company-brain queries use memory_list and memory_get; confirm their schemas with the connected server. See Company brain.
Connect to https://mcp.octolane.com/mcp over Streamable HTTP using OAuth or a personal API key in Authorization: Bearer YOUR_OCTOLANE_API_KEY. Requests use the connected member’s permissions. See Authentication.

Examples use illustrative names, dates, and IDs. Replace IDs with values returned by your workspace and follow the discovered tool schema; MCP arguments can differ from REST inputs.

Search & Query

Tools for finding and retrieving data from your CRM.

search_deals

Search deals with filters for pipeline, stage, account, contact, deal size, and close date. Use find_stale_deals for activity or stage staleness.

search_contacts

Search contacts by name, email, company, or job title.

search_accounts

Search accounts (companies) by name, domain, or industry.

search_emails

Search email conversations by contact, company domain, keyword, or direction.

search_meetings

Search past and upcoming meetings by keyword, attendee, or date range.

get_deal_details

Get full details of a specific deal including associated contacts, account, notes, tasks, and next steps.

get_pipeline_overview

Get a summary of your sales pipeline(s) showing deal counts, total values, and average deal size by stage.

get_signal_visitors

Retrieve website visitors identified by Octolane Signal with visit counts, intent scores, and activity dates.

get_email_thread

Get the full email thread conversation by thread ID.

get_notes

Search and retrieve notes linked to a deal, contact, or account. Supports lookup by name, email, or domain. No ID required.

get_tasks

Get tasks assigned to you or linked to a specific deal, contact, or account.

get_current_user

Get your identity, workspace role, and subscription details. Returns name, email, organization, role, and billing info.

Create & Update

Tools for writing data to your CRM. Writes can apply directly and do not necessarily enter the in-app approval queue. Enrichment and follow-up workflows depend on workspace configuration, plan entitlements, and remaining usage.

create_deal

Create a new deal in the CRM and assign it to a pipeline stage. The associated account and contacts must already exist. Create them first if needed.

create_contact

Create a new contact from an email address. Work-email domains can be linked to company accounts; personal email domains do not identify a company. Enrichment is subject to your plan and available credits.

create_account

Create a new account (company) from a domain. Enrichment follows your plan and available credits.

create_note

Create a note and link it to a deal, contact, or account.

create_task

Create a task and optionally link it to a deal, contact, or account. Use for reminders, follow-ups, action items, or next steps. For several tasks, the server also accepts a tasks array of 1–50 items with optional defaults. Do not mix a batch with single-task fields. Inspect each result and check unknown outcomes before retrying; replaying a batch can create duplicates.

update_deal_stage

Move a deal to a specific stage by stage ID.

move_deal_to_next_stage

Automatically advance a deal to the next stage in its pipeline based on stage order.

update_note

Update an existing note’s title or content.

update_task

Update an existing task. Change title, due date, priority, or mark as complete.

Pipeline Management

Tools for configuring and navigating your pipeline structure.

list_pipeline_stages

List all stages for a pipeline, showing name, order, type (won/lost/default), and win probability.

rename_pipeline

Rename a sales pipeline.

Field Discovery

Tools for discovering available fields and custom properties on your CRM records. Useful before creating or updating records to check what fields are available.

get_account_fields

Discover available fields and custom properties for accounts (companies). Returns field names, types, and valid dropdown options.

get_contact_fields

Discover available fields and custom properties for contacts. Returns field names, types, and valid dropdown options.

get_deal_fields

Discover available fields and custom properties for deals in a specific pipeline. Each pipeline can have different custom fields.

Signal

get_signal_script

Get the Octolane Signal tracking script tag for your website. Returns an HTML snippet with your organization’s unique public key to install in your website’s <head>.

Workspace

Tools for managing your workspace and team.

list_workspace_members

List all members in the workspace with their name, email, role, and avatar.

invite_team_member

Invite one or more people to your workspace by email. Requires admin or owner role.

Stale deals

find_stale_deals

Find open deals that have not moved for at least days days. stale_by: "activity" measures the linked account’s last email or meeting; "stage" measures the last stage change. A deal is never counted as older than its creation date. Won and lost deals are excluded.
Continue through the returned pagination before describing all matching deals. Use days_stale and stale_since_source to explain why a deal is included. An omitted deal may be too new to qualify; absence does not prove recent activity.

Company brain

Knowledge is accessible through the following memory tools. Read the connected server’s schemas before calling them. A read request does not authorize changing knowledge.

memory_list

List accessible memory blocks. scope can be org (shared workspace), user (your private knowledge), or both (default). Optional category filters a category such as sales_icp, sales_process, product_info, pricing, writing_style, or custom. Use entity_type (account, contact, or opportunity) together with entity_id to select knowledge linked to a record. include_pending defaults to false; proposed learnings awaiting review should not be presented as approved knowledge.

memory_get

Read a block using its required id UUID from memory_list. The response includes content, scope, category, source, version, review state, and update time. Read the applicable blocks before answering and distinguish their evidence from your own suggestions.

memory_upsert

Create or update a knowledge block when the user requests that change. Required fields are scope, category, and content; content is limited to 8,000 characters. Supply id to update an existing block. On update, scope and category remain those of the stored block. Shared org writes require administrator privileges; user blocks are private to the connected user. Use category: "custom" for a free-form block, with a nonempty title of at most 80 characters. Creating a fixed-category block replaces that category’s system block, so read it before replacing its content. Check the returned scope, category, title, and content instead of assuming every requested field changed. Optional activation_tags describe when knowledge applies; they do not automatically inject or enforce instructions in an external MCP client. The client must read applicable knowledge using memory_list and memory_get.

memory_delete

Delete a block by its required id. Confirm the target from a prior read, respect the connected member’s permissions, and verify the result. Do not delete knowledge as part of a query-only request.

Additional workflows

Discover these tools with tools/list for their full argument schemas. Availability follows the connected server and permissions. Batch record creates accept at most 50 items; direct batch updates accept at most 25 records per call. Use IDs and property names from searches and field-discovery tools. Review per-record failures before retrying, especially for operations that create new records. Scheduled email calls can send messages to people: establish the intended sender, recipients, content, and send time before making an authorized call. Scheduling accepts at most 10 drafts per call with an explicit timezone, at least 30 seconds in the future and no more than a year out. Editing and cancelling a scheduled email are separate alternatives in update_scheduled_email.

Rate limits

Handle 429 responses, honor Retry-After when provided, and back off before retrying. MCP discovery does not publish a numeric quota; do not assume REST route limits apply to every tool. See Authentication.