Skip to main content

Setting up Fulcrum MCP and the AI Toolkit in the Claude desktop app

Connect Claude to your Fulcrum organization and teach it Fulcrum best practices.

O
Written by Oscar Mendoza

This article shows you how to connect Fulcrum MCP and install the AI Toolkit in the Claude desktop app. After setup, you can use Fulcrum in Claude chat, in Cowork, and in Claude Code in VS Code or the browser when you're signed in with the same Claude account.

If you use Claude Code from a terminal, see Setting up Fulcrum MCP and the AI Toolkit in Claude Code (command line) instead.


Prerequisites

  • An API token and your region's endpoint. See Getting your API token and endpoint for Fulcrum MCP.

  • Node.js installed on your computer. To download it, visit the Node.js website, or contact your IT team.

  • Permission in Claude to edit developer settings and add plugins. On Claude Team and Enterprise plans, your Claude administrator controls these permissions.


Connecting Fulcrum MCP

In this section, you add Fulcrum to Claude's configuration file.

If the file already lists other MCP servers, don't replace its contents. Add only the "fulcrum" section inside the existing "mcpServers" section, with a comma after the entry before it. Replacing the whole file removes your other connections.

  1. In Claude, select your name in the bottom-left corner, then select Settings.

  2. Select Developer, then select Edit Config. Finder (Mac) or File Explorer (Windows) opens with the claude_desktop_config.json file selected.

Edit Config button in the Developer section of Claude settings.

  1. Open the file in a text editor, such as TextEdit, Notepad, or VS Code.

  2. Replace the contents of the file with the following text:

{
"mcpServers": {
"fulcrum": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.fulcrumapp.com/",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer YOUR_FULCRUM_API_TOKEN"
}
}
}
}
  1. Replace YOUR_FULCRUM_API_TOKEN with your API token. Keep the word Bearer and the space before the token.

  2. If your organization isn't hosted in the United States, replace https://mcp.fulcrumapp.com/ with your region's endpoint.

  3. Save the file.

  4. Quit Claude completely, then open it again. Closing the window doesn't apply the changes. On Mac, in the menu bar, select Claude, then select Quit Claude. On Windows, right-click the Claude icon in the system tray, then select Quit.

Expected outcome: In Settings > Developer, fulcrum appears with the status running.
​

Fulcrum MCP server listed with running status in Claude Developer settings.

Tip: If you have Claude Code, you can ask it to add Fulcrum MCP to your Claude desktop configuration file for you. You still need to provide your API token.


Installing the AI Toolkit

In this section, you upload the AI Toolkit to Claude as a plugin.

  1. Visit the Fulcrum AI Toolkit on GitHub and download the AI Toolkit ZIP file.

  2. In Claude, open Settings, then select Plugins.

  3. Select Add, then select Upload plugin.

  4. Drag the ZIP file into the upload window, then select Upload.

Upload plugin window in Claude settings with the Fulcrum AI Toolkit ZIP file added.

Expected outcome: Fulcrum AI Toolkit appears in your list of plugins.


Testing the connection

Confirm that Claude can reach your organization.

  1. Start a new chat in Claude.

  2. Enter: "How many apps are in my Fulcrum organization?"

Expected outcome: Claude uses Fulcrum MCP to look up your apps and answers with the number.


Installing the AI Toolkit for your Claude organization

Owners of a Claude Team or Enterprise organization can make the AI Toolkit available to every member of that organization.

  1. In Claude, open your Organization settings.

  2. Follow the steps in "Installing the AI Toolkit" from there.


Notes

  • Installing the AI Toolkit for your Claude organization doesn't connect Fulcrum MCP for anyone. Each person connects Fulcrum MCP with their own API token.

  • A plugin uploaded as a ZIP file doesn't update automatically. To get new skills, download the latest ZIP file from GitHub and upload it again.

Did this answer your question?