About Perfly MCP
Perfly Agent Sync is a hosted MCP server for coding agents to submit approved work summaries to Perfly. Its write-only workflow lets agents preview and select entries without access to source code or Perfly history.
Key features
- 01Verify connection and retrieve policy
- 02Preview and validate summary items
- 03Submit selected items as Today entries
- 04Write-only access to Perfly
Use cases
- 01Record approved coding work in a Perfly Today timeline
- 02Preview summaries before submitting them
- 03Send work summaries without sharing source code
MCP support
The hosted MCP server exposes connection checks, ingestion policy, preview, and submission tools. Agents can write selected summaries but cannot read Perfly history or other account data.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEPerfly Agent
Perfly Agent connects coding assistants to Perfly, so approved work summaries can be written into your Perfly Today timeline without giving the agent access to your source code, issue bodies, pull requests, documents, or company SaaS accounts.
This repository contains the public agent-facing packages for Perfly Agent Sync:
| Package | Purpose |
|---|---|
mcp/ | Hosted MCP server metadata, setup instructions, and client examples. |
skill/ | English canonical Skill instructions for Codex, Claude Code, and compatible coding agents. |
What It Does
Perfly Agent Sync gives your coding agent a narrow write-only workflow:
- Preview concise work summary items.
- Ask for confirmation unless unattended submission was explicitly enabled.
- Write selected summaries into Perfly as reviewable Today entries.
The MCP server exposes these tools:
| Tool | Purpose |
|---|---|
perfly_check_connection | Verify the connection and return non-secret token/client metadata. |
perfly_get_ingestion_policy | Return Perfly privacy and formatting rules. |
perfly_preview_work_items | Validate items and preview what would be submitted without writing records. |
perfly_add_work_items | Write selected summaries into Perfly as reviewable Today raw entries. |
Recommended Setup
Use the hosted MCP endpoint:
https://api.perfly.dev/mcp
Perfly supports MCP OAuth for clients that discover authorization from the server. For clients or environments that cannot complete a browser OAuth flow, Perfly also supports write-only bearer tokens created in the Perfly app.
Start with the MCP package:
Then install or copy the Skill instructions:
Privacy Boundary
Perfly Agent Sync is designed for summary metadata only.
Do not submit:
- source code or diffs
- secrets or credentials
- customer data
- issue bodies or pull request bodies
- document bodies or attachments
- full terminal output or logs
Agents should submit short titles, optional notes, timestamps, source labels, and compact metadata references only.
Packages And Registries
MCP registries should point to:
mcp/
or:
mcp/manifest.json
Skill hubs should point to:
skill/
or:
skill/SKILL.md
The current ClawHub listing is:
https://clawhub.ai/levi840714/skills/perfly-skill
The current Smithery listings are:
https://smithery.ai/servers/perfly/perfly-mcp
https://smithery.ai/skills/perfly/perfly-skill
Project Links
- Perfly: https://perfly.dev
- App setup page:
https://app.perfly.dev/agent-setup - MCP endpoint:
https://api.perfly.dev/mcp
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.