Skip to content
shuffl
Get started

Searches the public product guides only. Nothing from a workspace is read, and questions are not saved.

Tutorial

Use Shuffl with your agent

Use the built-in assistant, or connect your own agent over MCP, the API, the SDK or the CLI.

For Workspace administrators and agent builders

On this page

App links open your signed-in workspace. Check the selected workspace before making changes.

Use the built-in assistant

Open Chat in your workspace, ask about an approved source and follow the citation. The built-in assistant needs no API key. Workspace membership, employee access and source visibility still apply.

What Mello does for people

Mello also acts for a person, within what their role allows. Reads run at once. A change appears as a card in Chat or Slack first and runs when the person chooses Run.

  • Never offered as actions: credentials, exports, HR request cases, identity links, billing, Pulse answers and new hire check-ins.
  • From the People directory it answers who someone’s manager or reports are, their department and groups, who is in a group, and how to reach a colleague.
  • It cites the person or unit, says when a field isn’t recorded, and doesn’t discuss access, pay, benefits, performance or HR matters.
  • In a shared Slack channel or group message it can’t use the directory and asks you to message it directly.
  • Requests to change a record, and concerns about a person, go to Contact HR as a reviewed request.

Connect an existing agent

A workspace key’s MCP permission turns on MCP access. Its endpoint permissions decide what it can do over HTTP and MCP alike.

After you create a key, Check connection sends a tools/list request to the MCP server and a permissions request to the API. It lists the key’s tools and permissions and explains a denial, revoked key, rate limit or network failure.

The check tests the key, not a particular agent product.

Pick a route

  • MCP: an agent works in Shuffl through the remote MCP server, with OAuth or an API key as a bearer header.
  • API, TypeScript SDK or CLI: scripts run the same operations. Install @shuffl/sdk and @shuffl/cli from npm.

Where to connect

  • Set this up with your agent, under the workspace setup steps, has a prompt to copy into your agent. It runs setup over MCP and asks before it publishes or invites anyone.
  • Steps for other agents covers Claude, Claude Code, Codex, Cursor, ChatGPT, VS Code and other clients, with Add to Cursor and Install in VS Code buttons.
  • An OAuth client signs in in your browser and appears under Connected apps. It needs no API key.
  • For the API, SDK or CLI, an administrator creates a key in Workspace settings → API keys. It is shown once and expires after 30 days.

Start with a capability read

  1. Sign in, select the workspace and create a separate credential for this integration. Copy the one-time secret into your credential manager.
  2. For MCP, call get_team, then search_knowledge. For the API, SDK or CLI, read teams.current and permissions.list, then use only endpoints you’ve granted.
  3. Check the returned workspace and capabilities before running the integration. Empty knowledge results mean no current matching source is visible to the connected person.

The application origin is https://shuffl.ai. Send credentials over HTTPS in the Authorization header, only to the deployment that issued them. Keep them out of prompts, URLs, logs and public documents.

Add actions deliberately

The API, SDK and CLI also include reviewed management operations.

Before you grant a write

  • Grant each operation separately. Write doesn’t include Read.
  • Check inputs, confirmation, revisions and request keys in the reference first.
  • Over MCP, a key’s endpoint permissions are its tools, with the same checks.
  • OAuth consent, billing confirmation and provider installation stay in the browser.
  • An operation in the catalog may still need a provider your workspace hasn’t set up.
  • Revoking a credential stops future calls. It can’t erase what an agent already saved.

Give your agent the Shuffl skill

The Shuffl skill teaches your agent how to connect, which MCP tool to use when, and what to ask you before it acts. Every guide is a reference file in it. It holds no workspace data.

In Claude, upload the zip as a skill. In Claude Code, unzip it into ~/.claude/skills so the shuffl folder sits there. Other agents can read SKILL.md and the guides it links to.

Every guide page also has Open in Claude and Open in ChatGPT, which start a chat that reads the guide’s Markdown.

Was this guide helpful?