LogoZero Authority
LogoZero Authority
Model Context Protocol

Connect Zero Authority MCP to your AI

Use Claude Code, Cursor, or Claude Desktop to list gigs, bounties, and quests — powered by your account. Start with an API key, then paste one of the configs below.

Create API keyAIBTC MCP (on-chain)

You need to be signed in. Dashboard → API Keys.

MCP: https://chronosagora.com/mcp

How it works

1

Create an API key

Keys authenticate your assistant to your account. You only see the full key once — store it safely.

2

Use the right MCP URL

This deployment uses the testnet MCP endpoint (Chronos Agora). For mainnet, use the URL in the note below.

3

Add the MCP in your editor

Paste the config below into Claude Code, Cursor, or Claude Desktop. Replace YOUR_API_KEY with your key.

4

Optional: on-chain actions

Creating bounties or gigs on-chain also requires the AIBTC MCP and a Stacks wallet — see the resources section.

MCP endpoint for this deployment

Configs below use this URL. Replace YOUR_API_KEY everywhere.

NetworkMCP URL
Testnet
Chronos Agora
https://chronosagora.com/mcp

Other environment: http://zeroauthoritydao.com/mcp (Mainnet (Zero Authority))

Claude Code

In a terminal. You can rename chronosagora to any label you like.

Shell
claude mcp add --transport http chronosagora https://chronosagora.com/mcp --header "Authorization: Bearer YOUR_API_KEY"

Or edit %USERPROFILE%\.claude.json (Windows) or ~/.claude.json (macOS/Linux):

~/.claude.json
{
  "mcpServers": {
    "chronosagora": {
      "type": "http",
      "url": "https://chronosagora.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Useful: claude mcp list · in-app /mcp

Cursor

Settings → Tools & MCP, or edit .cursor/mcp.json. Restart Cursor or reload MCP after saving.

.cursor/mcp.json
{
  "mcpServers": {
    "chronosagora": {
      "url": "https://chronosagora.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Desktop

Merge into %APPDATA%\Claude\claude_desktop_config.json (Windows) or ~/Library/Application Support/Claude/claude_desktop_config.json (macOS). Restart Claude Desktop.

claude_desktop_config.json
{
  "mcpServers": {
    "chronosagora": {
      "url": "https://chronosagora.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude on the web (claude.ai)

The website connector often expects OAuth, while our MCP uses a Bearer API key. If you only see OAuth client id/secret fields, use Claude Desktop or Claude Code with the configs above — they support custom headers.

On-chain bounties & gigs (AIBTC)

Our MCP can prepare contract calls; signing and broadcasting use the AIBTC MCP and your Stacks wallet. Add both servers in Cursor — platform URL + AIBTC NETWORK=testnet matching this deployment:

.cursor/mcp.json — platform + AIBTC
{
  "mcpServers": {
    "chronosagora": {
      "url": "https://chronosagora.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    },
    "aibtc": {
      "command": "npx",
      "args": ["-y", "@aibtc/mcp-server@latest"],
      "env": {
        "NETWORK": "testnet"
      }
    }
  }
}

Flow: prepare → call_contract (AIBTC) → sync with the returned txid. See the AIBTC MCP server repo for wallet setup.

Ready to connect?

Generate a key, copy a config block, and ask your assistant to list open bounties or gigs.

Go to API Keys
    Shapes