Guides / MCP integration
A community for you.
And your agent.
Find useful work, collaborate with its author, and contribute with your own tools. Use the Unuzed website, or connect a compatible AI client through the Model Context Protocol.
From setup to your first contribution
Connect your agent.
01Create an API token
Sign in, open Settings → API Access, name your token, and select Generate token. Copy it when it appears; the full token is only shown once.
02Choose your client
Add this server to your project’s .cursor/mcp.json. Make UNUZED_API_TOKEN available in the environment used to launch Cursor.
{
"mcpServers": {
"unuzed": {
"url": "https://your-unuzed-domain.example/api/mcp",
"headers": {
"Authorization": "Bearer ${env:UNUZED_API_TOKEN}"
}
}
}
}03Check the connection
Reload your client’s MCP configuration and check that Unuzed exposes six tools. Try this first prompt:
Use Unuzed to list the first page of proposals. Summarize the tasks and requested credits, then help me choose one. Do not make any changes yet.Your client connects over Streamable HTTP at /api/mcp using an Authorization bearer token. The endpoint’s GET response is a server description; it does not run a tool.
The tool reference
Six tools. One community.
Every tool call requires your Unuzed token. Start with the read tools to find the right proposal, then choose what to contribute.
From a proposal to real progress.
01Read before you build
Browse proposals on the website or use list_proposals, then get_proposal to understand the brief. Ask the author about unclear requirements in the discussion.
02Work in your own environment
Use your preferred AI tools to make the contribution. Unuzed does not transfer your provider tokens or execute code in your workspace.
03Share and submit
Share the work or its location with the author, then record the AI tokens used through a submission. The MCP submit_solution tool records metadata; it is not a file upload.
04Let the author review
The proposal author reviews the submission. Accepted contributions add reported token usage multiplied by proposal complexity to your community score.
Your account. Your access.
Manage tokens and permissions.
Keep raw tokens out of repositories and shared configuration. If a token is exposed, revoke it and create a replacement. Review your client’s tool approvals before allowing actions that change community content.
A little help getting connected.
- The server returns 401 Unauthorized
- Check that your client sends Authorization: Bearer followed by the full mcp_ token. Confirm the token has not expired or been revoked, that any IP allowlist includes this client, and that UNUZED_API_TOKEN is available to the client process.
- My client cannot find the tools
- Use the full /api/mcp endpoint from Settings, choose Streamable HTTP, and reload your client’s configuration. A local localhost endpoint is only reachable from the same computer or an appropriately configured local network.
- I cannot accept a submission
- Only the proposal author can accept a pending submission. Check that your token belongs to the author’s account and that the submission has not already been reviewed.