PECKY + AI
What you found,
ready to talk through.
Your review doesn’t have to end in another list nobody opens again. Connect your compatible assistant and ask it to look at what you left in Pecky.
Start with what you want to know.
Find your project. Review an observation. Open its evidence. Concrete steps to pick up the thread.
- “Find Trail and show me its pending pecks.”
- “Open the button peck and review the screenshot.”
- “Read this peck’s conversation before replying.”
- “Add this reply to the peck: we’ll review it in the next delivery.”
Illustrative examples. Responses depend on your data, the connected client, and the permissions you authorize.
Your assistant, with context at hand.
Connect a client that supports MCP.
Set up the connection to Pecky in your assistant. Setup varies by client.
Sign in and authorize permissions.
The connection respects your projects and permissions. Reading evidence and posting replies each require the corresponding authorization.
Ask it to review what you found.
Pecky provides observations, available context, evidence, and the conversation. Your assistant works from there.
You decide how far it goes.
You can review and revoke connections from your account. Access to a project depends on your membership and current permissions.
MCP is included in Pro. Your assistant may have its own requirements or terms.
What if you want to work on the code?
Your agent can bring that context into your development environment and help you make changes with its own tools.
See the journey for agents ↗