MCP Connector: Full Tool List

Use these tools with the MCP Connector to read and act on your LaunchBay data from Claude, ChatGPT, or any other MCP-compatible AI tool.

The MCP Connector exposes tools across projects, tasks, templates, automations, clients, and forms. The real value shows up when your AI assistant combines several of these in a single request, pulling a project's status, cross-referencing what your team finished in another tool, and drafting a client update, all from one conversation.

👋 We're actively adding more capabilities to this list with our regular updates. Stay up to date by visiting our changelog. If there's a tool that's not on this list you're interested in, send us an email at hello@launchbay.com.

Projects

Tool	Definition	Example usage
`find-project`	Finds one single project by ID, name, status, or tag.	“Pull up the FireSide Media project.”
`find-projects`	Finds multiple projects by name, status, tag, or a list of IDs. Archived and completed projects are excluded by default.	“Show me every active project tagged ‘enterprise.’”
`create-project-from-template`	Creates a new project from a saved template, prefilled with that template’s stages and tasks.	“Create a new project for Acme Corp from the Standard Onboarding template, due in six weeks.”
`get-project-health-score`	Returns a project’s health score (0-100) with a breakdown of activity, task, and client-email-engagement components.	“What’s the health score on the Northwind project, and what’s driving it?”
`get-project-activity`	Returns a project’s recent activity, newest first: task updates, comments, files, form submissions and signatures, project notes, and client touchpoints like portal invites, reminder emails, nudges, and a client’s first portal login.	“Catch me up on the Acme onboarding project before my 2pm call.”
`get-project-decisions`	Returns logged decisions for a project, most recent first, each with who logged it, where it came from, and when.	“What decisions have we logged on the Acme project this month?”
`get-project-files`	Returns the files uploaded to a project, grouped by the task they’re attached to.	“Pull every file the client has uploaded to the Riverside Media project.”
`get-project-notes`	Returns the notes logged on a project, most recently updated first.	“What notes do we have on the Northwind project?”
`create-or-update-project-note`	Creates a new project note or updates an existing one.	“Add a note to the Acme project: kickoff call moved to Thursday.”
`update-project-tags`	Adds or removes tags on a project by name.	“Tag the Riverside Media project as ‘at risk.’”
`add-user-to-project`	Adds an existing user to a project as a team member or a client, with an optional portal invitation.	“Add jane@acmecorp.com to the Acme project as a client and send her a portal invite.”
`create-stage`	Creates a new stage within a project to group tasks into a logical phase. Can be marked private.	“Add a ‘Go-Live’ stage to the Northwind project.”
`reorder-project`	Reorders the stages in a project or template, or the tasks within a stage. Can also move tasks from one stage to another. Anything you don’t mention keeps its current order.	“In the Acme project, move the Kickoff stage to the top and put ‘Sign Contract’ first in it.”

Tasks

Tool	Definition	Example usage
`find-task`	Finds a single task by ID, name, project, assignee, status, or due date. Returns a full Files section, tagged by source, and a pointer to any attached form.	"Pull up the 'Brand Assets' task for Riverside Media and show me anything the client has uploaded."
`find-tasks`	Finds multiple tasks across projects, with filtering, pagination, and ordering by due date or creation date. Does not return file or form data.	"Show me every overdue task across my active projects, sorted by how long they've been waiting."
`create-task`	Creates a task in a project, with an assignee, due date, stage, and subtasks. Can attach files by URL or a form on creation.	"Create a task on the Acme project: upload the signed MSA, due next Friday, and attach this Google Drive link to it."
`update-task`	Updates an existing task: change its title or description, add or remove subtasks and files, attach proofs or embeds, require a signature, turn on reminders, or switch it between internal and client-facing.	"Add a proof to the Brand Assets task for Acme and turn on reminders."
`update-task-status`	Updates a task's status (active, archived, deleted, completed, in review, draft, incomplete).	"Mark the 'Kickoff Call' task on Acme as completed."
`update-task-due-date`	Sets a task's due date.	"Push the due date on the 'Contract Review' task back to the 15th."
`archive-task`	Archives a task.	"Archive the 'Legacy Migration' task, we're not doing that anymore."
`update-task-tags`	Adds or removes tags on a task by name.	"Tag the 'Data Import' task as 'blocked.'"
`assign-or-remove-client-from-task`	Assigns a client already on the project to a task, or removes them from it.	"Assign the 'Brand Assets' task to Acme's marketing contact."
`read-comments`	Reads all comments on a task.	"What's the latest on the 'API Credentials' task?"
`comment-on-task`	Posts a comment on a task, marked private or client-visible, with @-mentions.	"Comment on the 'Contract Review' task: @Josh, can you confirm this is the final version?"

Templates

Tool	Definition	Example usage
`list-templates`	Lists all saved project templates for the team.	"What project templates do we have set up?"
`find-template`	Shows one template in full: every stage and task, with each task's description, subtasks, form, and settings.	"Walk me through everything in our Enterprise Onboarding template."
`create-template`	Creates a new, empty template that stages and tasks can be added to. Confirms the name with you first.	"Turn this spreadsheet of our onboarding steps into a new LaunchBay template."
`update-template`	Renames a template or changes its description.	"Rename the 'Onboarding v2' template to 'Standard Onboarding.'"
`save-template-stage`	Adds a stage to a template or edits an existing one: its name, whether it's internal, and how many days it's expected to take.	"Add an internal 'QA Review' stage to the Website Build template, expected to take 5 days."
`save-template-task`	Adds a task to a template or edits an existing one: title, description, stage, subtasks, attached form, embed, signature requirement, reminders, internal or client-facing, and how many days after activation it's due.	"Add a client task to the Discovery stage asking them to upload brand assets, due 3 days after it's activated."
`delete-from-template`	Deletes tasks or stages from a template. Warns you first if anything depends on them, like an automation or a blocked task.	"Remove the 'Legacy Data Import' stage from the Standard Onboarding template."

Changes to a template, including its automations, apply to projects created from that template going forward. Projects already in progress aren't affected.

Automations

Tool	Definition	Example usage
`find-automations`	Shows every automation on a project or template in plain language, including triggers, delays, and actions.	“What automations are running on the Acme project?”
`save-automation`	Creates a new automation from a description of the trigger, delay, and actions, or edits an existing one, like renaming it, changing its delay, or swapping an action. Actions include setting the project end date to a number of days after the automation runs.	“When the contract task is completed, wait one day, then activate the invoice task.” or “When the Kickoff stage is completed, set the project end date to 60 days out.”
`delete-automation`	Deletes an automation that’s no longer needed.	“Remove the old welcome email automation from the Onboarding template.”

Automations can be triggered when a task or stage is completed, activated, or archived, when a project is created or completed, when a form question gets a specific answer, or when a task tag is added or removed. They can send an email notification, activate or archive tasks and stages, import tasks or stages from another template, show or hide client portal pages, and add or remove project tags.

Clients

Tool	Definition	Example usage
`find-client`	Finds a client by name or email address.	"Find the client record for jane@acmecorp.com."
`nudge-client`	Sends an AI-drafted reminder email to a client with a magic link into their portal, scoped to a project or specific tasks. Requires your confirmation before sending.	"Find every client with incomplete tasks this week and draft a nudge for each one."
`remind-client-of-task`	Sends a reminder to a client about one specific outstanding task.	"Remind Acme's contact about the 'Upload Brand Assets' task."

Forms

Tool	Definition	Example usage
`build-form`	Builds a new form from a natural-language description of what it should collect. Requires your confirmation of the field list before building.	"Build a client intake form asking for company name, budget range, and project goals."
`get-form-responses`	Returns completed responses for a single form, looked up by ID or name.	"Pull the responses to the Brand Assets form for Riverside Media."
`find-forms`	Finds forms in your account by name or ID.	"What forms do we have set up in LaunchBay?"

Account and meta

Tool	Definition	Example usage
`whoami`	Returns the identity of the currently authenticated user, for resolving "me" and "my" references.	"Who am I logged in as?"
`feedback`	Sends feedback directly to LaunchBay about how to improve MCP Connector responses.	"Send feedback: I wish I could filter tasks by whether they have an attached form."

Meetings

Tool	Definition	Example usage
`find-meeting`	Finds a specific meeting by ID, title, or project.	"Pull the details for the Acme kickoff meeting."
`find-meetings`	Lists meetings across projects, filterable by date range.	"Show me all meetings scheduled this week across active projects."

Using the MCP Connector Alongside Other Tools

The MCP Connector isn't just a way to run LaunchBay from a chat window, it's a bridge between every other tool your business already connects to Claude, ChatGPT, Perplexity, Grok, Cursor, Viktor, or any other MCP-compatible assistant.

If your CRM, project management tool, file storage, or email is also connected over MCP, your AI assistant can push and pull data between LaunchBay and that tool in the same conversation, often without you ever logging into either one.

Because the MCP Connector is prompt-based, the tools above are the building blocks, not the ceiling. There are thousands of ways to combine them, especially alongside the other tools your team already connects via MCP: your CRM, your project management tool, file storage, email or messaging, and everyday tools like Google Docs, Sheets, and Drive.

A few workflows to get you started:

Kick off onboarding the moment a deal closes, without re-typing anything

When a deal moves to closed-won in HubSpot, Salesforce, or whatever CRM you connect over MCP, ask a question about the deal first, the company name, deal value, and any custom fields you need (implementation tier, contract start date). Then, in the same chat, hand it off to create-project-from-template to spin up the matching onboarding project in LaunchBay. Use add-user-to-project to add the right contacts from that company as clients and bring in the team members who'll be working the project, roles and all, so the moment the project exists, everyone who needs access already has it.

"The Acme Co. deal in HubSpot just closed. Pull the company name, deal value, and implementation tier, then create a new project in LaunchBay from the Enterprise Onboarding template. Add Jane and Priya from Example Co. as clients, and add Josh and Maria from our team."

From there, the template's own stages, automations, and dependencies take over exactly like they would if you'd built the project by hand, activating tasks in the right order as each step clears.

Move client files out of LaunchBay and into wherever your team works

find-task returns direct links to every file tied to a task, a client's upload, a file submitted through a form, or a file a teammate attached. Hand those links to whatever tool your team lives in.

"Pull the files the client uploaded on the 'Brand Assets' task for Riverside Media, and add them to our shared Dropbox folder."

Turn form submissions into tasks in the project management tool your team already uses

find-task points to the form attached to a task, and get-form-responses pulls the actual field data. Use that to create and assign tasks directly in Asana, monday.com, or wherever your team tracks internal work, and save a PDF of the completed form to Google Drive for the record.

"Pull the completed intake form for Acme, save it as a PDF to our Drive, and create the matching setup tasks in Asana's Backlog project."

Send project updates without building them by hand

Keeping leaders, managers, and your own team in the loop on project health used to mean digging through several tools, then building an email, a spreadsheet, or a slide deck to actually deliver it. get-project-health-score gives your assistant a real-time read on any active project, so however your team is used to sharing updates, an email, a Slack post, a one-pager, you can have it built and sent in minutes from a single chat instead of an afternoon of pulling data together by hand.

"Every Friday morning, pull the health score for every active project and post a summary to our #onboarding Slack channel."

Know what's changed, even if you weren't on the call

A customer asking for a new integration, additional data they need migrated, or a tweak to how your team is implementing their setup, this kind of change surfaces constantly in meetings, comment threads, and chats. When the Decisions agent is enabled on a project, it flags these the moment they come up. From there, if you've connected the MCP Connector to Claude, ChatGPT, or another AI assistant, ask it things like:

"Check what's been decided on the Northwind project this week, create tasks for anything that isn't already tracked, and add a project note summarizing what changed."

get-project-decisions pulls everything the agent has caught, who decided it, where it came from, and when, so you can create and assign the follow-up work, loop in the right people, and pair it with create-or-update-project-note to keep a running log so handoffs come with the context they need.