MCP Authentication

GigUp MCP uses API tokens to identify the account or workspace an agent is allowed to help with. A token is required for MCP requests because tools can read account context and, with write permission, change account data.

How Authentication Works

The agent sends your GigUp API token as a bearer token. GigUp uses that token to authenticate the user, resolve the current team, and decide which read or write tools the agent can use.

Create a Token

1. Open Developer Tools.
2. Create a new API token for the agent or workspace.
3. Select the minimum permissions needed for the workflow.
4. Copy the token and store it securely. Tokens are shown only once.

Send the Token

Add the token as an authorization header in your MCP client configuration:

Authorization: Bearer {your_api_token}

Permissions

Permission	Use it for
read	Let the agent inspect account summary, trackers, tracked jobs, proposal templates, documentation, and API metadata.
write	Use when the agent needs to create, update, or delete trackers/templates, update job status, update AI preferences, or generate proposals.

Security Practices

• Create a separate token for each agent or workspace.
• Use the lowest permission level that supports the workflow.
• Do not paste tokens into prompts or public documents.
• Revoke tokens when an agent or workspace no longer needs access.

Authentication Errors

Error	What to check
Missing token	Add the bearer token header to the MCP client.
Invalid token	Create a new token from Developer Tools and update the agent configuration.
Insufficient permissions	Confirm the token has the permissions required for the workflow.