1. Overview
Connect Lative to Claude to ask questions about your sales organisation, compare productivity and efficiency, and work with plan quota and target imports. The connector brings Lative data into Claude conversations through the Model Context Protocol (MCP).
This connector is intended for revenue leaders, Revenue Operations, sales operations, finance, and other authorised teams using Lative to understand performance and manage planning inputs.
The documented tools support productivity and efficiency breakdowns, KPI trends, headcount lookups, and quota and target imports. Broader features described on Lative’s website are not automatically available through MCP: use the tools exposed by your connected server as the source of truth for current capabilities.
| Connection detail | Value |
|---|---|
| Server name | Lative |
| Remote MCP endpoint | https://mcp.eu-west-1.lative.ai/mcp |
| Connection | HTTPS; HTTP transport in Claude Code |
| Sign-in | OAuth flow using your Lative account |
| Documented clients | Claude Web and Claude Code |
| Access type | Read and write: analytics and roster reads; plan quota and target imports |
| Support | su*****@****ve.ai |
2. Before you connect
- Have a Lative account and access to the organisation and data you intend to use.
- Use a Claude account that permits connectors, or an installed and signed-in Claude Code client. Your organisation’s Claude settings may restrict connector access.
- For Claude Team or Enterprise, an Owner or Primary Owner must first add the custom connector for the organisation when following the custom setup below.
- Ensure your browser or client can reach the production MCP endpoint and complete the Lative sign-in flow. Ask IT for help if network or identity controls block access.
- Have the relevant revenue and planning data configured in Lative. Connecting MCP does not create a dataset or configure your CRM integrations.
3. Connect in Claude Web
3.1 Organisation setup: Team and Enterprise
These instructions describe adding Lative as a custom connector. Interface labels can change as Claude evolves.
- Sign in to Claude as an Owner or Primary Owner.
- Open Organization settings > Connectors and select Add.
- Choose Custom > Web and name the connector Lative.
- Enter
https://mcp.eu-west-1.lative.ai/mcpas the remote MCP server URL. - Under Advanced settings, select Register automatically to use Dynamic Client Registration (DCR).
- Select Add to finish organisation configuration.
3.2 Member connection
- Open Customize > Connectors in Claude.
- Find the Lative connector your organisation added.
- Select Connect, sign in to Lative, and review the authorisation screen.
- Complete authorisation, then start a conversation with the connector enabled.
- Ask: “Use Lative to show the available dimensions for analysis.” Confirm that a Lative tool runs and returns a result.
3.3 Individual custom connection
Where custom connectors are available on your Claude account, open Customize > Connectors, choose Add custom connector, enter Lative and the production endpoint, then follow the connection and OAuth prompts. If the option is unavailable, check your Claude plan or organisation policy.
3.4 Directory connection
Once Lative is published in Claude’s directory and made available to your account, select its listing and follow the connection prompts. Organisation approval may still be required. The custom setup above remains useful for testing before publication.
4. Connect in Claude Code
Run one of the following commands in a terminal. All examples use the production endpoint.
For personal use in the current project
claude mcp add --transport http lative https://mcp.eu-west-1.lative.ai/mcpThe default is local scope: the connection is private to you and associated with the current project. It does not create a shared .mcp.json file.
For use across your projects
claude mcp add --transport http --scope user lative https://mcp.eu-west-1.lative.ai/mcpFor shared project configuration
claude mcp add --transport http --scope project lative https://mcp.eu-west-1.lative.ai/mcpProject scope writes the server configuration to .mcp.json. Each user still signs in with their own Lative account. Follow your organisation’s policy for shared project configuration.
Authenticate and verify
- Start a new Claude Code session and enter
/mcp. - Select lative and follow the prompts to authenticate with Lative in your browser.
- Return to Claude Code and confirm the server is connected.
- Run the read-only verification prompt from Section 3.2.
To inspect configuration or connection status, use:
claude mcp list
claude mcp get lativeThe client retains your session. Re-authenticate when it expires or when the client asks you to sign in again.
5. Ask useful questions
Name the reporting dates, revenue metric, roles, dimensions, and cost structures you need. Ask Claude to show the dates, filters, and metric actually used, particularly when comparing results with the Lative application.
Dimensions and dimension values are specified by name, not ID. Ask Claude to discover the available names before applying filters. For headcount and plan operations, use the returned IDs to avoid confusion between people or plans with the same name.
-
“Using Lative, show productivity by Region from 1 January to 31 March 2026, compared with the same dates in 2025. First verify that Region is available. State the revenue metric and filters used.”
Discover the dimension and values, then retrieve a productivity breakdown for the requested periods.
-
“Show a quarterly trend of sales productivity by headcount for our current fiscal year. Include the previous fiscal year comparison and state the reporting dates.”
Retrieve sales_productivity_by_headcount trend data with a quarterly period and comparison enabled.
-
“Compare return on investment by Role for our current fiscal year. First list the available cost structures and tell me which ones are included.”
Discover cost structures and the Role dimension, then retrieve an efficiency breakdown.
-
“Show monthly total cost from 1 January to 30 June 2026 and explain the trend. State the filters and cost structures used.”
Retrieve the efficiency total_cost monthly time series and summarise the results.
-
“List our sales organisation as of 31 March 2026, including each person’s ID, role, and manager. Retrieve all pages.”
Retrieve the roster for a period ending on the requested date and follow pagination until complete.
Examples depend on the dimensions and data configured in your organisation. A missing dimension or dataset should be reported rather than substituted silently. Narrative conclusions are generated by Claude; review the underlying figures before using them for business decisions.
6. Tool reference
The following tools are documented from the supplied server descriptions. Discovery can expose additional tools; inspect their definitions before use. A tool’s name alone does not establish its permissions.
| Tool | Purpose | Effect |
|---|---|---|
search_tools | Find tool definitions using a natural-language query, ranked by relevance. | Discovery |
call_tool | Execute a discovered tool by name with its arguments. | Depends on the selected tool; may write data |
get_productivity_dimension_breakdown | Retrieve nine productivity KPIs per value for a single dimension. | Read |
get_productivity_kpi_trends | Retrieve one productivity KPI over time, with optional comparison and supported dimension splits. | Read |
get_efficiency_dimension_breakdown | Retrieve seven efficiency KPIs per value for a single dimension. | Read |
get_efficiency_kpi_trends | Retrieve one efficiency KPI over time, with an optional comparison. | Read |
list_headcounts | Retrieve a paginated headcount roster for a period. | Read |
import_plan_quota | Apply CSV quota values to individual contributors or managers in a plan. | Write: persists assigned quotas |
import_plan_target | Upload the target management source CSV for a plan. | Write: changes the plan’s target source |
Supporting tools referenced by these operations include list_dimensions, list_dimension_values, get_efficiency_cost_structures, list_plans, and get_plan_headcount_quota. Their complete input schemas were not supplied for this guide; use discovery to inspect the definitions exposed by the server.
7. Authentication, data handling, and administrator review
7.1 Authentication and session behaviour
The Lative MCP connector uses OAuth to authenticate with your Lative account. You must have access to the Lative application before connecting.
If your organisation uses enterprise managed authentication, your IT administrator must complete the required configuration and assign you access to Lative through Okta, Microsoft Entra ID, or your organisation’s identity provider. Contact your IT department if you cannot sign in to Lative.
On first connection, sign in to Lative and authorise the connector. The client retains your authentication session and may ask you to sign in again when it expires.
7.2 Data used by the connector
Tool calls send their arguments to the remote Lative MCP server; responses return the requested Lative data to Claude for use in your conversation. The documented operations can include productivity and efficiency figures, costs, bookings, headcount counts, employee names and IDs, reporting relationships, and plan quota or target inputs.
Limit the requested scope to the periods, dimensions, and people needed for the task. Follow your organisation’s rules for sharing employee, revenue, and planning data with an AI service. Lative’s privacy policy is available at https://lative.ai/privacy-policy/. Claude’s handling of conversations and tool results depends on your Anthropic service and applicable terms.
8. Disconnect or remove access
Claude Web
Open Customize > Connectors, locate Lative, and use the available disconnect or removal control. Team and Enterprise Owners can remove the custom connector from Organization settings > Connectors. Follow the prompts to complete removal.
Claude Code
Remove the configured connection using the relevant scope, for example:
claude mcp remove lative --scope userUse --scope local or --scope project if that is where the connection was registered. Check claude mcp list afterwards. Client removal should not be treated as proof that all server-side grants have been revoked.
