The Cursor MCP server for what customers said.
Add Laxis to Cursor and your agent can read the feedback call, the bug report meeting and the sprint retro — then fix, file and ship without you retyping any of it.
Start for free, no credit card required.
Claude
ChatGPT
Cursor
Grok
Meta MuseMCP
laxis · get_transcriptConnectedFound three: CSV export drops the last row, dark mode ignores the chart legend, and sign-in loops on expired tokens. Starting with the export bug — opening csvWriter.ts.
The gap between “the customer said” and “the code does” just closed.
From call to commit
Cursor reads the transcript of the feedback session, finds the bugs that were described, and starts on the fix in your codebase.
Specs with the customer's words
Generate a PRD, a ticket or acceptance criteria from a discovery call, quoting the requirement as the customer stated it.
Context your agent can cite
Ask “what did Priya say about the export format?” mid-task. Cursor answers from the meeting and keeps coding.
Add the Laxis MCP server to Cursor
One click, then a sign-in. No local process and nothing to keep running.
- 1
Install with one click
Use the Add to Cursor button above (or on the Laxis MCP GitHub page). Cursor opens and adds the Laxis server.
- 2
Sign in with Laxis
Open Cursor Settings → Tools & MCP and click Sign in (or Needs login) next to Laxis. Approve the Laxis sign-in in your browser.
- 3
Or configure mcp.json by hand
Prefer a config file? Add Laxis to ~/.cursor/mcp.json, then sign in from the MCP settings as above.
{ "mcpServers": { "Laxis": { "url": "https://app.laxis.com/mcp" } } } - 4
Use it in Agent or Chat
Ask “Use Laxis to list what the customer asked for on Tuesday's call, then create the tickets.” Cursor calls the Laxis tools as it works.
Things to ask Cursor
Cursor's agent picks the Laxis tool it needs — search, one meeting, or the full transcript.
“Read today's feedback call and create a GitHub issue for each bug mentioned.”
One issue per bug with the customer's description and repro steps.
“Write acceptance criteria for the export feature from the last two discovery calls.”
Given/when/then criteria quoting the calls they came from.
“What did the customer say about the sign-in flow? Then fix it.”
The relevant transcript lines, followed by the code change.
“Draft release notes for this sprint from the demo meeting and the merged PRs.”
Release notes that describe features the way they were demoed.
“Summarize the sprint retro and turn the follow-ups into TODO comments in the right files.”
Retro summary plus TODOs placed where the work lives.
“Which requirements from the kickoff meeting aren't reflected in the schema yet?”
A gap list comparing the meeting against the code.
Workflows developers build with Cursor + Laxis
Meetings become inputs to the agent, not notes you have to remember to read.
Feedback call → fixes
Record customer feedback sessions with Laxis. After the call, hand Cursor the meeting and let it file issues or start fixes — with the customer's exact words in each ticket.
Discovery → spec → implementation
Run discovery with Laxis recording, generate the spec in Cursor from the transcript, and implement against it. The spec stays traceable to who asked for what.
Standup-aware agent
Ask Cursor each morning what was decided in yesterday's standup and planning meetings before it starts on a task, so the work matches the latest direction.
Cursor + Laxis: questions
Either click the Add to Cursor button, which registers the Laxis server for you, or add it to ~/.cursor/mcp.json under mcpServers with the url https://app.laxis.com/mcp. Then open Cursor Settings → Tools & MCP and sign in next to Laxis.
No. It is a remote server hosted by Laxis over Streamable HTTP, so there is no binary, Docker image or npm package to run and nothing to keep updated. Cursor connects to the URL and you sign in with your Laxis account.
Four read-only tools: list_meetings, search_meetings (semantic search across transcripts), get_meeting (participants, AI summary, metadata) and get_transcript (full, timestamped). The agent chooses which to call based on your prompt.
No. The server only reads. Cursor can edit your code based on what it reads, but it cannot modify or delete meetings in Laxis.
Yes. VS Code (1.101+), Windsurf, Claude Code and any client that supports remote MCP servers with OAuth connect to the same URL.
Laxis Premium, Business and Enterprise, and the 14-day Premium trial every new account starts with.
Laxis also works in
Let your agent hear the customer.
Download Laxis, record your next feedback call, and add the MCP server to Cursor in one click.
Start for free, no credit card required.