To install a local MCP server on Windows, download LMCP — a free local MCP server that connects Claude Desktop, Cursor, VS Code or ChatGPT to Outlook, Microsoft Teams and OneDrive on your PC. It installs to your user folder in about 30 seconds, needs no admin rights, and auto-configures your AI clients. No API keys, no Azure AD, no cloud processing — everything runs on your machine.

Time to complete: ~5 minutes
Requirements: Windows 10 or later (64-bit), Claude Desktop or Cursor

Step 1 — Install LMCP

Download LMCP for Windows and install it:

Run the downloaded LMCP-Setup.exe from your Downloads folder
Follow the installer — it installs to your user folder, no admin rights needed
LMCP starts automatically and appears in your system tray

Takes about 30 seconds. The installer auto-configures your AI clients — nothing to edit by hand.

Prefer PowerShell? One line does the same thing:

irm https://www.local-mcp.com/install-windows | iex

What runs on your PC: LMCP runs entirely as a local system tray app. No data is sent to the cloud during setup or operation.

Step 2 — Connect your AI client

Claude Desktop (recommended for most users)

The installer automatically adds LMCP to your Claude Desktop config. You just need to restart Claude Desktop for the change to take effect.

Quit Claude Desktop completely (right-click the system tray icon → Quit, not just closing the window)
Reopen Claude Desktop
Start a new conversation

That is it. No manual config editing required.

Manual config (if auto-setup did not run)

Open %APPDATA%\Claude\claude_desktop_config.json in a text editor and add:

{
  "mcpServers": {
    "local-mcp": {
      "command": "npx",
      "args": ["-y", "local-mcp@latest", "stdio"]
    }
  }
}

Then restart Claude Desktop.

Cursor

Cursor requires Agent mode to use MCP tools. Standard Chat mode will not show the tools.

Open Cursor Settings → MCP Servers
Add a new server:
- Name: local-mcp
- Command: npx
- Args: -y local-mcp@latest stdio
Save and restart Cursor
Switch to Agent mode when starting a conversation

Other clients (VS Code, Windsurf)

Add the MCP server config pointing to npx -y local-mcp@latest stdio, then restart the client.

Step 3 — Make your first tool call

Verify the connection:

Run diagnostics on LMCP and tell me which tools are available.

Read your Outlook inbox:

What are my 5 most recent unread emails in Outlook?

Check your Outlook calendar:

What is on my calendar today and tomorrow?

Catch up on Teams:

What did the team discuss in Teams today?

Verifying it is working

After your first tool call, you will see tool use blocks showing which tools were called. If Claude responds with your actual Outlook or Teams data, LMCP is set up correctly.

You can also ask:

Run run_diagnostics and show me the full health report.

Limitations on Windows

A few things are worth knowing up front, so a first prompt does not read as a bug:

Outlook tools need classic desktop Outlook — the new Outlook app (Microsoft.OutlookForWindows, the default in recent Microsoft 365 installs) does not register the COM interface LMCP uses. If your Outlook prompts fail, check whether you are on classic Outlook.
Teams and OneDrive need their desktop apps signed in — LMCP reads local data those apps already keep on your PC; it does not work against the web versions.
Sending Teams messages needs a Microsoft 365 account connected (OAuth via Microsoft Graph) — reading chats and channels does not.
The Windows tool catalog is smaller than the macOS one — WhatsApp, iMessage, OmniFocus and Notion are Mac-only integrations and are not available on Windows.

Common issues

“I do not see any LMCP tools in Claude Desktop”

Quit Claude Desktop completely and reopen. Then verify:

type %APPDATA%\Claude\claude_desktop_config.json

You should see "local-mcp" in mcpServers. If not, re-run the installer.

“Cursor is not using the tools”

Switch to Agent mode — tools are not available in standard Chat mode.

“Claude says it cannot access Outlook”

Check that you are running classic desktop Outlook (not the new Outlook app), that it has a profile configured, and that it is open at least once so Windows registers its COM server.

“The install command failed”

Try the PowerShell one-liner directly:

irm https://www.local-mcp.com/install-windows | iex

Frequently Asked Questions

Does LMCP work on Windows?

Yes. LMCP has a native Windows build with its own tool catalog for Outlook, Microsoft Teams, OneDrive, Office documents, and Windows-specific automation — installed with a signed .exe, no admin rights required.

Do I need to install Node.js first?

No, not for the .exe installer or the PowerShell one-liner — both bundle everything needed. Node.js is only required if you use the npx local-mcp@latest manual config path.

Is it free?

Yes — free, no paid tier, permanent license.

What is next

Have a question? Ask Claude to use the report_problem tool, or open the LMCP system tray icon and click Report Problem.

Getting Started with LMCP on Windows