Agent Plugin

Sitefire’s agent plugin lets AI assistants access your action pipeline directly inside the conversation. Browse your tracked topics, create actions, read briefings, and work with generated articles — without switching tabs.

The plugin includes an MCP server for data access, product knowledge so your agent understands Sitefire’s domain model, and slash commands for common workflows like reviewing actions and triggering article generation.

MCP Server URL: https://app.sitefire.ai/api/mcp

Getting Started

Coding Agents

Install the full plugin (MCP server + product knowledge + slash commands) with a single command:

npx skills add sitefire-ai/skills

This works with Claude Code, Codex, Cursor, Gemini CLI, and any agent that supports the Agent Skills spec.

On first use, a browser window opens where you sign in to your Sitefire account and approve access.

What’s included

Claude Code on the web

If you use Claude Code on the web with Remote Control, the plugin installs on your local machine and works automatically through the web interface.

If you use Claude Code on the web without Remote Control, add the MCP server URL manually in your session settings. You can also upload the skills individually — see the Claude.ai tab for instructions.

Claude.ai

Setting up Sitefire on claude.ai has two parts: a connector that gives Claude access to your data, and skills that teach Claude how Sitefire works and add workflow commands.

1. Add the connector

1. Open claude.ai
2. Click Customize in the bottom-left, then click Connectors +
3. Click Add custom connector
4. Enter a name (e.g. “Sitefire”) and the server URL: https://app.sitefire.ai/api/mcp
5. Click Add
6. Click Connect to authorize Claude to access your Sitefire account

2. Add the skills

The skills give Claude context about Sitefire’s domain model — what actions, briefings, and articles are and how they work. They also add commands like /sitefire-discover that make common workflows easy to trigger.

1. Download the 4 skill files from the sitefire-ai/skills repository.
2. Go to Customize > Skills
3. Click + > Create skill > Upload a skill
4. Drag and drop each of the 4 files

The connector alone works — Claude can call Sitefire’s API without the skills. But the skills make the experience significantly better: Claude understands Sitefire’s terminology, knows the right workflow for each situation, and offers the slash commands.

Claude Desktop

Claude Desktop supports installing the full plugin (MCP server + skills) from a .zip file or folder.

Option A: Install the plugin (recommended)

1. Download the Sitefire plugin (.zip)
2. Open Claude Desktop and go to Settings > Plugins
3. Drag the .zip file (or unzipped folder) into the plugin area
4. Restart Claude Desktop

This installs the MCP server, product knowledge, and all slash commands at once.

Option B: Add the MCP server manually

If you only want the data connection without the skills:

1. Open Claude Desktop and go to Settings (gear icon or Cmd+, on Mac)
2. Navigate to Developer > Edit Config
3. Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "Sitefire": {
      "url": "https://app.sitefire.ai/api/mcp"
    }
  }
}

4. Restart Claude Desktop

Other clients

Any AI client that supports remote MCP servers can connect to sitefire. Use the following URL:

https://app.sitefire.ai/api/mcp

Most clients accept a JSON configuration like this:

{
  "mcpServers": {
    "Sitefire": {
      "url": "https://app.sitefire.ai/api/mcp"
    }
  }
}

Check your client’s documentation for where to add MCP server configurations.

Authentication uses your existing Sitefire account. When you connect for the first time, a browser window opens where you sign in and approve access. The AI assistant only sees data belonging to your company — the same data you see in the Sitefire dashboard.

How It Works

Sitefire’s action pipeline follows a simple flow:

Topics are the keywords you track (e.g. “crm software”, “email marketing tools”). When you want to improve your visibility for a topic, you create an action. Sitefire diagnoses the situation, produces a briefing with a concrete plan, and for content-related actions, can generate a full article.

Topic → Create Action → Diagnosis → Briefing → Article (optional)

Action types: Create new content, improve an existing page, pursue editorial coverage, or engage in forums (Reddit, Q&A sites). You can pick a type or let Sitefire’s AI choose the best one.

What You Can Do

Every query is scoped to your company. The AI assistant cannot see or modify data from other Sitefire accounts.

Example Workflows

Find topics and create actions

You want to find topics that don’t have actions yet and kick off the diagnosis workflow.

What to say:

Show me my Sitefire topics related to “email marketing”. For any that don’t have an action yet, create one and let Sitefire decide the best action type.

The assistant searches your topics, checks which ones already have actions, and creates new actions for the rest. Sitefire’s AI diagnoses each topic and picks the best approach - create new content, improve an existing page, pursue editorial coverage, or engage in forums.

Follow up with:

Check the progress on those actions. Which ones have briefings ready?

The assistant checks each action’s status and tells you which diagnoses are complete and which briefings you can read.

Turn a briefing into content

Once an action’s diagnosis is complete and the briefing is ready, you can use the AI assistant to produce the actual content.

For new content:

Get the briefing for my “best CRM software” action. Use it to write a full article draft following the recommended angle and structure.

The assistant reads the briefing - competitive landscape, recommended content angle, talking points - and writes a complete article draft based on it.

For improving existing content:

Get the briefing for my “sales automation” action. Here’s my current page [paste content]. Apply the recommended changes.

The assistant reads the briefing’s improvement recommendations and applies them to your existing content, focusing on the changes that matter most for AI visibility.

Tips

• Search topics first. Ask the assistant to search your topics before creating actions. Topic names need to match what Sitefire tracks.
• Check back on actions. Creating an action starts a diagnosis that takes a minute or two. Ask the assistant to check the action status to see when the briefing is ready.
• Combine with other tools. The assistant can use Sitefire briefings alongside web search, Google Docs, or other tools. Ask it to draft an article from a briefing, or apply improvement recommendations to content you paste in.