Librebase for AI agents

1. Hosted MCP (SaaS)

POST JSON-RPC to https://app-stage.librebase.xyz/api/mcp. Add this to MCP config when the client supports a URL (no PYTHONPATH, no repo clone):

{
  "mcpServers": {
    "librebase": {
      "url": "https://app-stage.librebase.xyz/api/mcp"
    }
  }
}

1. Call auth_status. If unauthenticated, call auth_start.
2. Paste showToHuman as your next chat message: the verificationUriComplete URL on its own first line, then the user code (on this origin: https://app-stage.librebase.xyz/mcp/authorize). Do not bury the link.
3. Open the link in your browser, review the permissions, and click Approve.
4. Call auth_poll (same mcp-session-id header, or pass deviceCode) until authenticated. Keep that session header; hosted sessions survive a Studio rebuild. The token is never returned in JSON-RPC.

2. Local stdio MCP (repo clone)

Only if you already have the mcp/ directory. auth_login polls for you and stores the token in the OS keychain.

{
  "mcpServers": {
    "librebase": {
      "command": "python3",
      "args": [
        "-m",
        "librebase_mcp"
      ],
      "env": {
        "LIBREBASE_ADMIN_URL": "https://app-stage.librebase.xyz/api/admin-proxy",
        "LIBREBASE_CONSOLE_URL": "https://app-stage.librebase.xyz"
      }
    }
  }
}

3. Tools after login

• Hosted: org_whoami, project_list, project_create, instance_*, host_*, member_*, key_*, auth_provider_*
• Stdio extras: migration_apply, sql_execute, table_list, oauth_setup
• Project end-user GitHub/Google is auth_provider_upsert — not MCP login.

Security

• Secrets are sealed in the KMS; key_get hands the value to the process only.
• Every decrypt/sign is audited.
• Agent tokens are user-bound and revocable instantly.