FitMeet MCP quickstart: authorize and find people

1. Add the remote endpoint

Set the transport to Streamable HTTP and enter the endpoint below. Configuration field names vary by host; use its documented remote MCP settings. An initial 401 is expected before authorization. The client should open the FitMeet login and consent flow.

https://api.fitmeet.cn/api/v1/mcp

2. Review the requested scopes

Use your own account and choose only permissions needed for the task. People discovery uses people:search; reading your profile uses profile:read. Publication and messaging have separate scopes. Cancel if the requested access is not appropriate.

After authorization, let the client initialize the connection and list tools. Use the schemas returned by the service.

3. Try a discovery request

Ask the Agent to find people with relevant experience while keeping this first test read-only. For example: “Find someone to discuss product-design portfolios. Show candidates only; do not publish or contact anyone.”

The Agent can use fitmeet_people_search and then permitted details from the current results. Empty results do not prove that no such person exists. Check constraints and discovery visibility instead of inventing candidates.

4. Preview before acting

Publication, opening a chat and sending a message each use a prepare and confirm workflow. Review the exact preview, then explicitly confirm the unchanged action. If details change or the preview expires, prepare it again.

If a write result is uncertain after a network failure, inspect the receipt or current state before creating another action.

5. Verify revocation

Revoke this client in FitMeet’s external connection management and verify that it can no longer use the old authorization. This is separate from your own profile’s external-discovery setting.

For connection problems, record the client version, time and non-sensitive error code. Never include passwords, verification codes or tokens in a support report.