OloLand Setup

OloLand authenticates via OAuth (one-click sign-in) — there is no key to copy for normal use. The plugin's MCP server is OAuth-native: connecting it opens a sign-in page at api.ololand.ai, you approve, and you're done.

Connect (interactive — Claude Desktop / Cowork / Claude Code / Cursor / Grok Bot)

1. Enable / connect the ololand MCP server in your client's connectors or

plugin settings. On Cursor and Grok Bot this is the connector bundled by the Cursor-format plugin (.mcp.json → https://api.ololand.ai/mcp).

1. The host opens the OloLand sign-in page at https://api.ololand.ai — sign

in with email or Google and click Approve.

1. That's it. Try any OloLand command:

• /dd-analyze — Run bounded extraction, risk, and financial-snapshot processing for a deal; cross-document reconciliation is a separate explicit tool/workflow
• /similar-deals — Find comparable transactions

If you see OloLand tools in your tools list, you're connected.

The sign-in runs on a single canonical host and self-heals the browser handoff, so it works in Cowork and Desktop. If a sign-in window doesn't return on the first try, just reconnect the server and approve again.

Headless / CI (no browser)

Automated environments can't do an interactive sign-in, so they use a long-lived agent key as a Bearer token. One command does the wiring — no hand-editing JSON:

1. Get a key at https://api.ololand.ai/connect (sign in → **Generate new

key**, starts with olo_agent_sk_), and export it:

   export OLOLAND_AGENT_KEY=olo_agent_sk_...

1. Run the setup script — it adds the OloLand MCP server to your .mcp.json,

preserving any servers already there:

   "${CLAUDE_PLUGIN_ROOT}/scripts/setup_headless.sh"

The config references ${OLOLAND_AGENT_KEY} rather than the literal key, so the secret stays in your environment, not on disk. Flags: --config <path> targets a different file; --inline-key writes the literal key for ephemeral CI that can't set an env var (gitignore that config).

1. Restart / reconnect your MCP host and run any OloLand command.

(If you're asking Claude to set this up, it can run that script for you.)

<details> <summary>Manual config — equivalent to what the script writes</summary>

The published plugin manifest is OAuth-native and sends no header, so add the OloLand server to your own MCP config with an Authorization header:

{
  "mcpServers": {
    "ololand": {
      "type": "http",
      "url": "https://api.ololand.ai/mcp",
      "headers": { "Authorization": "Bearer ${OLOLAND_AGENT_KEY}" }
    }
  }
}

</details>

The agent key works in every MCP host and never expires until you revoke it.

Troubleshooting

• "Authentication required" / 401: the OloLand server isn't connected yet.

Reconnect it and complete the OAuth sign-in (interactive), or check your OLOLAND_AGENT_KEY + Authorization header (headless).

• Sign-in window didn't return: reconnect the server and approve again —

the handoff is self-healing and the second attempt typically completes. If it still stalls, generate an agent key (see Headless / CI) and use that.

• "Rate limit exceeded": Free tier allows 10 requests/minute. Contact

[email protected] to upgrade.

• MCP server unreachable: check https://status.ololand.ai or try again in

60 seconds (Cloud Run cold start).