Where it fits
Agent developers who need a verified human to handle a real-world task.
- Search privacy-safe human availability by skill and country.
- Submit a real-world task request for MEKU operator review.
- Check the status of a submitted human task request.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with MEKU Human Cloud
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Hand the current conversation to a new background agent that picks up the work right away.
Turns a decision the user cannot fully answer into a questionnaire for someone else to fill in.
Covers writing documents for agents. Use it when creating or editing skills, or when modifying AGENTS.md or CLAUDE.md.
No skills found
Try a different search term or clear the filters.
OpenCode config
Merge this object into opencode.jsonc. The Authorization header is required; the key is issued manually by MEKU.
{"$schema":"https://opencode.ai/config.json","mcp":{"servers":{"meku-human-cloud":{"type":"remote","url":"https://meku.farm/api/public/mcp","oauth":false,"headers":{"Authorization":"Bearer <YOUR_MEKU_KEY>"}}}}}Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name meku-human-cloud. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
meku-human-cloudappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Search privacy-safe human availability by skill and country. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
- The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
MEKU Human Cloud documentationhttps://meku.farm/docs