Connect to MCP

Connect PromptBits to an MCP app to use your saved prompts without copying and pasting them.

Create an API Key

1. Click your avatar in the sidebar.
2. Open the API Keys tab.
3. Click Create New Key.
4. Copy the key. It starts with pb_.

Configure Your MCP Client

Add PromptBits to your MCP client with this config. Replace pb_your_api_key_here with the API key you copied.

{
  "mcpServers": {
    "promptbits": {
      "url": "https://www.promptbits.dev/api/mcp",
      "headers": {
        "x-api-key": "pb_your_api_key_here"
      }
    }
  }
}

If your MCP client supports environment variables, you can keep the key out of the config file:

{
  "mcpServers": {
    "promptbits": {
      "url": "https://www.promptbits.dev/api/mcp",
      "headers": {
        "x-api-key": "${env:PROMPTBITS_API_KEY}"
      }
    }
  }
}

Choose Prompts

Only enabled prompts appear in your MCP client. Turn prompts on or off from your PromptBits prompt list.

Prompts appear by name. If a prompt has variables, your MCP client will ask you for those values before using the prompt.

Manage Prompts With Tools

PromptBits also exposes three MCP tools:

• list_prompts returns a lightweight directory of prompt names, ids, descriptions, enabled state, updated time, and argument names.
• get_prompt searches by prompt name or intent. Exact name matches return one full prompt with content; fuzzy matches return up to 10 lightweight summaries.
• put_prompt creates or updates by prompt name. Content or argument changes create a new prompt version.

Your MCP client may ask for confirmation before calling put_prompt because it changes your prompt library.