# Connect lemlist to Muse Prepare a grounded outreach campaign briefing

> Read campaigns with Muse and Agent200. Prepare a outreach campaign briefing using the connected user’s own lemlist account.

- Page: https://www.agent200.com/connectors/lemlist/framework/muse/
- Connector: [lemlist](https://www.agent200.com/connectors/lemlist.md)
- Framework: Muse
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect lemlist to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/lemlist/framework/muse/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Muse's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure lemlist is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Muse: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Muse's exact menus or commands.
4. The first lemlist request returns an authorization link if the user has not connected lemlist yet: show it to them and continue once they have approved access on lemlist's own page.
5. Check it works with this request: "Read the lemlist campaign I identify and prepare a outreach campaign briefing. Name the source and use only campaign, lead and activity fields. State access gaps; do not change records."
   What should come back:
   - The selected campaign is identified.
   - Only the returned campaign, lead and activity fields are reported.
   - Access gaps and missing context are explicit; no source data is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in lemlist, then retry.

## Overview

Use Muse to prepare a short outreach campaign briefing for review. Put the Agent200 key in Muse’s secure credential interface, then inspect the source before sharing the result.

Start with one identified campaign. Preserve returned campaign, lead and activity fields; report missing data and keep the workflow read-only.

Provider reference: [lemlist API](https://developer.lemlist.com/api-reference/getting-started/overview).

- **Connector:** [lemlist](https://www.agent200.com/connectors/lemlist/)
- **Works with:** Muse · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [5 tools](https://www.agent200.com/connectors/lemlist/framework/muse/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **lemlist enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a lemlist account.** They approve access once, on lemlist's own page.
- **Muse, with custom MCP servers allowed.** Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

## Connect lemlist to Muse

### Step 1: Create your Agent200 API key

Create a key on the [API keys page](https://agent200.com/platform/apikeys/) and store it securely.

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Create the custom connector

Connect to `https://api.agent200.com/mcp/` over Streamable HTTP with an Authorization: Bearer header. Enter the key in Muse’s secure credential interface.

File `Muse chat`:

```text
Create a Custom Connector for the Agent200 remote MCP server and connect to it:
Name: Agent200
Transport: remote streamable HTTP
URL: https://api.agent200.com/mcp/
Auth: API key sent in the Authorization header as "Bearer <key>"
Open the secure credentials store so I can enter the API key there, not in this chat.
Then list its tools to confirm the connection works.
```

### Step 3: Inspect read tools

Confirm the lemlist operations and schemas advertised by the connection.

### Step 4: Authorize lemlist

Connect the intended user and test one accessible campaign.

## Test your connection

Ask: "Read the lemlist campaign I identify and prepare a outreach campaign briefing. Name the source and use only campaign, lead and activity fields. State access gaps; do not change records."

What should come back:

- The selected campaign is identified.
- Only the returned campaign, lead and activity fields are reported.
- Access gaps and missing context are explicit; no source data is changed.

Check the selected campaign ID, account scope, read permission and pagination. Campaign and team scope matter. Do not interpret a paged activity list as every send, open or reply.

## lemlist tools Muse can call

- **List campaigns** (`lemlist_list_campaigns`, read): Find campaigns available to the connected team.
- **Read a campaign** (`lemlist_get_campaign`, read): Retrieve one identified campaign.
- **List campaign leads** (`lemlist_list_campaign_leads`, read): Find leads in the selected campaign.
- **Read a lead** (`lemlist_get_lead`, read): Retrieve one identified campaign lead.
- **List activities** (`lemlist_list_activities`, read): Review recorded outreach activity in scope.

## How it works

1. **You ask Muse.** In your own words, for something in lemlist.
2. **Muse picks a tool.** It sees the lemlist tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own lemlist connection, within the tools and scopes your project allows.
4. **Muse answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's lemlist account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and lemlist enforces what its API grants.

## Troubleshooting

### The source cannot be read

Check the selected campaign ID, account scope, read permission and pagination. Campaign and team scope matter. Do not interpret a paged activity list as every send, open or reply.

## FAQ

### How do I verify this result?

Compare the named campaign and returned campaign, lead and activity fields with the source. Treat missing information as missing, not as a fact.

## Use lemlist with another framework

- [lemlist + Claude](https://www.agent200.com/connectors/lemlist/framework/claude.md)
- [lemlist + ChatGPT](https://www.agent200.com/connectors/lemlist/framework/chatgpt.md)
- [lemlist + Claude Code](https://www.agent200.com/connectors/lemlist/framework/claude-code.md)
- [lemlist + Grok Bot](https://www.agent200.com/connectors/lemlist/framework/grok-bot.md)
- [lemlist + OpenAI Dots](https://www.agent200.com/connectors/lemlist/framework/openai-dots.md)
- [lemlist + Claude Duet](https://www.agent200.com/connectors/lemlist/framework/claude-duet.md)
- [lemlist + Hermes Agent](https://www.agent200.com/connectors/lemlist/framework/hermes-agent.md)
- [lemlist + OpenClaw](https://www.agent200.com/connectors/lemlist/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
