> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linkedcamp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# OpenClaw

> Run LinkedCamp from any chat OpenClaw is on — WhatsApp, Telegram, Slack, Discord or the Control UI — with approval prompts before anything reaches people.

> **[LinkedCamp plugin](https://clawhub.ai/asveloper/plugins/linkedcamp)**
>
> Recommended. The LinkedCamp connection, the skill, and approval prompts.

> **[LinkedCamp skill](https://clawhub.ai/asveloper/skills/linkedcamp)**
>
> The skill on its own. You connect LinkedCamp yourself, and there are no approval prompts.

Both are published on ClawHub and talk to the same hosted server every other client uses:

```text theme={null}
https://mcp.linkedcamp.com/mcp
```

## Plugin or skill?

| | Plugin | Skill only |
| - | - | - |
| Teaches the agent the LinkedCamp workflow | Yes | Yes |
| Connects to LinkedCamp | You sign in once after installing | You add the MCP server yourself |
| Asks before sending, launching or deleting | Yes — OpenClaw approval prompts | No — the conversation is the only check |

Use the plugin unless you have a reason not to.

## Install

Requires OpenClaw **2026.6.1** or newer.

**Plugin (recommended)**

```bash theme={null}
openclaw plugins install clawhub:@asveloper/linkedcamp
```

On OpenClaw main/dev builds with ClawHub as the default source, the `clawhub:` prefix is optional. Stable releases through 2026.10.4 need it.

```bash theme={null}
openclaw plugins install @asveloper/linkedcamp
```

**Skill only**

```bash theme={null}
openclaw skills install @asveloper/linkedcamp
```

The skill does not connect LinkedCamp for you — follow the next step as well.

## Connect your account

**Sign in (recommended)**

```bash theme={null}
openclaw mcp set linkedcamp '{"url":"https://mcp.linkedcamp.com/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login linkedcamp
```

The login prints a link. Open it, paste your API key into the LinkedCamp page, and approve. OpenClaw stores an encrypted token, not your key.

If the Gateway runs on another machine and the browser cannot return to it, finish with:

```bash theme={null}
openclaw mcp login linkedcamp --code <code>
```

In the Control UI, the same flow is **Settings → MCP → linkedcamp → Sign in**.

**API key (headless)**

For a Gateway with no browser, put your key in the Gateway environment, for example `~/.openclaw/.env`:

```bash theme={null}
LINKEDCAMP_API_KEY=your-api-key
```

Then register the server. Keep the single quotes, so the shell leaves the variable for OpenClaw to fill in:

```bash theme={null}
openclaw mcp set linkedcamp '{"url":"https://mcp.linkedcamp.com/mcp","transport":"streamable-http","headers":{"X-Api-Key":"${LINKEDCAMP_API_KEY}"}}'
```

**Teams**

On a shared Gateway, each chat member can sign in to their own LinkedCamp account:

```bash theme={null}
openclaw config set gateway.publicOrigin https://gateway.example.com
openclaw mcp set linkedcamp '{"url":"https://mcp.linkedcamp.com/mcp","transport":"streamable-http","auth":"oauth","oauth":{"identity":"per-requester"}}'
```

Your API key is in [Settings → Integrations → API](https://app.linkedcamp.com/settings/integrations?type=api). See the [quick start](/mcp/quickstart.md#1-get-your-api-key) for plan requirements.

Then check the connection:

```bash theme={null}
openclaw mcp probe linkedcamp
```

and ask the agent: *"Which LinkedCamp account am I connected to?"*

> [!WARNING]
>
> Never paste your API key into a chat. The agent is told not to ask for it; if a key does end up in a conversation, rotate it in Settings → Integrations.

## Approval prompts

With the plugin installed, the agent asks you to **allow once** or **deny** before it:

* **Reaches people** — launching or resuming a campaign, sending a message or test email, scheduling or publishing a LinkedIn post, changing posting slots, turning on an automation.
* **Changes live outreach** — a campaign's audience, saving or editing a sequence, attaching an agent, editing an active agent, knowledge-base entry or persona, overwriting templates, saved replies or notes, skipping a scheduled step.
* **Removes data** — deleting campaigns, leads, messages, agents, knowledge, personas, tags, blacklist rules, merge fields, blocked dates or reminders, and blacklisting a lead.

Reading data, building a draft campaign, adding leads, private draft posts, and inactive agents or automations go through without a prompt. Approve in the Control UI, with `/approve`, or in the chat the request was routed to.

> [!NOTE]
>
> With the skill alone there are no approval prompts. The agent is instructed to confirm in the conversation, but nothing enforces it.

### Plugin settings

Set under `plugins.entries.linkedcamp.config`:

| Setting | Default | What it does |
| - | - | - |
| `requireApproval` | `true` | Set `false` to turn approval prompts off. Not recommended. |
| `serverName` | `"linkedcamp"` | Change only if you connected LinkedCamp under another name. |

### Hide tools entirely

To take tools away from the agent instead of approving them one by one:

```bash theme={null}
openclaw mcp tools linkedcamp --exclude 'message_send,campaign_launch,*_delete,lead_blacklist'
```

## What you can do

The agent reaches the [full tool surface](/mcp/overview.md#tool-groups) your plan and permissions allow. Tools appear in OpenClaw as `linkedcamp__<tool>` — for example `linkedcamp__whoami` or `linkedcamp__campaign_list`.

* Campaigns: build, generate LinkedIn and Sales Navigator audience searches, author multi-step sequences, launch after confirmation
* Leads, notes, tags and blacklists
* The unified inbox and reply drafts
* AI reply agents and knowledge bases
* LinkedIn post scheduling
* Campaign, account and funnel analytics, including [agency sub-accounts](/mcp/agencies.md)

Try:

* *"Show me my LinkedCamp account and unread inbox counts."*
* *"Build a draft campaign for heads of customer support at B2B SaaS companies. Show me the audience and the sequence before anything sends."*
* *"Summarize my campaign performance for the last 30 days."*
* *"Find my unread conversations, prioritize interested prospects and draft a reply for each. Don't send anything."*

## What it will not do

* Connect a LinkedIn account — that takes your LinkedIn password, so do it in LinkedCamp
* CRM integrations, billing, team management or API-key changes

The agent will never ask for a LinkedIn password, session cookie or verification code.

## Versions

The current release of both the plugin and the skill is **1.0.4**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.