Connecting Agents - GigUp Docs

Use this guide when adding GigUp to an AI agent that supports cloud MCP connections. Create a GigUp API token, pick your agent, paste the matching snippet, and ask the agent to list the GigUp tools.

Requirements

An MCP-compatible agent or client.
The hosted GigUp MCP endpoint.
A GigUp API token from Developer Tools.
Read permission for browsing account context. Add write permission only when the agent should create, update, delete, or generate content.

Quick Settings

Setting	Value
Server name	`gigup`
URL	`https://giguphq.com/mcp`
Connection type	Cloud MCP endpoint
Transport	`Streamable HTTP`
Authorization	`Authorization: Bearer {your_api_token}`

Use an environment variable when the client supports it. It keeps the token out of config files you may accidentally share.

export GIGUP_API_TOKEN="paste_your_gigup_api_token_here"

Copy-Paste Setup

Codex

Add this to ~/.codex/config.toml or to .codex/config.toml for one trusted project.

Codex docs

[mcp_servers.gigup]
url = "https://giguphq.com/mcp"
bearer_token_env_var = "GIGUP_API_TOKEN"

Then restart Codex or open the MCP panel and ask it to use GigUp.

Use GigUp MCP to list the tools available for my account.

Cursor

Add this to ~/.cursor/mcp.json for global use, or .cursor/mcp.json inside one project.

Cursor docs

{
  "mcpServers": {
    "gigup": {
      "url": "https://giguphq.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:GIGUP_API_TOKEN}"
      }
    }
  }
}

Open Cursor settings, refresh MCP servers, then ask Cursor to use GigUp.

Use GigUp MCP to show my account summary and available tools.

OpenCode

Add this to opencode.json or opencode.jsonc.

OpenCode docs

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gigup": {
      "type": "remote",
      "url": "https://giguphq.com/mcp",
      "oauth": false,
      "headers": {
        "Authorization": "Bearer {env:GIGUP_API_TOKEN}"
      },
      "enabled": true
    }
  }
}

Restart OpenCode or reload its config, then mention GigUp in your prompt.

Use GigUp MCP to list my active AI Job Trackers.

Other MCP Clients

Use these values in any client that supports remote or streamable HTTP MCP servers.

Server name: gigup
URL: https://giguphq.com/mcp
Transport: Streamable HTTP
Header name: Authorization
Header value: Bearer {your_api_token}

If your client does not support environment variables in headers, paste the full Authorization header value directly into the MCP settings. Do not paste the token into a chat prompt.

Confirm the Connection

After saving the config, ask one of these prompts:

Use GigUp MCP to list what tools are available for my account.

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

If the agent can answer with the available tools and account-aware capabilities, the connection is ready.