PECKY FOR AGENTS
From a finding on screen
to work on your project.
The screenshot shows what happened. The comment explains what you saw. Your connected agent can consult both before working on the code.
Review the real thing. Then pick it up with your agent.
Spot the detail in the product.
Explore the site in your browser. Save a screenshot and your observation in Pecky. In Chrome, you can add an element reference and the web context you choose.
Give your agent a starting point.
“Find Trail and review the peck about the clipped button.” Your connected agent reads the detail, evidence, and conversation through MCP.
Work in your development environment.
Your agent needs independent access to your repository and tools. Pecky provides context; the agent makes changes with its own permissions and following your instructions.
Keep track of the work.
With the necessary permissions, your agent can post a reply or update the peck’s status. Return to the product and check the result.
What the connection makes possible.
- Find projects and consult their reviews and pecks.
- Read observations, context, conversations, and authorized private images.
- Post replies and update statuses, according to role and permissions.
The current MCP tools don’t administer projects, invite members, or delete or move pecks.
Choose how to develop. Keep the context.
The journey isn’t tied to a single agent brand. You need a client compatible with Pecky’s MCP and an authorized connection. Compatibility and setup are validated per client.
A conversation you can continue.
Your findings and your client’s observations stay in the project, alongside evidence and replies. The next round of improvements starts there.
See what you can ask your assistant ↗