@launchpath-ai/mcp-server 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +94 -0
- package/build/client.d.ts +38 -0
- package/build/client.js +210 -0
- package/build/client.js.map +1 -0
- package/build/index.d.ts +12 -0
- package/build/index.js +374 -0
- package/build/index.js.map +1 -0
- package/build/tools/agents.d.ts +6 -0
- package/build/tools/agents.js +249 -0
- package/build/tools/agents.js.map +1 -0
- package/build/tools/analytics.d.ts +7 -0
- package/build/tools/analytics.js +282 -0
- package/build/tools/analytics.js.map +1 -0
- package/build/tools/campaigns.d.ts +6 -0
- package/build/tools/campaigns.js +158 -0
- package/build/tools/campaigns.js.map +1 -0
- package/build/tools/channels.d.ts +7 -0
- package/build/tools/channels.js +319 -0
- package/build/tools/channels.js.map +1 -0
- package/build/tools/clients.d.ts +6 -0
- package/build/tools/clients.js +138 -0
- package/build/tools/clients.js.map +1 -0
- package/build/tools/composio.d.ts +6 -0
- package/build/tools/composio.js +188 -0
- package/build/tools/composio.js.map +1 -0
- package/build/tools/core.d.ts +6 -0
- package/build/tools/core.js +130 -0
- package/build/tools/core.js.map +1 -0
- package/build/tools/integrations.d.ts +6 -0
- package/build/tools/integrations.js +188 -0
- package/build/tools/integrations.js.map +1 -0
- package/build/tools/knowledge.d.ts +7 -0
- package/build/tools/knowledge.js +274 -0
- package/build/tools/knowledge.js.map +1 -0
- package/build/tools/portal.d.ts +6 -0
- package/build/tools/portal.js +86 -0
- package/build/tools/portal.js.map +1 -0
- package/build/tools/tools-config.d.ts +6 -0
- package/build/tools/tools-config.js +213 -0
- package/build/tools/tools-config.js.map +1 -0
- package/build/tools/whatsapp.d.ts +7 -0
- package/build/tools/whatsapp.js +399 -0
- package/build/tools/whatsapp.js.map +1 -0
- package/build/types.d.ts +87 -0
- package/build/types.js +3 -0
- package/build/types.js.map +1 -0
- package/package.json +44 -0
- package/plugin.json +28 -0
- package/skills/agent-report/SKILL.md +44 -0
- package/skills/deploy-agent/SKILL.md +74 -0
- package/skills/launchpath-guide/SKILL.md +60 -0
- package/skills/setup-client/SKILL.md +44 -0
- package/skills/whatsapp-campaign/SKILL.md +72 -0
|
@@ -0,0 +1,74 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: deploy-agent
|
|
3
|
+
description: Create, train, and deploy an AI agent for a client's business. Scrapes their website, builds a knowledge base, tests it, and deploys to widget, WhatsApp, or API.
|
|
4
|
+
argument-hint: [business description or website URL]
|
|
5
|
+
allowed-tools: mcp__launchpath__*
|
|
6
|
+
context: fork
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
You are deploying an AI agent using LaunchPath. Follow this workflow precisely:
|
|
10
|
+
|
|
11
|
+
## Step 1: Parse the user's input
|
|
12
|
+
|
|
13
|
+
- If they gave a **website URL**, you'll scrape it for knowledge
|
|
14
|
+
- If they **described a business**, use that as context for agent generation
|
|
15
|
+
- If both, use both
|
|
16
|
+
|
|
17
|
+
## Step 2: Create the agent
|
|
18
|
+
|
|
19
|
+
Use `create_agent_from_prompt` with a detailed prompt that includes:
|
|
20
|
+
- The business type and industry
|
|
21
|
+
- What the agent should help with (support, sales, scheduling, etc.)
|
|
22
|
+
- Tone and personality guidelines
|
|
23
|
+
- Any specific instructions from the user
|
|
24
|
+
|
|
25
|
+
If the user provided a website URL, pass it as `website_url` so the AI can use it for context.
|
|
26
|
+
|
|
27
|
+
## Step 3: Add knowledge
|
|
28
|
+
|
|
29
|
+
- If a website URL was provided, call `discover_pages` to find all pages on the domain
|
|
30
|
+
- Then call `scrape_website` for each relevant page (prioritize: about, services, pricing, FAQ, contact)
|
|
31
|
+
- Generate relevant FAQs based on the scraped content and call `add_faq` for each one
|
|
32
|
+
|
|
33
|
+
## Step 4: Test
|
|
34
|
+
|
|
35
|
+
- Call `chat_with_agent` with 2-3 test questions relevant to the business
|
|
36
|
+
- Verify the agent responds accurately using the scraped knowledge
|
|
37
|
+
- If responses are poor, add more knowledge or FAQs and re-test
|
|
38
|
+
|
|
39
|
+
## Step 5: Ask about deployment
|
|
40
|
+
|
|
41
|
+
Ask the user which channel they want to deploy to:
|
|
42
|
+
|
|
43
|
+
### Option A: Website Widget (default)
|
|
44
|
+
1. Call `deploy_channel` with `channel_type: "widget"`
|
|
45
|
+
2. Call `set_widget_appearance` to customize colors, theme, avatar, and position
|
|
46
|
+
3. Call `set_widget_content` to set welcome message, conversation starters, and pre-chat form
|
|
47
|
+
4. Call `get_embed_code` to get the ready-to-paste HTML snippet
|
|
48
|
+
|
|
49
|
+
### Option B: WhatsApp
|
|
50
|
+
Tell the user: "For WhatsApp, we need to set up a campaign. Let me walk you through it."
|
|
51
|
+
Then follow the WhatsApp campaign flow:
|
|
52
|
+
1. Create a client if one doesn't exist: `create_client`
|
|
53
|
+
2. `enable_toolset("campaigns")` then `create_campaign` with `channel_type: "whatsapp"`
|
|
54
|
+
3. Tell the user they must enter Meta credentials in the LaunchPath dashboard before proceeding
|
|
55
|
+
4. Once credentials are saved, use `enable_toolset("whatsapp")` and guide them through templates, contacts, and broadcasts
|
|
56
|
+
|
|
57
|
+
### Option C: API Channel
|
|
58
|
+
1. Call `deploy_channel` with `channel_type: "api"`
|
|
59
|
+
2. The response includes the public chat endpoint URL and bearer token
|
|
60
|
+
3. Explain how to use the API endpoint to build custom integrations
|
|
61
|
+
|
|
62
|
+
### Option D: Skip deployment
|
|
63
|
+
If the user doesn't want to deploy yet, skip this step. Remind them they can deploy later.
|
|
64
|
+
|
|
65
|
+
## Step 6: Present results
|
|
66
|
+
|
|
67
|
+
Summarize what was created:
|
|
68
|
+
- Agent name and what it does
|
|
69
|
+
- Knowledge base contents (pages scraped, FAQs added)
|
|
70
|
+
- Test conversation results
|
|
71
|
+
- Deployment details (embed code, WhatsApp status, or API endpoint)
|
|
72
|
+
- Link to LaunchPath dashboard for further configuration
|
|
73
|
+
|
|
74
|
+
Always confirm the agent name and greeting message with the user before deploying.
|
|
@@ -0,0 +1,60 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: launchpath-guide
|
|
3
|
+
description: Internal guide for using LaunchPath MCP tools to manage AI agents, clients, and deployments.
|
|
4
|
+
user-invocable: false
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# LaunchPath Platform Guide
|
|
8
|
+
|
|
9
|
+
LaunchPath is an AI agent deployment platform. You have access to it via MCP tools prefixed with `mcp__launchpath__`.
|
|
10
|
+
|
|
11
|
+
## What You Can Do
|
|
12
|
+
|
|
13
|
+
- **Create AI agents** from natural language descriptions or blank templates
|
|
14
|
+
- **Train agents** with website content (auto-scraped) and FAQ pairs
|
|
15
|
+
- **Deploy agents** to website widgets, WhatsApp, or API endpoints
|
|
16
|
+
- **Manage clients** — create client accounts and link agents as campaigns
|
|
17
|
+
- **Test agents** via chat to verify quality before going live
|
|
18
|
+
- **Monitor** conversations and analytics
|
|
19
|
+
|
|
20
|
+
## Common Workflows
|
|
21
|
+
|
|
22
|
+
### Build an agent for a new client
|
|
23
|
+
1. `create_agent_from_prompt` — describe what the agent should do
|
|
24
|
+
2. `discover_pages` → `scrape_website` — add the client's website content
|
|
25
|
+
3. `add_faq` — add common questions and answers
|
|
26
|
+
4. `create_client` — create the client account
|
|
27
|
+
5. `create_campaign` — link the agent to the client
|
|
28
|
+
6. `deploy_channel` — create a website widget
|
|
29
|
+
7. `get_embed_code` — get the HTML to paste on their site
|
|
30
|
+
8. `chat_with_agent` — test it works correctly
|
|
31
|
+
|
|
32
|
+
### Update an existing agent
|
|
33
|
+
1. `list_agents` — find the agent
|
|
34
|
+
2. `get_agent` — read current config
|
|
35
|
+
3. `update_agent` — change prompt, greeting, model, etc.
|
|
36
|
+
4. `chat_with_agent` — test the changes
|
|
37
|
+
|
|
38
|
+
### Check on your business
|
|
39
|
+
1. `list_agents` — see all agents and their status
|
|
40
|
+
2. `list_clients` — see all clients
|
|
41
|
+
3. Enable analytics toolset, then `list_conversations` — check recent activity
|
|
42
|
+
|
|
43
|
+
## Tips
|
|
44
|
+
|
|
45
|
+
- Always scrape the client's website before going live — it dramatically improves agent quality
|
|
46
|
+
- Use `chat_with_agent` to test after every change
|
|
47
|
+
- Deploy as widget first — it's the fastest path to a working agent
|
|
48
|
+
- Create the client and campaign before deploying so conversations are properly tracked
|
|
49
|
+
- Use `discover_pages` before `scrape_website` for comprehensive coverage
|
|
50
|
+
- The default model (openai/gpt-4o-mini) is the most cost-effective. Upgrade to claude-sonnet for higher quality.
|
|
51
|
+
|
|
52
|
+
## Available Toolsets
|
|
53
|
+
|
|
54
|
+
Default (always loaded): agent management, knowledge, deployment, clients
|
|
55
|
+
On-demand (use `enable_toolset`):
|
|
56
|
+
- **campaigns** — link agents to clients
|
|
57
|
+
- **whatsapp** — templates, broadcasts, contacts, sequences
|
|
58
|
+
- **analytics** — metrics, conversation history
|
|
59
|
+
- **tools-config** — webhooks, APIs, Composio integrations
|
|
60
|
+
- **portal** — client portal invites and branding
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: setup-client
|
|
3
|
+
description: Create a client account on LaunchPath, link an existing agent as a campaign, and generate deployment details.
|
|
4
|
+
argument-hint: [client name]
|
|
5
|
+
allowed-tools: mcp__launchpath__*
|
|
6
|
+
context: fork
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
You are setting up a new client on LaunchPath. Follow this workflow:
|
|
10
|
+
|
|
11
|
+
## Step 1: Gather information
|
|
12
|
+
|
|
13
|
+
Ask the user for:
|
|
14
|
+
- **Client name** (required)
|
|
15
|
+
- **Client email** (optional)
|
|
16
|
+
- **Client website** (optional)
|
|
17
|
+
- **Which agent to assign** — show the list from `list_agents` and let them pick
|
|
18
|
+
|
|
19
|
+
## Step 2: Create the client
|
|
20
|
+
|
|
21
|
+
Call `create_client` with the provided details.
|
|
22
|
+
|
|
23
|
+
## Step 3: Create the campaign
|
|
24
|
+
|
|
25
|
+
Call `create_campaign` linking the chosen agent to the new client. Use a descriptive name like "[Client Name] - [Agent Name]".
|
|
26
|
+
|
|
27
|
+
## Step 4: Deploy
|
|
28
|
+
|
|
29
|
+
Call `deploy_channel` on the agent with `channel_type: "widget"` to create a website widget.
|
|
30
|
+
Call `get_embed_code` to get the HTML snippet.
|
|
31
|
+
|
|
32
|
+
## Step 5: Optional portal access
|
|
33
|
+
|
|
34
|
+
Ask if they want to invite the client to the portal:
|
|
35
|
+
- If yes, call `enable_toolset("portal")` first, then `invite_client_member` with the client's email
|
|
36
|
+
|
|
37
|
+
## Step 6: Present results
|
|
38
|
+
|
|
39
|
+
Summarize:
|
|
40
|
+
- Client created with ID
|
|
41
|
+
- Campaign linked (agent → client)
|
|
42
|
+
- Embed code ready to paste
|
|
43
|
+
- Portal invite status
|
|
44
|
+
- Next steps (customize widget, add more knowledge, etc.)
|
|
@@ -0,0 +1,72 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: whatsapp-campaign
|
|
3
|
+
description: Set up a complete WhatsApp campaign — create templates, import contacts, and launch broadcasts or drip sequences.
|
|
4
|
+
argument-hint: [campaign name or description]
|
|
5
|
+
allowed-tools: mcp__launchpath__*
|
|
6
|
+
context: fork
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
You are setting up a WhatsApp campaign using LaunchPath. Follow this workflow:
|
|
10
|
+
|
|
11
|
+
## Step 1: Load required toolsets
|
|
12
|
+
|
|
13
|
+
Call `enable_toolset("campaigns")` and `enable_toolset("whatsapp")`.
|
|
14
|
+
|
|
15
|
+
## Step 2: Find or create the campaign
|
|
16
|
+
|
|
17
|
+
- Call `list_campaigns` to check if a WhatsApp campaign already exists
|
|
18
|
+
- If not, ask the user which agent and client to use (call `list_agents` and `list_clients` to help)
|
|
19
|
+
- Call `create_campaign` with `channel_type: "whatsapp"` to create the campaign
|
|
20
|
+
|
|
21
|
+
## Step 3: Check WhatsApp credentials
|
|
22
|
+
|
|
23
|
+
The response from create_campaign will indicate if Meta credentials are needed. If so:
|
|
24
|
+
- Tell the user: "You need to enter your Meta Business credentials in the LaunchPath dashboard before we can proceed."
|
|
25
|
+
- Provide the direct link to the campaign settings page
|
|
26
|
+
- Wait for the user to confirm credentials are saved before continuing
|
|
27
|
+
|
|
28
|
+
## Step 4: Create message templates
|
|
29
|
+
|
|
30
|
+
- Ask the user what messages they want to send
|
|
31
|
+
- Call `create_wa_template` for each message template
|
|
32
|
+
- Explain that Meta must approve templates (1-24 hours) before they can be sent
|
|
33
|
+
- Use `list_wa_templates` to check approval status
|
|
34
|
+
|
|
35
|
+
Template tips:
|
|
36
|
+
- Use {{1}}, {{2}} for variables (e.g., "Hi {{1}}, your appointment is on {{2}}")
|
|
37
|
+
- MARKETING category for promotions, UTILITY for transactional, AUTHENTICATION for login codes
|
|
38
|
+
- Template names must be lowercase with underscores only
|
|
39
|
+
|
|
40
|
+
## Step 5: Import contacts
|
|
41
|
+
|
|
42
|
+
- Ask the user for their contact list
|
|
43
|
+
- Call `import_wa_contacts` with the contacts (phone number required, name/email/tags optional)
|
|
44
|
+
- Use tags for segmentation (e.g., "vip", "new-customer")
|
|
45
|
+
|
|
46
|
+
## Step 6: Choose sending strategy
|
|
47
|
+
|
|
48
|
+
Ask the user: "Would you like to send a one-time broadcast or set up a drip sequence?"
|
|
49
|
+
|
|
50
|
+
### Option A: One-time broadcast
|
|
51
|
+
1. Verify templates are approved: `list_wa_templates`
|
|
52
|
+
2. Call `send_wa_broadcast` with:
|
|
53
|
+
- `contact_ids` for specific contacts, OR `audience_filter` to target by tags/status
|
|
54
|
+
- `variable_mapping` to personalize messages (e.g., `{ "1": "name" }`)
|
|
55
|
+
- Optionally `scheduled_for` to schedule for a future time
|
|
56
|
+
|
|
57
|
+
### Option B: Drip sequence
|
|
58
|
+
1. Call `create_wa_sequence` with timed steps:
|
|
59
|
+
- Each step has a `delay_hours` (0 for immediate, 24 for next day, etc.)
|
|
60
|
+
- Use `variable_mapping` per step for personalization
|
|
61
|
+
- Set `stop_on_reply: true` if the sequence should stop when someone replies
|
|
62
|
+
2. Call `activate_wa_sequence` with `status: "active"` to start the sequence
|
|
63
|
+
3. Call `enroll_wa_contacts` with contact IDs or a filter to add contacts
|
|
64
|
+
|
|
65
|
+
## Step 7: Present results
|
|
66
|
+
|
|
67
|
+
Summarize what was set up:
|
|
68
|
+
- Campaign name and linked agent
|
|
69
|
+
- Templates created (and their approval status)
|
|
70
|
+
- Number of contacts imported
|
|
71
|
+
- Broadcast sent or sequence activated
|
|
72
|
+
- Link to dashboard for monitoring
|