Skip to main content
Profy Experts can be consumed as a Skill or MCP Server by mainstream AI coding tools, giving developers access to Expert capabilities without leaving their IDE.

Supported Tools

Prerequisites

  • Profy account with Developer role
  • API Key (create at Developer Console, format profy_sk_*)
  • Expert must have API access enabled (apiAccess: "open")

A Skill is a Markdown file that teaches AI coding tools how to call the Profy API. Once installed, the agent automatically knows when and how to invoke Profy Experts.

Claude Code

Set your API Key:
Then simply tell Claude Code:
“Use Profy’s react-architect Expert to review this code”
Claude Code will follow the Skill instructions and call POST https://api.profy.cn/v1/experts/react-architect/chat automatically.

Cursor

Codex / Cline / Gemini CLI

Place SKILL.md in your project’s agent skills directory (exact path varies by tool). Ensure the PROFY_API_KEY environment variable is set.

Method 2: MCP Server Integration

MCP (Model Context Protocol) provides deeper integration, allowing AI tools to invoke Profy Experts via structured tool calls.

Configure .mcp.json

Create .mcp.json at your project root:

Register in Claude Code

Available Tools (after MCP Server launch)

The MCP Server endpoint mcp.profy.cn is under development. Please use the Skill method for now.

API Endpoint Reference

All requests require Authorization: Bearer $PROFY_API_KEY. Base URL: https://api.profy.cn

Invoke an Expert

Response: SSE stream (text/event-stream). The X-Session-Id header is used for multi-turn conversations.

Multi-turn Conversations

OpenAI-Compatible Chat


For Creators: Enable API Access for Your Expert

  1. Edit your Expert in Studio
  2. Set API Access to Open (any developer with an API Key can invoke)
  3. Publish a new version
Once enabled, your Expert can be invoked by developers worldwide from Claude Code, Cursor, and Codex.

FAQ

  • Skill: Plain text instructions that teach AI how to curl your API. Zero infrastructure, cross-platform compatible.
  • MCP Server: Structured tool protocol where AI makes function calls. More powerful but requires server-side support.
Start with Skills. Upgrade to MCP Server seamlessly once available.
The Expert’s api_access field is off (default). Ask the Expert creator to enable API access, or try a different Expert with api_access: open.
Responses use standard Server-Sent Events format. Each line starts with data: and the stream ends with data: [DONE]. Most HTTP clients and AI tools natively support SSE parsing.
Via the /v1/chat/completions endpoint, all platform-configured models are available (DeepSeek, Qwen, etc.). Available models depend on platform configuration.
Token-based billing (METERED). Credits are deducted from the API Key owner’s account. View usage in the Developer Console.

Next Steps