Preview before publish
Create drafts first. Read content, schedule, links, and staffing requirements before opening signup.
On this page
G GiGa MCP · Admin tools
Connect as an admin.
Run gig operations.
Add the same GiGa MCP endpoint used by every account, sign in as an admin, and receive the operations tools available to you.
Browser sign-in Account-scoped tools Human-reviewed actions
One connection
Your signed-in account selects the tools
Workers and admins add the same endpoint and use the same browser sign-in flow.
Worker account
Manage your GiGa journey
Complete your profile, discover gigs, manage applications, and handle referrals.
Open Worker docs AdminAdmin accountCreate and manage gigs
Draft opportunities, add sessions and shifts, set schedules, and open signup.
See the gig workflow Admin accountHire and staff workers
Review applications, hire workers, assign shifts, and check staffing coverage.
See the hiring workflowAdmin connection
Connect the GiGa MCP and sign in
Add the GiGa endpoint to your client. The browser opens so you can sign in with your Company or platform admin account.
1
Add GiGa MCP
Paste the endpoint into your client’s remote MCP or connector settings.
2
Sign in as an admin
Approve the Company-scoped or platform permissions shown for your GiGa account.
3
Start with a read
Try “List the latest draft gigs” before asking GiGa to create or change anything.
mcp.json
{
"mcpServers": {
"giga": {
"url": "https://api.giga.jobs/mcp"
}
}
}Production endpoint
https://api.giga.jobs/mcpStarter prompt
“Using GiGa, list the latest draft gigs. Do not modify or publish anything.”
Automation keys are optional
For unattended automation, create a managed Company or SuperAdmin key and store it in the client’s secret manager. Interactive connections should use browser sign-in.
Create & manage gigs
Draft first. Build the schedule. Review. Publish.
A gig belongs to a brand and program. Shared event details live on sessions; role-specific headcount lives on shifts.
Recommended sequence
1. brand_list → program_list → role_list → venue_list
2. gig_create (always start as draft)
3. gig_session_create for each shared occurrence
4. shift_create for each role requirement
5. gig_asset_upload → gig_read → gig_links
6. Human review, then gig_open_signup01Resolve IDsReuse existing setup resources whenever possible.02Create a draftKeep the public lifecycle closed while building.03Model the scheduleCreate one shared occurrence, then its role shifts.04Open deliberatelyPreview content and get human approval before signup.Manage existing gigs
Use gig_list → gig_read → a typed gig_update → gig_read. Avoid raw fields updates unless an approved integration requires them.
Manage applications
Make staffing decisions reviewable
Read the exact application and selected shifts before recording an outcome. Hiring and rejection are production actions, not drafting steps.
Review-and-hire sequence
1. application_list({ gigId, status: "applied" })
2. application_read({ applicantId })
3. Review worker, role, and selected shifts
4. Human approves the outcome
5. application_update({ applicantId, status: "hired" })
6. staffing_board_read({ gigId })01Filter the queueStart from one gig and one application state.02Inspect the recordVerify worker, gig, role, and selected shifts.03Confirm with a humanAsk immediately before hire or reject.04Read backVerify the application and staffing board after mutation.Hiring has immediate side effects
A first hire ensures a worker conversation and sends the “You’re Chosen” notification. Do not blindly retry if the first response outcome is unknown.
Admin MCP reference
Tools for gigs, schedules, hiring, and staffing
Use these tools to create and update gigs, build schedules, review applications, hire workers, and manage staffing.
25 admin tools4 capability groups1 GiGa MCP endpoint
Find setup resources
Resolve the brand, program, role, and venue IDs used when creating a gig and its shifts.
brand_listList brands
Find the brandId needed by program and gig creation.
Example input
{ "limit": 50, "offset": 0 }program_listList programs
List programs with brand, gig, and role summaries.
Example input
{ "brandId": 28, "includeStats": true }role_listList roles
venue_listList venues
Find reusable venues by name or city before scheduling.
Example input
{ "search": "Convention Center", "city": "Austin" }Create & manage gigs
Create drafts, inspect and update gig content, manage artwork and links, then deliberately open applications.
gig_listList gigs
List gigs with optional lifecycle-status filtering and pagination.
Example input
{ "status": "staffing", "limit": 20, "offset": 0 }gig_readRead a gig
Read a gig with its program, brand, schedule, and staffing details.
Example input
{ "gigId": 184 }gig_createCreate a draft gigWrites production data
Create a program-scoped gig. Dates, roles, and staffing requirements belong on shifts.
Example input
{ "title": "Summer product launch", "brandId": 28, "programId": 9, "city": "Austin", "state": "TX", "timezone": "America/Chicago" }gig_linksGet gig links
Return canonical worker signup, admin review, edit, and graphics-preview URLs.
Example input
{ "gigId": 184 }gig_updateUpdate a gigNotifies workers
Update typed gig content and lifecycle fields. Status changes use guarded transitions and can notify workers.
Example input
{ "gigId": 184, "title": "Summer launch — Austin", "description": "Represent the brand at a live activation." }gig_asset_uploadUpload gig artworkWrites production data
Persist a logo or banner and attach it to the gig.
Example input
{ "gigId": 184, "assetKind": "banner", "sourceUrl": "https://assets.example.com/launch-banner.jpg" }gig_open_signupOpen worker signupNotifies workers
Transition a reviewed gig to staffing and return its public signup URL.
Example input
{ "gigId": 184 }Sessions & shifts
Model each shared occurrence once, then add role-specific staffing requirements with shifts.
gig_session_listList gig sessions
List each shared training, event, setup, or other occurrence once.
Example input
{ "gigId": 184 }gig_session_createCreate a shared sessionWrites production data
Create a dated occurrence whose details can be inherited by multiple role shifts.
Example input
{ "gigId": 184, "sessionType": "event", "title": "Event day 1", "date": "2026-09-18", "startTime": "10:00", "endTime": "18:00", "venueId": 31 }gig_session_updateUpdate a shared sessionWrites production data
Update a shared occurrence; linked shifts inherit its schedule and venue changes.
Example input
{ "gigId": 184, "sessionId": 72, "startTime": "09:30" }shift_listList shifts
List role-specific staffing requirements with role and venue data.
Example input
{ "gigId": 184 }shift_readRead a shift
Read one shift with its gig, role, session, and venue details.
Example input
{ "shiftId": 901 }shift_createCreate a staffing shiftWrites production data
Create a role-specific headcount requirement, preferably attached to a shared session.
Example input
{ "gigId": 184, "roleId": 4, "sessionId": 72, "requiredStaff": 8 }shift_updateUpdate a shiftWrites production data
Update the role, schedule, headcount, venue, pay override, or notes for a shift.
Example input
{ "shiftId": 901, "requiredStaff": 10 }Applications & staffing
Review applications, make outcomes explicit, place workers into shifts, and verify the resulting staffing board.
application_listList applications
List a gig’s applications with worker, role, selected shifts, and contract state.
Example input
{ "gigId": 184, "status": "applied", "limit": 50, "offset": 0 }application_readRead an application
Read one application with its worker, gig, selected shifts, and contract state.
Example input
{ "applicantId": 512 }application_updateUpdate an applicationNotifies workers
Set an application outcome, preferred role, apply mode, or selected shifts.
Example input
{ "applicantId": 512, "status": "hired", "primaryRoleId": 4 }staffing_board_readRead the staffing board
Read role boards, shifts, applicants, roster placement, and contract state.
Example input
{ "gigId": 184 }staffing_assign_applicantAssign an applicantWrites production data
Place an applicant into a shift, acknowledging active contract changes when required.
Example input
{ "gigId": 184, "shiftId": 901, "applicantId": 512 }staffing_unassign_applicantUnassign an applicantWrites production data
Remove an applicant from a shift, acknowledging active contract changes when required.
Example input
{ "gigId": 184, "shiftId": 901, "applicantId": 512, "acknowledgeContractChange": true }gig_statsRead gig staffing stats
Read seats, staffing coverage, applications, and contract counts for a gig.
Example input
{ "gigId": 184 }Operational safety
Keep a human at consequential boundaries
Confirm outcomes
Get explicit human approval immediately before publishing, hiring, rejecting, assigning, or unassigning.
Protect worker data
Application records contain personal data. Do not send them to unapproved models, logs, or analytics systems.
Before an important action
- Read the gig or application first
- Confirm before publishing, hiring, rejecting, assigning, or unassigning
- Read the result before retrying a change
For agents & tooling
Portable admin guidance
MD
Admin Markdown docs
Quickstart, gig and application workflows, safety rules, and the focused tool catalog.
Open Markdown WorkerWorker tool reference
Manage profiles, discover gigs, handle applications, and use referrals through the same endpoint.
Open Worker API GRequest support
Get help connecting an admin client or building a gig and hiring workflow.
Contact supportReady to automate?
Start with a draft.
Connect the GiGa MCP, sign in as an admin, test a read, and build your gig workflow.