Skip to main content
Profy provides an MCP (Model Context Protocol) Server that lets you manage the full Expert lifecycle from within Cursor, Codex, or any MCP-compatible IDE — without leaving your editor.

Quick Connection

Create or edit a .mcp.json file in your project root:
The MCP Server authenticates using your Profy browser session. On first use, your IDE will prompt you to log in to Profy in the browser.

Available Tools (22)

The Profy MCP Server provides 22 tools covering the complete workflow from Expert creation to monetization. All tools are lightweight proxies to existing Profy services and introduce no new business logic.

Identity (2)

Expert Config (4)

Skills (3)

Billing & Publish (3)

Distillation (2)

Distillation tools use a synchronous SSE collection mode and may take ~30 seconds to complete. Please wait patiently for the response.

Testing (2)

Evolution (3)

Earnings (2)

Typical Workflows

Creating an Expert from Scratch

Reviewing and Optimizing an Expert

Authentication

The MCP Server uses Profy’s Session authentication (Browser Cookie / Bearer Token).
  • Cursor / Codex IDE plugins: The IDE handles authentication automatically, prompting a browser login on first use
  • Manual configuration: If your IDE does not handle it automatically, ensure you are logged in at app.profy.cn in your browser

Profy Plugin (IDE Plugin)

Profy provides IDE plugins for Cursor and Codex that include a pre-configured MCP Server and 4 dedicated Skills: The plugin’s MCP configuration (.mcp.json) points to mcp.profy.cn/mcp, identical to the manual configuration method.

Transport Protocol

The Profy MCP Server uses Streamable HTTP transport (stateless mode), built on the @modelcontextprotocol/server SDK’s WebStandardStreamableHTTPServerTransport. Key characteristics:
  • Stateless: No session management; each request is handled independently
  • CORS: Supports cross-origin requests (with MCP-required headers)
  • Timeout: 300-second server timeout (to accommodate time-consuming operations like distillation)
  • Path: All MCP requests are sent to /mcp

Notes

start_distillation and continue_distillation internally call the invoke endpoint synchronously via the SSE Collector, which may take 20–60 seconds. This is expected — distillation involves multiple rounds of AI interaction.
test_expert also waits synchronously for the Expert’s reply via the SSE Collector. Simple conversations typically complete within 5–15 seconds.
Most tools require a logged-in Profy account. Creating and publishing Experts requires first applying for creator status via apply_creator.
Except for browse_marketplace and list_marketplace_skills, all tools require authentication. Calling without being logged in will return an authentication error.

Next Steps

Quickstart

Make your first API call

App Development Guide

Build a complete Profy App