MCP
MCP Overview
Get started with GigUp MCP. Learn what it is, when to use it, how the cloud endpoint works, and the basic limits to expect.
GigUp MCP lets supported AI agents connect to GigUp through a secure cloud endpoint. Use it when you want an agent to understand GigUp docs and help with account workflows such as AI Job Trackers, tracked jobs, proposal templates, and proposal generation.
What is MCP?
MCP is a standard way for an AI agent to ask an application for useful context and actions. In GigUp, MCP exposes authenticated tools for dashboard workflows plus documentation, integration guidance, API context, and setup direction.
When to Use MCP
| Use MCP when | Use API docs when |
|---|---|
| You want an AI agent to manage trackers, search jobs, update statuses, generate proposals, or help plan an integration. | You are personally reading endpoint details and writing requests. |
| You want the agent to use your GigUp account context or find the right docs for a task. | You already know which endpoint or resource you need. |
| You want guided setup or workflow suggestions. | You need a direct reference for authentication, permissions, or responses. |
How It Works
- Create a GigUp API token from Developer Tools.
- Add the GigUp MCP endpoint to an MCP-compatible agent.
- Send the API token as a bearer token.
- Ask the agent to help with trackers, jobs, proposal templates, proposals, docs, or integration planning.
Endpoint
Connect agents to the hosted MCP endpoint:
https://giguphq.com/mcpIf your agent asks for a connection type, choose streamable HTTP. The endpoint requires a bearer API token.
Rate Limiting
MCP requests are rate limited to 60 requests per minute. If an agent is making repeated requests, slow down the workflow and retry after the limit resets.