Gigwell MCP lets you connect Perplexity to your Gigwell data. Once it's connected, you can ask Perplexity about your roster, your organization's members and your reports in plain language, and it pulls live answers from Gigwell.
Before you start
Gigwell access: API/MCP access has to be enabled for your Gigwell user. It's currently available to agency users with the Owner role. Start a chat with us and we'll turn it on for you.
Perplexity plan: custom connectors are available on Pro and Enterprise plans. On Enterprise, an admin may need to allow custom connectors first.
Have your Gigwell login (or company SSO) ready. You sign in through Gigwell's secure login, so never put your password in the connector form.
Connection details
Name: Gigwell MCP
MCP server URL: https://api.gigwell.com/api/mcp
Description (optional): Access Gigwell roster, team and reports
Authentication: OAuth
Set it up
In Perplexity, go to Account settings → Connectors.
Click + Custom connector in the top-right corner.
In the pop-up, choose Remote.
Enter the name and MCP server URL above. Add the description if you like, and choose OAuth if asked. Leave the other settings as they are.
Tick the box confirming you understand custom connectors can introduce risks, then click Add.
Click the Gigwell MCP card on the Connectors page to start the sign-in. Log in with your Gigwell account, review the permissions and approve. If asked, pick the Gigwell agency you want to use.
Gigwell MCP then shows as connected. Each person signs in with their own Gigwell account, so Perplexity only sees what that user can see in Gigwell.
Test it
For your first question, name the connector so Perplexity knows to use it:
"Using Gigwell MCP, who are the members of my Gigwell organization?"
"Using Gigwell MCP, show me everyone on my roster."
"Using Gigwell MCP, tell me who I am and who the best-performing artists on my roster are."
Troubleshooting
You can't add a custom connector: check your Perplexity plan allows it. On Enterprise, ask your admin to enable connector permissions.
The connection fails before sign-in: make sure API/MCP access is enabled for your Gigwell user, and that the URL is exactly https://api.gigwell.com/api/mcp with no spaces.
Sign-in fails: remove the connector, add it again, and sign in with the right Gigwell account.
Perplexity isn't using Gigwell: start a new query with "Using Gigwell MCP, …" and check the connector is still connected in Account settings → Connectors.
Data is missing or it shows the wrong agency: your Gigwell user's access controls what Perplexity can see. Sign in again with the right account.
Security
Only use the Gigwell server URL shown here. To revoke access, remove Gigwell MCP from Perplexity's Connectors page, or ask us to turn off API/MCP access for your user.