How to Use the MCP-API
Using Launchfy’s MCP-API, you can ask AIs like Claude Code or Codex to handle app inquiries within your team and update help pages. Available on the PRO plan.
Feature Overview
| Feature | What you can ask the AI to do |
|---|---|
| Inspect apps | Check the list of apps in the team and supported languages for each app |
| Handle inquiries | List unresolved inquiries, review messages and attached images, and register draft replies that haven’t been sent yet. For safety, the AI cannot send replies directly. The AI creates reply drafts and a person sends them. |
| Documents | Read help pages, terms, etc., and save update proposals for existing pages as unpublished drafts. For safety, the AI cannot update pages directly. The AI creates update proposals and a person publishes them. |
| FAQ | Review categories and FAQs, add or rename categories, and add/edit/delete FAQs. FAQs can be updated directly. Because FAQ entries are often small, direct updates are allowed. |
1. Preparation
Issue an MCP token
- Open Launchfy’s app management screen and choose MCP-API Settings from the team menu.
- Click Issue token for MCP API Token. The token is shown only once on issuance, so store it securely.
- Copy the connection URL shown in the settings. Include the trailing
?teamId=...when copying. Replace the examplehttps://example.com/api/mcp?teamId=YOUR_TEAM_IDbelow with that URL.
When you connect with the token, all apps in the team become accessible. Do not paste the token into AI prompts or shared files. Set it as LAUNCHFY_MCP_TOKEN in the environment where the client runs. If you reissue the token, the old one becomes invalid, so update any connected clients.
Connect with Claude Code
Add the following to the project’s .mcp.json. If mcpServers already exists, add a launchfy entry inside it.
{
"mcpServers": {
"launchfy": {
"type": "http",
"url": "https://example.com/api/mcp?teamId=YOUR_TEAM_ID",
"headers": {
"Authorization": "Bearer ${LAUNCHFY_MCP_TOKEN}"
}
}
}
}
Start Claude Code from a terminal where the environment variable is set and run /mcp to check the launchfy connection. On first use you may be asked to approve the project’s MCP settings—confirm the destination and allow it. Claude Code MCP setup guide
Connect with Codex CLI
Replace the connection URL and run this command in your terminal:
codex mcp add launchfy \
--url 'https://example.com/api/mcp?teamId=YOUR_TEAM_ID' \
--bearer-token-env-var LAUNCHFY_MCP_TOKEN
Verify registration with codex mcp list. To confirm actual connectivity, start Codex from a terminal with the environment variable set and ask, “List the names and IDs of the apps managed in Launchfy.” You can verify the same behavior in Claude Code. Codex MCP setup guide
2. How to Use Each Feature
Review inquiries and prepare replies
First list unresolved inquiries and select one to handle.
In Launchfy, check the 5 most recent unresolved inquiries for “App Name”.
List the inquiry ID, summary, and whether an AI reply draft exists.
Then specify the inquiry ID. Before replying, review the message text and past exchanges, and view attached images if needed.
Review the conversation for inquiry “InquiryID” in “App Name”.
If needed, check attached images and draft a reply in the same language as the inquiry.
Do not state causes or timelines definitively; ask for additional information if necessary.
Show the draft reply here; after I approve it, save it in Launchfy and tell me the confirmation screen URL.
If an AI draft already exists, confirm before overwriting it.
When the AI registers a reply draft, AI Reply Draft appears in the inquiry details. Open the returned URL and click Apply to reply field, then edit the text if needed. The reply is sent to the user when you click Send in the admin screen.
Create document update proposals
The AI can read existing pages and save Markdown update proposals as drafts. After saving, review the draft from the confirmation screen and publish it.
From the help page list for “App Name”, find the page that explains notification settings.
Review the current steps and draft a proposal that adds a section “When notifications do not arrive”.
After I approve, save it as a draft and give me the link to the confirmation screen.
If an existing draft exists, confirm before overwriting it.
Review and update FAQs
Because FAQ additions/edits/deletions are applied directly, it’s safer to review the proposed changes first and then ask to apply them.
Check the FAQ for “App Name” and see if a question about “Notifications not arriving” already exists.
If there’s no duplicate, propose a category to add it under and draft the question and answer.
After I approve, register the FAQ in that category.