Installing the MCP Server

The PromptBits MCP server allows you to access and manage your prompt templates directly from your favorite MCP-enabled clients. This guide will walk you through the installation process for various MCP clients.

What is the Prompt Bits MCP Server?

The Prompt Bits MCP server connects your MCP client to your prompt template library, enabling you to:

• Access your saved prompt templates
• Create and edit prompts
• Use prompts directly in your workflow

Installation

The MCP server is available via npx, so no installation is required. The configuration uses:

npx mcp-remote https://www.promptbits.dev/mcp

Configuration by Client

Choose your MCP client below and follow the configuration instructions:

Cursor

Configuration File Location:

• macOS/Linux: ~/.cursor/mcp.json
• Windows: %USERPROFILE%\.cursor\mcp.json

Configuration:

{
  "mcpServers": {
    "prompt-bits": {
      "type": "stdio",
      "command": "npx",
      "args": ["mcp-remote", "https://www.promptbits.dev/mcp"]
    }
  }
}

After adding the configuration, restart Cursor for the changes to take effect.

Claude Desktop

Configuration File Location:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Configuration:

{
  "mcpServers": {
    "prompt-bits": {
      "type": "stdio",
      "command": "npx",
      "args": ["mcp-remote", "https://www.promptbits.dev/mcp"]
    }
  }
}

Restart Claude Desktop after updating the configuration.

Claude Code

Claude Code offers two installation methods:

Option 1: Using CLI (Recommended)

Run this command in your terminal:

claude mcp add "prompt-bits" npx -a mcp-remote -a https://www.promptbits.dev/mcp

Option 2: Manual Configuration

Configuration File Location:

• ~/.claude.json

Configuration:

{
  "mcpServers": {
    "prompt-bits": {
      "type": "stdio",
      "command": "npx",
      "args": ["mcp-remote", "https://www.promptbits.dev/mcp"]
    }
  }
}

AmpCode

Configuration File Location:

• macOS: ~/.config/amp/settings.json

Configuration:

{
  "mcp": {
    "prompt-bits": {
      "type": "stdio",
      "command": "npx",
      "args": ["mcp-remote", "https://www.promptbits.dev/mcp"]
    }
  }
}

For more information, see the AmpCode manual.

Crush

Configuration File Location:

• ~/.config/crush/crush.json

Configuration:

{
  "$schema": "https://charm.land/crush.json",
  "mcp": {
    "prompt-bits": {
      "type": "stdio",
      "command": "npx",
      "args": ["mcp-remote", "https://www.promptbits.dev/mcp"]
    }
  }
}

Codex

Configuration File Location:

• ~/.codex/config.toml

Configuration:

[mcp_servers.prompt-bits]
command = "npx"
args = ["mcp-remote", "https://www.promptbits.dev/mcp"]

Gemini

Configuration File Location:

• macOS/Linux: ~/.gemini/config.json
• Windows: %USERPROFILE%\.gemini\config.json

Configuration:

{
  "mcpServers": {
    "prompt-bits": {
      "type": "stdio",
      "command": "npx",
      "args": ["mcp-remote", "https://www.promptbits.dev/mcp"]
    }
  }
}

Verifying Installation

After configuring your MCP client:

1. Restart your MCP client to load the new configuration
2. Check for the Prompt Bits server in your client's MCP servers list
3. Test the connection by trying to access your prompts

If you encounter any issues, check your client's logs for error messages related to the MCP server connection.

Next Steps

Once installed, you can:

• Browse your prompt templates
• Create new prompts
• Edit existing prompts
• Use prompts with custom arguments

Visit the Prompts page to start managing your prompt library.