MCP server

Connect AI assistants such as Claude, Codex or Cursor to your data through the MCP server — by URL or with an API key.

The MCP server lets AI assistants that support the Model Context Protocol — such as Claude Desktop, Claude Code or Cursor — work with your LocalUp data. Once connected, you can ask the assistant in plain language, for example to summarise this week's reviews or list locations with a low rating, and it reads the data through LocalUp.

Open it from the sidebar: Other → MCP server. If you don't see the item, the MCP server is not enabled for your account — ask your account manager.

Layout

Server switch (top right) — turns the MCP server On or Off for your account. When it is off, assistants can't connect.
Server endpoint — the address to add to your MCP client, with a Copy button.
Connect by URL — the server URL and step-by-step instructions for Claude and Codex.
Scopes — switches that control what connected assistants are allowed to do.
Authorized assistants — assistants connected by URL, with Revoke.
Connected clients — assistants that have connected to your account.
Claude Desktop config — a ready-made configuration for Claude Desktop and a command for Claude Code.

Authentication

Assistants connect in one of two ways:

By URL — paste the server URL into Claude or Codex, sign in to LocalUp on the consent screen that opens, choose the permissions and click Allow. No key is copied, and you can revoke access under Authorized assistants.
With an API key that has the mcp:connect scope. Create one on the API screen — see Create an API key. Requests through the MCP server count towards the same per-minute limit as the API: every tool call is one request.

Scopes

Each switch in Scopes allows or blocks a group of actions for connected assistants. Turn off everything the assistant doesn't need — for example, keep only reading if you just want reports and summaries.

Authorized assistants

Assistants connected by URL, with who authorized them, when they were last used and their permissions. Revoke cuts the assistant off immediately; connect it by URL again to use it again.

Connected clients

Each entry shows the assistant, its status (active or revoked) and when it last connected.

Revoke — the assistant loses access immediately and has to authenticate again.
Remove — deletes the connection record from the list. Revoke it first if it may still connect.

Connect Claude or Codex by URL

Make sure the Server switch is On.
In Connect by URL, copy the Server URL.
Connect your assistant:
- Claude (claude.ai, Desktop, mobile): open Settings → Connectors, click Add custom connector, paste the URL, click Add and then Connect.
- Claude Code: run the command from the Claude tab, then type /mcp and choose Authenticate.
- Codex: run the codex mcp add and codex mcp login commands from the Codex tab.
A LocalUp window opens. Sign in if asked, check the permissions and click Allow.

Connect with an API key (Claude Desktop config)

Make sure the Server switch is On.
Create an API key with the mcp:connect scope and copy the token.
In Claude Desktop config, choose your operating system (macOS or Windows) and click Copy config.
Paste the configuration into Claude Desktop's configuration file as shown, and replace the token placeholder with your API key.
Restart Claude Desktop.

Claude Desktop reaches the server through the mcp-remote bridge, which requires Node.js on your computer. Claude Code supports remote servers natively: click Copy command, replace the token placeholder and run the command in your terminal.

Other MCP clients: add the Server endpoint and send your API key in the Authorization: Bearer … header.

Important: The assistant can do whatever the key's scopes and the MCP Scopes allow. Grant only what you need, and revoke the key or the client when you stop using it.