A band marketing bot with GigJack’s MCP connector

GigJack’s MCP connector lets an AI app work with your band’s profile, planning, tasks, venues and contacts. Put that connection alongside web research and an email draft tool, and you can configure a marketing bot that researches opportunities, records new relationships in GigJack and prepares messages for you to review.
Here is a practical example: ask a bot to find venues and festivals that fit your band, check which ones are already in your workspace, create follow-up tasks and prepare individual booking emails. The aim is to develop your band’s network and pursue relevant opportunities. The workflow below describes how to configure that process; it does not guarantee replies or bookings.
What MCP connects
MCP stands for Model Context Protocol. It gives a compatible AI app a way to discover and call tools supplied by another application. With GigJack, those tools can read your profile, search your existing venues and contacts, and create or update planning records within the access you approve.
The AI app coordinates the work. GigJack supplies the workspace data and actions. Web searches, email drafts in a mailbox and recurring runs need separate tools or capabilities in the bot’s environment. The GigJack MCP connector does not itself search the web, create mailbox drafts or schedule a marketing campaign.
Start with the band’s profile and a brief
The bot can read your profile’s name, genres, biographies, social links, other links, repertoire information and booking contact. That gives it material for judging a possible match and introducing the band in an email. Profile access is read-only.
Add a brief with the criteria for this search: the region, travel limits, target period, preferred types of show and how many leads you want. Include any commercial requirements yourself: the connector does not expose gig deal finances or booking fees. A date with no gig in GigJack should still be checked with the band before offering it.
For example, imagine a fictional indie-soul band looking for club shows and small festivals within 100 kilometres of Utrecht next spring. The bot reads the band’s biography and links, then uses that brief to research suitable programmes and booking pages.
Research opportunities with a separate search tool
Using its web research tool, the bot checks official venue and festival websites for musical fit, booking instructions, application deadlines and published contact details. Ask it to keep the source URL and the date checked for every lead, and to distinguish an open application from a venue that simply programmes similar music.
The result could be a shortlist with the organisation, location, reason for the match, booking route and next action. If a deadline or contact is unclear, the next action can be to verify it. The bot should leave missing details blank rather than invent a booker’s name or email address.
Check the workspace before adding anyone
Before saving each lead, the bot searches the connected GigJack workspace for the venue and contact. These searches find existing records by name; they do not discover businesses on the web. Ask the bot to try relevant name variations and compare the returned website, city and contact details before deciding whether it has a match.
If the venue exists, the bot reuses it. If the booker already exists as a contact, it reuses that contact too. When only one is missing, it creates only that record. When both are missing, it can create both and link the contact to the venue. It can also record a festival as a festival.
In our example, the band might already have the club in GigJack but not its current booker. The bot adds the verified contact and links it to the existing venue. For a newly discovered festival, it creates the festival record and adds a named contact only if one was verified. Ambiguous matches go back to the user for review; duplicate checking is part of the bot’s instructions, not an automatic merge feature.
Venue and contact notes can hold the research source and relevant booking instructions, giving the band a record of why the lead was added.
Turn a lead into a follow-up task
A prospective booking does not need a gig record yet. GigJack’s MCP tools can create a standalone task with a due date and links to the relevant venue and contacts. A task can also be assigned to a band member when the bot has a verified member ID; assigning it notifies that person.
For the fictional club lead, the task could be Review booking introduction for the club, due in three days and linked to the club and its booker. A task note can contain the source URL, the reason for the match, the application deadline and what still needs checking.
On a later run, instruct the bot to inspect existing tasks and their notes before creating another follow-up. After you send an introduction, it can add a note and update the next task’s due date. Keep the status accurate: a prepared draft is not a sent email, and a sent email is not a confirmed booking.
Prepare individual emails with a mailbox tool
With a separately authorized email tool that supports draft creation, the same bot can save an unsent message in your mailbox. It uses the band’s profile for the introduction and the research for a specific reason to contact that venue. Ask it to include a subject, the verified recipient, a short pitch, relevant listening or live-video links and the band’s booking contact.
Each draft should reflect the recipient’s published booking instructions. The bot should avoid claiming availability, audience figures, previous relationships or achievements that you have not supplied. If the venue uses an application form instead of email, the task should point to that form.
You review the recipient, wording, links and proposed dates before sending. The bot can add the draft reference to the GigJack task note so the follow-up stays connected to the lead. Without a mailbox draft tool, it can prepare the email text in the conversation for you to copy.
Connect the tools and define the routine
The MCP connector is included in Artist Gold, Band Silver and Band Gold. In a compatible AI app, start a remote MCP connection to https://app.gigjack.com/api/mcp, using Streamable HTTP and OAuth. Sign in to GigJack, choose the band’s Workspace and approve the requested access. Client setup depends on the AI app; see the MCP connector guide for the connection steps.
For this workflow, the connection needs View and change planning, and your workspace role must allow the changes. In GigJack, open Settings → Integrations and connectors → MCP connector, expand the application and enable Profile, Tasks, Venues and Contacts under Tool groups. Select Save tools. Enable planning groups too if you want the bot to check recorded gigs, rehearsals or events.
Authorize web research and mailbox access separately in your bot’s environment. If that environment supports scheduled runs, configure the routine there, for example once a week with a limit of five new leads. GigJack connections last up to 30 days. Offline access lets the app renew its access within that period; continuing after expiry needs a new authorization.
A brief you can adapt
Act as our band’s marketing assistant. Read the connected GigJack profile and use the search region and target period I provide. Research up to five relevant venues or festivals using official sources. For each lead, show why it fits, the source URL, the date checked and any verified deadline or booking instructions.
Search our existing venues, contacts, tasks and relevant notes first. Reuse matching records; create only missing venues or contacts with verified details, and link contacts to venues where appropriate. Ask me about ambiguous matches. Create a standalone review task for each new opportunity, linked to its venue and contacts, with a due date and research notes. Avoid repeating existing outreach tasks.
Use the connected email tool to create an individual unsent draft where email is the published booking route. Include our verified profile links and booking contact. Record the draft reference in the task notes. Do not send messages or submit applications. Finish with a report of records and tasks created or reused, drafts prepared, and questions that need my review.
This brief defines the behaviour you want from the bot; it does not add permissions or enforce a technical draft-only restriction. Use the controls available in your AI app and email connection to match that scope. Each GigJack connection stays bound to the workspace you authorized, and you can review its activity or select Disconnect from the MCP connector page.
The result of a run is a reviewable set of researched leads, workspace records, follow-up tasks and email drafts. The band decides which relationships to pursue and which messages to send.