MCP Capabilities

GigUp MCP gives AI agents a guided way to work with GigUp account data and developer docs. After you connect an API token, an agent can inspect your account context, manage trackers, search tracked jobs, manage proposal templates, generate proposals, and cite docs when it needs reference material.

What Users Can Do

User goal	How MCP helps
Understand account limits	The agent can check the current team, tracker limits, template limits, and daily alert usage.
Create and manage AI Job Trackers	The agent can list, search, create, update, pause, reactivate, or delete trackers.
Search tracked jobs	The agent can find jobs by keyword, tracker, job type, client rating, client spend, difficulty, location, and status.
Track application progress	The agent can mark jobs as applied, viewed, interviewed, or hired, and save proposal text and connects used.
Manage proposal templates	The agent can list, create, update, set default, and delete reusable proposal templates.
Generate proposals	The agent can generate proposal text for a tracked or imported job using optional template context.
Find the right documentation	The agent can identify whether a task belongs in API docs, MCP docs, jobs, trackers, or proposal templates.

Capability Types

Capability	What it means for users
Tools	Actions the agent can call to read account data, perform allowed dashboard workflows, discover docs, inspect API metadata, and get setup examples.
Resources	Read-only documentation context the agent can load when it needs more background.
Prompts	Reusable planning templates that help the agent produce consistent GigUp-aware implementation plans.

Available Actions

GigUp exposes focused MCP tools. See the full list on MCP Tools.

• Discover what GigUp MCP can do.
• Get connection setup details.
• Load examples for common agent workflows.
• Check authenticated account and team limits.
• Create, search, update, and delete AI Job Trackers.
• Search tracked jobs and open individual job details.
• Update tracked job status and saved proposal details.
• Create, search, update, and delete AI proposal templates.
• Generate proposals for accessible jobs.
• List developer surfaces such as API docs and MCP docs.
• Inspect API endpoint summaries and permissions.
• Read documentation summaries and links.

How Agents Use Capabilities

A typical agent flow looks like this:

1. The user asks a GigUp-specific question.
2. The agent checks account context, token permissions, or relevant docs.
3. The agent calls the safest specific tool for the task.
4. The agent explains what it found or changed and cites docs when docs were used.

Boundaries

• MCP actions are limited by the API token permissions you grant.
• Use read for inspection and write only when the agent must change data or generate proposals.
• Use the REST API for direct application integrations and large data syncs.
• Use MCP when an AI agent should help through a conversational workflow.