GigUp Docs

MCP

MCP Use Cases

Common ways to use GigUp MCP with AI agents.

Use MCP when an AI agent should help with GigUp account workflows or GigUp-specific developer work.

Manage Trackers

Ask the agent to inspect existing AI Job Trackers, create new trackers from Upwork search URLs, tune AI match prompts, change thresholds, pause inactive searches, or delete old trackers.

Use GigUp MCP to show my active AI Job Trackers. Then create a new tracker for senior Laravel API jobs with payment-verified clients and a 75% match threshold.

Find Jobs

Ask the agent to search tracked jobs by keyword, tracker, job type, difficulty, client rating, client spend, status, and location filters.

Use GigUp MCP to find fixed-price SaaS jobs from my Laravel tracker where the client has spent at least $10,000 and has a 4.5+ rating.

Track Applications

Ask the agent to update a job's status and save useful application details such as the cover letter text and connects used.

Use GigUp MCP to mark job 991 as applied, save this proposal text, and record that I used 12 connects.

Proposal Workflows

Ask the agent to review templates, create reusable proposal prompts, set the default template, and generate a proposal for a tracked job.

Use GigUp MCP to generate a proposal for job 991 using my default proposal template. Keep it concise and tailored to the client's SaaS requirements.

Choose the Right Docs

Ask the agent which GigUp docs page applies to a task before you start. This works well when you are deciding between dashboard actions through MCP and direct integrations through the REST API.

Which GigUp docs should I read before syncing tracked jobs into another system?

Plan an Integration

Ask the agent to create a plan using GigUp docs, including the relevant permissions, endpoints, tools, and rollout steps.

Use GigUp docs to plan a read-only integration that exports tracked jobs.