Lansy Desk

ai.lansyPublished by lansy.aiOfficial publisherv1.0.0Updated Oct 26, 2026

Bot-free AI meeting notes, insights & coaching

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lansy Desk is a remote MCP server for bot-free AI meeting notes, insights and coaching, connected over OAuth.

What you can do
  • The listing gives no tool list, so capabilities are known only from its one-line description.
  • It is presented as bot-free AI meeting notes, meaning meeting capture without a bot joining the call.
  • It also advertises insights and coaching drawn from meetings.
  • No further detail on specific actions is provided.
When to use it
Consider it if you want an assistant to work with AI-generated meeting notes, meeting insights or coaching, and you prefer a setup that does not add a bot participant to calls.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's API host; OAuth authentication is required. No environment variables, headers or packages are declared.
Before you install
Meeting notes and coaching imply that conversation content is processed by a third-party service; review the provider's data handling before connecting. OAuth grants the server access to your account, so check the scopes requested. No tool list is published, so what it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Lansy Desk in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.lansy%2Fdesk/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lansy-desk": {
      "type": "http",
      "url": "https://api.ae.app.lansy.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 21, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.