Ongoing agent access, pinned to one person and one Team.

1. 01

   Enable MCP Access for the Team

   A person with the Team setting permission enables MCP access in Team settings. Disabling it later rejects all connection requests immediately without deleting the connections.

2. 02

   Create a personal MCP Connection

   In Profile → MCP connections, give the client a recognizable name and create it. Wagglet shows the MCP Token once and retains only its hash. Save it in the client's protected credential store, not in a repository, prompt, URL, or screenshot.

3. 03

   Configure the Wagglet endpoint

   Point the MCP client at the canonical HTTPS endpoint and send the token in the Authorization header. The public endpoint link is useful for configuration, but a browser visit without MCP authentication is not a workspace login.

4. 04

   Verify current identity before work

   Call whoami first. Use its Team, identity, roles, permissions, and the current tools/list schemas as authority. Tool names and schemas can evolve; a copied old catalog is not the source of truth.

URL     https://wagglet.com/api/mcp
Header  Authorization: Bearer <your MCP token>

Use list_notes and search_notes to discover notes and transcripts. read_note returns a short-lived markdown download URL and includes small documents inline. Every download rechecks access.

create_note creates a Private Note. Read before update_note or append_note, and supply its revision and a fresh operation id. Writes merge with live typing; conflicting replacements ask you to read again.

1. 01

   Discover identifiers

   Use bounded search and list tools for tickets, Stories, Notes, and people. Continue through cursors when the requested population is larger than one response.

2. 02

   Read the complete authorized record

   Fetch the ticket or Story before changing it. Keep the returned record and item revisions for the intended mutation. Recurring Template records include their structured schedule; scheduled Occurrences include their template provenance.

3. 03

   Use the matching lifecycle command

   Choose the explicit Wagglet action. Give each intended mutation a fresh operationId; reuse it only to retry that exact operation after an uncertain network result.

4. 04

   Reconcile conflicts and confirmations

   On STALE_REVISION, read again and reconcile with current state. On CONFIRMATION_REQUIRED, show the impact to the user and continue with that tool's required confirmation fields against the same current revision only after approval.

Current checks

Connection revocation, Team MCP setting, current membership, roles, effective permissions, and the connection's Team are checked on every request.

Private Drafts

Only the creator and collaborators can see them. Everyone else receives no identifier, count, relationship, or existence signal.

Human-only tasks

Create and update tools accept humanOnly and preferredAssigneeId; list_people supplies teammate IDs. Assignment reserves work without claiming it or granting private Draft access. Human-only mode sets hands-on to 5 and revokes machine tokens when changed. Existing human-only instructions stay hidden and protected, and reserved lifecycle actions still require a person.

Attachments

Every MCP read reauthorizes task visibility. Bounded text and images may return inline; other files use short-lived download access.

Analytics

Outcome analysis requires the dedicated analytics permission and returns bounded product evidence, never arbitrary SQL or an invented stored taxonomy.

Action records

A successful mutation records its connection, person, tool, target, and time. Authored content, arguments, credentials, reads, and refusals are not copied into that origin record.

• Rotate a connection when its credential may have been exposed.
• Revoke clients you no longer use; revoked credentials fail on the next request.
• Team disablement preserves connections so they remain visible and revocable, but they cannot be used until access is enabled again.
• MCP Connections have no automatic expiry. Review names, creation time, and last-use time as part of normal Team access hygiene.

For one claimed task, use Task Handoff. Its starting credential is read-only, claim-rooted, and short-lived; delivery arrives separately. Whichever path you choose, use your own provider account and keep delivery, acceptance, merge, and deployment truthful and separate.