MCP Examples - GigUp Docs

These examples are prompts you can give to an MCP-compatible agent after connecting it to GigUp with an API token.

Connect an Agent

Use GigUp MCP docs to help me connect this agent to GigUp. Include the endpoint, authentication header, and token safety checklist.

The agent should point you to the cloud endpoint, bearer-token authentication, and the security practices for using a separate token per agent.

Check Account

Use GigUp MCP to check my current team, tracker limit, proposal template limit, and remaining daily alerts.

The agent should use get-account-summary and explain the limits in plain language.

Create Tracker

Use GigUp MCP to create an AI Job Tracker named "Senior Laravel SaaS" for this Upwork search URL: https://www.upwork.com/nx/search/jobs/?q=laravel%20saas&sort=recency. Use a 75% AI match threshold and only match jobs where the client needs API, billing, or backend architecture work.

The agent should check limits, create the tracker, and confirm that background importing has started.

Search Jobs

Use GigUp MCP to find tracked jobs mentioning Stripe or Laravel. Only show fixed-price jobs from clients with at least a 4.5 rating and $10,000 spent.

The agent should use search-tracked-jobs and summarize the best matches with job IDs so you can open or update them.

Update Job Status

Use GigUp MCP to mark job 991 as applied. Save this cover letter text and record 12 connects used.

The agent should use update-tracked-job-status and confirm the status that was saved.

Manage Templates

Use GigUp MCP to create a default proposal template for Laravel backend jobs. Keep proposals short, mention relevant SaaS experience, and ask one smart clarifying question at the end.

The agent should use the proposal-template tools and tell you whether the new template became the default.

Generate Proposal

Use GigUp MCP to generate a proposal for job 991 with my default template. Tailor it to the job requirements and keep it ready to paste into Upwork.

The agent should use generate-job-proposal, then show the generated proposal text.

Choose API or MCP

I want to automate tracked job exports. Use GigUp docs to tell me whether I should use the API or MCP.

The agent should explain that MCP is good for conversational account workflows and docs-aware planning, while the REST API is better for direct application integrations and large sync jobs.