Start with one MCP tool with a clear responsibility, such as querying service health.
Specify the target, time range, and response fields. For a first integration, a read-only query can make it easier to define empty data, insufficient permissions, and service failure. Match the protocol and transport supported by the target client.
Provide the Server URL and explain account, permission, and configuration requirements. Include a representative operation and service limits.
Configure OAuth, complete online authorization, and check the returned result. Review may also accept a test account, but that account does not replace the service's OAuth integration. Continue with debugging.
Open Extensions → Connectors and use the available add or authorize workflow. Read tool definitions, run a representative request, and compare tool input, service output, and client display. Check first-time authorization and insufficient permissions, then publish the connector.
Define the operation
Specify the target, time range, and response fields. For a first integration, a read-only query can make it easier to define empty data, insufficient permissions, and service failure. Match the protocol and transport supported by the target client.
Implement the service
- Prepare a compatible MCP service.
- Define the tool's purpose and input constraints, and validate required parameters.
- Call the real business API and handle timeouts and failures.
- Return useful results without disguising errors as normal data.
- Restrict access using each account's authorization rather than sharing your personal identity.