Connection and authentication
Endpoint: https://api.fitmeet.cn/api/v1/mcp. Transport: Streamable HTTP. Authentication: per-user OAuth authorization code flow with PKCE S256. Dynamic client registration is supported.
Use the client’s own OAuth flow. Do not configure a shared access token or paste credentials into a conversation.
What the tools do
The current service provides twelve tools in four groups: profile and people discovery; publication sources, preview and confirmation; conversation reading and opening; message preview and confirmation. Tool availability depends on the current authorization scopes.
The scopes are profile:read, people:search, hall:publish, messages:read and messages:write. Retrieve current tool schemas from the service rather than inventing parameters.
Authorization is not action confirmation
OAuth grants a capability scope. It does not approve a particular publication or message. Show the exact preview and obtain the user’s explicit confirmation before using a confirm tool. Opening a conversation creates an empty chat; it does not send a message.
External discovery is controlled by the profile owner. Search results retain uncertainty and do not guarantee identity, availability or outcomes. The MCP does not provide payment, booking or administrator capabilities.
Check the exact client
The public MCP and Skill package and the DeepSeek Harness plugin are available in their repositories. Check installation requirements and current verification status. No claim of universal client compatibility or marketplace approval is made.
Source and corrections
Prepared with AI assistance from FitMeet product documentation and engineering records. Examples are illustrative; client-specific acceptance and real-user outcomes are stated separately.
Publisher and company information (Chinese) →