> ## Documentation Index
> Fetch the complete documentation index at: https://docs.laneapp.co/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Use Lane from Claude, ChatGPT, Claude Code, Cursor and other AI apps: check customer demand, see current priorities, look up and list customers, Signals and feedback, and draft Docs.

Lane's MCP server lets AI apps that support the [Model Context Protocol](https://modelcontextprotocol.io) work with your Lane workspace: Claude, ChatGPT, Claude Code, [Cursor](/cursor) and others. Ask about your product and customers from wherever you already work: "do customers want bulk CSV export?", "what are we focused on right now?", "what did `john@acme.com` say about onboarding?", without copying anything into the prompt by hand.

Each person connects their own apps with their own Lane login. There's no key to copy: the app asks you to sign in to Lane once, and stays connected.

## Availability

The MCP server is available on the **Pro** plan (not during the trial). Contributors can't use it.

## Connect an app

Every app uses the same server URL:

```text theme={null}
https://mcp.laneapp.co/mcp
```

You'll also find it, with these steps, in Lane under **Settings → MCP Server**.

### Claude

1. In Claude, open **Settings → Connectors** and choose **Add custom connector**.
2. Name it **Lane** and paste the server URL.
3. Choose **Connect**, sign in to Lane and approve. This works in claude.ai, the desktop app and mobile.

### ChatGPT

1. In ChatGPT, open **Settings → Apps** and turn on **Developer mode**.
2. Choose **Create**, name it **Lane**, paste the server URL and pick **OAuth**.
3. Sign in to Lane and approve.

### Claude Code

1. Run this in your terminal:
   ```bash theme={null}
   claude mcp add --transport http lane https://mcp.laneapp.co/mcp
   ```
2. In Claude Code, run `/mcp`, pick **lane** and choose **Authenticate**.
3. Try: "Before we build this, check Lane for customer demand."

### Cursor

Use **Add to Cursor** in **Settings → MCP Server**, or add Lane to `~/.cursor/mcp.json`:

```json theme={null}
{
  "mcpServers": {
    "lane": { "url": "https://mcp.laneapp.co/mcp" }
  }
}
```

Cursor asks you to sign in to Lane the first time you use it.

### Other apps

Any app that supports remote MCP servers with OAuth sign-in can connect with the same URL.

## What you can ask

* "Do customers want bulk export to CSV? Is it already planned?"
* "What are we focused on right now, and what do customers want most?"
* "Tell me about Acme: who have we heard from and what do they need?"
* "Which customers renew next quarter, and what have they asked for?"
* "Show the top Signals by revenue at stake that don't have a ticket yet."
* "What did `john@acme.com` say about onboarding?"
* "Write a short PRD for the top Opportunity and save it to Lane."
* "Log this customer email in Lane as feedback." (with the email pasted in)

## Tools

The server has thirteen tools. The app picks the right one for your question.

| Tool | What it does | Changes Lane? |
| :- | :- | :- |
| `get_current_priorities` | Your workspace context from **Settings → Context** (company, product, customers, priorities, what's not a priority now, competitors), accepted Opportunities, Signals already ticketed, the open Opportunities customers want most, and what's moving this week | No |
| `check_demand` | Whether customers want something, before you build it: matching Opportunities and Signals by status, how many customers and how much revenue, the top customers behind each Signal with a quote, and any Doc or ticket already in motion | No |
| `get_opportunity` | One Opportunity in full, with its Signals, and the customer feedback behind it on request | No |
| `get_signal` | One Signal in full, with its Opportunity, ticket, Docs, and the customer feedback behind it on request | No |
| `list_signals` | Signals ranked and filtered: by priority, customers, revenue at stake, newest, most recently acted on, or what's rising this week; narrowed to open, accepted or closed, to those not yet in an Opportunity, to those with or without a ticket, or to those created since a date | No |
| `get_customer` | One customer's full picture: profile, the people you've heard from, their feedback, and the Signals, Opportunities and Docs that involve them. Find them by company name, domain, a person's email, or a person at a company ("John from Acme") | No |
| `list_customers` | Customers by status, tier, whether they're marked important, or renewal date, sorted by revenue, renewal date or how much feedback they've given. With a renewal date range, it also says how many customers have no renewal date set | No |
| `search_feedback` | Customer feedback itself, by meaning ("complaints about billing"), customer, Signal, source, type, sentiment or date | No |
| `search` | Searches Opportunities, Signals, Docs and feedback | No |
| `fetch` | Opens anything `search` found | No |
| `create_doc` | Saves a Doc the app wrote (a PRD, brief or plan) as a draft for your team to review, linked to the Opportunity, Signals or feedback it used | Yes, as you |
| `update_doc` | Edits a Doc you can edit in Lane: a new title, a rewrite, or a section added at the end | Yes, as you |
| `log_feedback` | Saves a customer email, call note or message as feedback, linked to the customer, so Lane analyses it like any other feedback | Yes, as you |

## What a connected app can do

* **Read** your Signals, Opportunities, feedback and customers, and workspace and public Docs. Private Docs, including yours, aren't shared.
* **Change** only what you can change: draft new Docs, edit Docs you can edit in Lane, and log feedback. Changes show your name and the app that made them.
* **Never delete** anything.

## Access follows your Lane account

An app connected to Lane works as you, not as the workspace. It sees what your workspace shares with every member: Signals, Opportunities, customer feedback, customers, and workspace and public Docs. Private Docs, including your own, are never shared with an app.

When it changes something, it does so as you and within your role: it can only edit Docs you can edit in Lane, and everything it creates shows your name and the app. Contributors can't connect apps. Everyone else can see which apps people in the workspace have connected, and only the workspace owner can disconnect someone else's.

## Manage connected apps

**Your apps:** **Settings → Connections** lists the apps you've connected (under **Lane MCP**), when each was last used, and a **Disconnect** button. A disconnected app stops working with Lane right away, until you choose **Allow again**.

**Everyone's apps:** **Settings → MCP Server** lists every app connected in the workspace under **Connections**. You can disconnect your own; the workspace owner can disconnect any of them. An app the owner disconnected can only be allowed again by the owner.

## FAQs

**Q: Do I need a key or token?**<br />A: No. Each app signs you in with your Lane login. There's nothing to copy or keep secret.

**Q: Can an app change my data?**<br />A: Only in three ways, and only as you: draft or edit Docs you can edit, and log feedback. It can't delete anything, change settings, or see private Docs.

**Q: Which app should I use?**<br />A: Any of them. Claude and ChatGPT are good for questions and drafting; Claude Code and Cursor let you check customer demand while you build.

**Q: How do I disconnect an app?**<br />A: In **Settings → Connections**, choose **Disconnect** next to it. You can also remove Lane from the app itself.

**Q: What's the difference between this and the API?**<br />A: The MCP server is for AI apps working with your workspace in a conversation. The [API](/api-key) is for programmatic integrations that create feedback and read signals.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.