Quickstart

From a fresh signup to "Cursor is querying my GitHub" in about 5 minutes.

1. Sign up & create a workspace

Go to /signup, sign in with email or Google, and pick a workspace slug. The slug ends up in your MCP URL (https://app.gigamcp.io/t/<slug>/mcp) so make it short and DNS-friendly — acme, not Acme Corp Hamburg!.

2. Invite teammates

Open Members from the sidebar and add up to your plan's seat-limit. Invitees get a magic link via email; their membership is provisioned the first time they click through.

3. Connect your first source

Go to Connectors, click Add connector, pick GitHub or Google Drive, and follow the per-connector recipe:

  • GitHub — install the GitHub App on your org, or paste a PAT scoped to the repos you want indexed.
  • Google Drive — paste a service-account JSON for shared folders, or use Personal connectors for your own Drive.

Choose a visibility for the connector — "Whole tenant", "Specific group", or "Just me". This becomes the audience filter on every chunk indexed from that source.

4. Paste the MCP URL into your AI client

Open Settings → API keys, mint a token (any member can; up to 5 active keys each), and copy the URL + token into your client config. The key authenticates as you — your group memberships decide what content the client can read. Recipes for the popular ones:

5. Test it

Ask your AI agent something like "What's in our last weekly?" or "Summarise the API docs in this repo" and check that the response includes citations from the connector you set up.

What's next?

  • Set up groups if you have departments that need separate access (e.g. HR vs. Eng).
  • Move from Free to Starter when you outgrow the 5-seat / 1k-call ceiling.
  • Configure Audit log retention for compliance reviews.