Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: Basic auth.
  • Connection: HTTP Basic auth with GURU_USERNAME as the username and GURU_USER_TOKEN as the password.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. Get a Guru account: Sign up at https://www.getguru.com - a free trial workspace is enough for testing the API.
  2. Generate an API token: In Guru, open Settings → API Access and generate a token. A User token (username = your email) acts as you across the knowledge base; a Collection token (username = collection ID) gives read-only access to one collection. Admins can issue tokens for other users.
  3. Store the credentials: Add GURU_USERNAME=<your email or collection ID> and GURU_USER_TOKEN=<your token> to your .env file. The API uses HTTP Basic auth against https://api.getguru.com/api/v1.
  4. Verify access: Run the List Collections tool (or GET /api/v1/teams with curl) - a successful response confirms your credentials work.

​
Provider notes

  • Collection tokens are read-only and scoped to a single collection - use a User token for the Create Card and Verify Card tools
  • Card search returns at most 50 results per page; narrow your search terms instead of paging when possible
  • shareStatus must be TEAM for a card to be visible to the whole team
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as guru__search_cards with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.