Pipa Connectors

Pipa Connectors

Set up, inspect, explain, or troubleshoot Pipa connected tools.

Mental Model

• This is an operation, not a business lane.
• pipa-manage routes Pipa configuration; this skill owns connector setup and status.
• Business lanes own the job; composio-mcp performs live app discovery, authorization, and actions.
• ~/.pipa/CONNECTORS.md records selected capability-to-tool mappings. Composio remains the source of truth for live connection status.
• The ~~ prefix marks a capability placeholder resolved through the global map; it is not a toolkit slug.

Capability Categories

• ~~chat, ~~email, ~~calendar, ~~project tracker
• ~~code hosting, ~~knowledge base, ~~cloud storage, ~~CRM
• ~~support platform, ~~content platform, ~~payments, ~~time tracking

Lane Map

Review The Global Connector Map

1. Read ~/.pipa/CONNECTORS.md when present.
2. Use composio-mcp discovery to inspect supported toolkits and active connection status; inspect the complete selected-tool schema before any live check.
3. Map active connections to relevant capability categories. Ask only when multiple tools could fill the same category or the mapping is unclear.
4. Show the exact proposed connector-map diff based on verified active connections or explicit user choices. Preserve unrelated mappings.
5. Immediately before creating or updating ~/.pipa/CONNECTORS.md, require explicit approval for that exact diff. Connector-map write approval is separate from authorization-link completion; never infer one from the other.
6. Apply only the approved diff, verify the file write, and report success or failure. If the write fails, do not claim the map was updated.
7. Never store credentials, authorization links, secrets, or connection status. Check Composio before claiming a mapped tool is active.

Use this shape and include only relevant categories:

---
updated_at: <ISO-8601 timestamp>
---

# Pipa Connectors

| Capability | Tool | Toolkit |
|---|---|---|
| `~~project tracker` | Linear | linear |

The map is a durable tool-selection preference, not proof of live access. Discovery and verification must remain read-only. Live checks must use composio-mcp discovery and the complete selected-tool schema, and report every requested source as used, partial, stale, empty, declined, unavailable, or failed. Use not-requested only for sources outside the request's scope. Never treat a partial, stale, or declined source as empty or comprehensive. Continue from other usable evidence when safe and cite material checks with direct links or stable IDs. Optional communication checks must be narrow and tied to a known gap, not broad inbox or channel scans.

Add A Connector

1. Name the Pipa job the connector should support.
2. Map the job to a connector category and target app.
3. Pick the minimum permission: read, write, publish, notify, schedule, or manage.
4. Use composio-mcp discovery to find the toolkit and connection status, then inspect the complete selected-tool schema before execution.
5. If the user explicitly requested the connection and discovery reports it disconnected, return the MCP-provided authorization link directly and wait. Completing the link is consent to authorize; do not ask for another authorization confirmation before or after it.
6. After authorization, run the smallest safe read-only check.
7. Show the exact proposed connector-map diff and ask for separate explicit approval immediately before writing it. Do not treat authorization-link completion as map-write approval.
8. Apply only the approved diff, verify and report write success or failure, then summarize what connected, what Pipa can do, and remaining gaps.

Output Contract

• Connector objective.
• Target app or toolkit.
• Needed permission category.
• Current connection status: connected, needs-auth, declined, unavailable, failed, not-reviewed, or TBD.
• Connector-map update or TBD.
• Setup action or authorization step.
• Safety note for writes, publishing, or notifications.
• Provenance for any live check.
• Source state for every requested source: used, partial, stale, empty, declined, unavailable, or failed; use not-requested only outside scope.
• Exact proposed connector-map diff, approval status, and confirmed write result or failure.

Safety Rules

• Never claim active status without tool-returned status or verified runtime evidence.
• Do not ask users for raw secrets in chat.
• Do not test connections with writes, sends, publishes, reminders, triggers, or finance changes.
• Keep the lane objective visible when a connector supports business work; route only setup here.
• If the user wants to use an already-connected app now, preserve the business objective and use composio-mcp for execution.
• Update the global map only from verified discovery results or explicit user choices; do not guess mappings.
• Never store credentials, authorization links, secrets, or live status in the connector map.
• For an explicit connection request, discovery may return an MCP authorization link directly. Wait for the user to complete it; link completion is authorization consent, so do not add a second authorization confirmation.
• Connector-map writes remain a separate external state change. Show the exact proposed diff and require explicit approval immediately before writing; never treat authorization-link completion as map-write approval.