MCP.so
Sign In
P

Perfly MCP

@perfly-dev

About Perfly MCP

Perfly Agent Sync is a hosted MCP server for sending approved coding-agent work summaries into perfly.dev. It is built for narrow, write-only ingestion: agents can preview and submit selected summary items, but they cannot read your Perfly history, reports, profile, billing, inte

Basic information

Category

AI & Agents

Transports

stdio

Publisher

perfly-dev

Submitted by

Levi Liu

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Perfly MCP?

Perfly MCP is a hosted MCP server that connects coding assistants to Perfly, enabling approved work summaries to be written into your Perfly Today timeline without exposing source code, issue bodies, pull requests, documents, or company SaaS accounts.

How to use Perfly MCP?

Use the hosted MCP endpoint at https://api.perfly.dev/mcp. Perfly supports MCP OAuth for clients that discover authorization from the server, or write-only bearer tokens created in the Perfly app for environments that cannot complete a browser OAuth flow. Detailed setup instructions are available in the mcp/ directory, along with client examples for Claude Code, Codex, and Cursor.

Key features of Perfly MCP

  • Exposes tools: perfly_check_connection, perfly_get_ingestion_policy, perfly_preview_work_items, perfly_add_work_items
  • Write-only workflow with user confirmation before submission
  • Supports unattended submission when explicitly enabled
  • Only accepts summary metadata (titles, optional notes, timestamps, source labels, compact references)
  • Protects privacy by blocking source code, secrets, customer data, issue/PR bodies, and document content

Use cases of Perfly MCP

  • A coding agent previews and submits concise work summaries to a developer’s Perfly Today timeline
  • Managers review Today entries to track progress without granting agents access to sensitive project content
  • Developers enable unattended submission for automated daily standup updates
  • Teams maintain a privacy boundary while still leveraging AI for status tracking

FAQ from Perfly MCP

What data should not be submitted to Perfly MCP?

Do not submit source code, diffs, secrets, credentials, customer data, issue bodies, pull request bodies, document bodies, attachments, or full terminal output. Only short titles, optional notes, timestamps, source labels, and compact metadata references are allowed.

How does authentication work?

Perfly MCP supports MCP OAuth for clients that can complete a browser flow. For environments that cannot, write-only bearer tokens can be created in the Perfly app.

What is the MCP endpoint URL?

The hosted endpoint is https://api.perfly.dev/mcp.

What tools does Perfly MCP provide?

Four tools: perfly_check_connection (verify connection), perfly_get_ingestion_policy (get privacy/formatting rules), perfly_preview_work_items (validate/preview without writing), and perfly_add_work_items (write summaries as Today entries).

Where is the MCP server registered?

MCP registries should point to mcp/ or mcp/manifest.json. Smithery listings are available at https://smithery.ai/servers/perfly/perfly-mcp.

Comments

More AI & Agents MCP servers