Connect Muse · custom connector
Connect Muse to Linkedcamp
Last updated:
Ask Meta's Muse to create a custom connector for Linkedcamp's MCP server, sign in, and run outreach by asking Muse.
Muse · LinkedcampSummarise last week's campaign results and suggest one change.
I'll pull last week's numbers for each active campaign, then compare them.
Read-only calls run straight away. Launches and sends ask first.
Setup
How do I connect Muse to Linkedcamp?
To connect Muse to Linkedcamp, ask Muse to create a custom connector for Linkedcamp's MCP server at https://mcp.linkedcamp.com/mcp and follow its sign-in steps. Muse keeps the connection details in its Secure Credentials Store, and you can disconnect any time in Settings → Connectors.
What you need
- A paid Linkedcamp plan and your Linkedcamp API key from Settings → Integrations → API.
- Meta's Muse assistant.
- 01
Ask Muse
In Muse, say: Create a custom connector for Linkedcamp. The MCP server URL is https://mcp.linkedcamp.com/mcp. - 02
Sign in
Follow Muse's prompts to sign in. Muse stores the details in its Secure Credentials Store. - 03
Test it
Ask Muse to test the connection: "List my Linkedcamp campaigns." - 04
Set approvals
Check approvals in Muse Settings so Muse asks before actions you want to approve.
Meta doesn't review custom connectors. Linkedcamp's own safeguards still apply: destructive actions ask first, and you choose the access level when you sign in.
How do I disconnect Muse?
Disconnect Linkedcamp in Muse under Settings → Connectors. Rotating your Linkedcamp API key also disconnects it.
What should I ask Muse?
Start with a read-only question so you can see what Muse reads, then ask for a summary or a draft.
List my active campaigns with acceptance and reply rates for the last 30 days.
Show unread replies across my campaigns and draft a reply to the three most recent positive ones. Don't send.
Check the health of my LinkedIn sending accounts: anything paused, invalid or at its weekly limit?
Give me this week's trend for invites sent, accepted and replies.
Safety
Safety and approvals
- Destructive tools (28 of 133) always ask for your confirmation first. Sending a message is a destructive tool: your assistant must ask, and you must confirm, every time.
- You choose the access level when you sign in on Linkedcamp's page: Read only (64 tools), Read and write (105) or Full access (133, pre-selected).
- Never available over MCP: billing, agency admin and impersonation, white-label settings, team invites and roles, stored credentials, connecting a LinkedIn account or entering PINs, CRM setup and API key rotation.
Troubleshooting
If Muse and Linkedcamp don't connect
| Symptom | Fix |
|---|---|
| 401 or "unauthorized" | Copy the API key again from Settings → Integrations → API and reconnect. If the key was rotated, every client must reconnect. |
| 403 or "outside scope" | You signed in with Read only or Read and write. Reconnect and pick a wider access level. |
| Campaign won't launch | Ask the assistant to check the campaign's readiness (campaign_get returns _readiness) and fix what it lists. |
| AI step fails | The workspace needs an AI provider key (OpenAI, Anthropic, Gemini, Grok or DeepSeek) in Linkedcamp settings. |
| Campaign active but nothing sends | Ask the assistant to check the LinkedIn account (linkedin_account_get: isValid, isPaused, weeklyLimitReached). |
| A step type is refused | Some steps are plan-gated. Ask the assistant to run whoami and read _derived. |
| Tools don't appear | Start a new chat after connecting, and confirm the connector is enabled for that chat. |
FAQ
Muse and Linkedcamp: questions
Other ways to connect
Is Linkedcamp a built-in Muse connector?
Where is my key stored?
Can Muse send messages without asking?
Which Linkedcamp plan do I need?
Run Linkedcamp from Muse.
Start a 14-day free trial, connect Muse, and ask for your first campaign.