Skip to content
Docs

Claude Desktop

Add Basemodo's Plugin to the Claude desktop app, then sign in in your browser.

Set up

The Plugin gives Claude Basemodo's Skills, which teach it when and how to use Basemodo, and its Remote MCP, which it acts through. In the Claude desktop app, select Customize in the sidebar, then Plugins, choose Add, then Add marketplace, and enter:

basemodocom/agent

Basemodo is then among your plugins: select it, then Add. Open it, and on its Connectors tab add Basemodo's connector.

Then sign in: select Connect on the connector. Claude sends you to basemodo.com in your browser, which asks you to approve Claude. Approve it, and Claude acts as you through its Agent Grant. The Plugin is on your Claude account, so it is also on claude.ai and in the Claude mobile app.

On a Team or Enterprise plan, an Owner chooses whether members may add a marketplace of their own, and adds the connector for the organization: if you cannot, ask one to add it, then connect it as yourself.

Other ways

Use one way in Claude Desktop: the Plugin, or one of these. The Plugin carries the Remote MCP, and the local MCP serves the same tools, so with two Claude sees every tool twice (one way per client).

The Remote MCP alone

Without the Skills: select Customize in the sidebar, then Connectors, and choose Add custom connector. Enter this as the remote MCP server URL, with no OAuth client ID or secret, and click Add:

https://mcp.basemodo.com

Then select Connect on it and approve Claude on basemodo.com. In a conversation, turn Basemodo on from the + menu, under Connectors. A connector belongs to your Claude account, so Basemodo is also there on claude.ai and in the Claude mobile app.

On a Team or Enterprise plan, an Owner adds it for the organization instead, in Organization settings, Connectors: Add, then Custom, then Web, with the same URL. Each member then finds Basemodo under Customize, Connectors, with the Custom label, and selects Connect to sign in as themselves.

The local MCP

The same tools on your computer, basemodo mcp, which deploys a folder instead of a GitHub repository. Claude Desktop starts local MCP servers from its configuration file. Open the Claude menu, Settings..., then Developer, and Edit Config. Add Basemodo to claude_desktop_config.json:

{"mcpServers": {"basemodo": {"command": "basemodo", "args": ["mcp"]}}}

Quit Claude Desktop completely and open it again. The basemodo command must be installed (curl -fsSL https://basemodo.com/install | sh on a Mac, irm https://basemodo.com/install.ps1 | iex in Windows' PowerShell) and signed in (basemodo login). If Claude Desktop cannot find it, put its full path in command: which basemodo prints it (where basemodo on Windows).

Or let the CLI add the Local MCP, with its full path, keeping everything else in the file (and signing the CLI in when it is not); --remove takes it out again:

Terminal window
basemodo setup --mcp

When Claude Desktop already has the Remote MCP in that file, setup asks before it takes the Remote MCP's entry out and puts the Local MCP in its place.

What it needs

A Claude plan: Free, Pro, Max, Team or Enterprise. On Free, you can add one custom connector. On Team and Enterprise, only an Owner adds one (on Enterprise, also a member whose role manages the organization's libraries).