Connect AI Tools to Your Knowledge Base

Agent Setup

For AI agents and automated systems — this is everything you need to connect. No API key. No registration flow. Just point and authenticate.

Configuration

Add this to your .mcp.json (Claude Code) or claude_desktop_config.json (Claude Desktop):

{
  "mcpServers": {
    "legate": {
      "type": "streamable-http",
      "url": "https://legate.studio/mcp"
    }
  }
}

That's it. No API key. No token. No environment variables.

What Happens Next

1. 1
   Your MCP client discovers the OAuth server

   It reads https://legate.studio/.well-known/oauth-authorization-server automatically.

2. 2
   A browser opens for GitHub authorization

   Log in with the GitHub account linked to your Legate Studio account.

3. 3
   You're connected — verify with check_connection

   The token is managed automatically. No manual credential handling required.

Verification

Tool: check_connection

Expected response:
{
  "status": "ok",
  "user": "<your-github-login>",
  "library": "<your-github-login>",
  "message": "Connected to Legate Studio"
}

Common First Steps

• check_connection — verify your identity and library access
• list_categories — see your library structure
• search_library — find notes by keyword
• create_note — add a new note to your library
• get_library_stats — see your library summary

Overview

Legate Studio is a personal knowledge management platform built around an MCP-first architecture. Your notes, categories, assets, and task lists are stored in a private per-user database — and the entire library is accessible to AI tools through a standard MCP server at https://legate.studio/mcp.

Unlike services that require API tokens, Legate uses OAuth 2.1 with PKCE. When you connect an MCP client, it redirects you to a GitHub login once. After that, the token is managed automatically — no copying keys, no environment variables, no expiry headaches.

Prerequisites

• A Legate Studio account — sign up free at legate.studio using your GitHub account
• A GitHub account (used for authentication — Legate uses GitHub OAuth)
• An MCP-compatible client (Claude Code, Claude Desktop, Claude.ai, or other)

Quick Start

Select your MCP client to see setup instructions:

{
  "mcpServers": {
    "legate": {
      "type": "streamable-http",
      "url": "https://legate.studio/mcp"
    }
  }
}

{
  "mcpServers": {
    "legate": {
      "type": "streamable-http",
      "url": "https://legate.studio/mcp"
    }
  }
}

{
  "mcpServers": {
    "legate": {
      "type": "streamable-http",
      "url": "https://legate.studio/mcp"
    }
  }
}

OAuth 2.1 Flow

Legate Studio uses OAuth 2.1 with PKCE for MCP authentication. Here's what happens when you connect:

1. 1
   Your MCP client discovers the auth server

   It fetches https://legate.studio/.well-known/oauth-authorization-server to get the authorization and token endpoint URLs.

2. 2
   Client generates a PKCE code challenge and redirects you to GitHub

   Your browser opens the Legate authorization page, which immediately redirects to GitHub's OAuth flow.

3. 3
   You log in with GitHub

   Authorize Legate Studio to access your GitHub profile (used only to identify your account).

4. 4
   Legate issues a token and redirects back to your client

   The MCP client exchanges the authorization code for an access token. This token is stored by the client and refreshed automatically.

5. 5
   All subsequent requests are authenticated

   Your client sends the token with every MCP request. You won't be asked to log in again unless the token expires or is revoked.

Available Tools

Legate Studio exposes 47 MCP tools grouped into 7 categories. All tools are available on any tier. Shared library tools require a managed-tier subscription.

Verification

After connecting, verify the integration is working:

1. Check the connection

Ask your AI assistant to call check_connection. You should see a response like:

{
  "status": "ok",
  "user": "your-github-login",
  "library": "your-github-login",
  "message": "Connected to Legate Studio"
}

2. List your categories

Ask your assistant to call list_categories. This will return the top-level organization of your knowledge base. If you've just signed up, you'll see the default categories.

3. Create a test note

Try creating a note to confirm write access is working:

Create a note titled "MCP Test" in the General category with content "MCP connection verified."

Then verify it appeared in your Legate Studio library at legate.studio.

Troubleshooting

Authentication loop / can't complete OAuth

Make sure you're logged into GitHub in your browser before starting the OAuth flow. If the browser doesn't open automatically, look for a URL in your MCP client's output and open it manually.

Tools not appearing in Claude

Check that:

• The type field is exactly "streamable-http" (not "http" or "sse")
• The URL is exactly https://legate.studio/mcp (no trailing slash)
• Your MCP client was fully restarted after editing the config

Authentication error: "User not found"

This means the GitHub account you authenticated with doesn't have a Legate Studio account. Make sure you sign up at legate.studio with the same GitHub account before connecting via MCP.

Sync errors / library out of date

Call verify_sync_state to check the sync status, then repair_sync_state to pull the latest state from GitHub. This is usually caused by a note being edited directly in GitHub between syncs.

Still having issues?

Contact support via the contact page or check the security docs for information about authentication architecture.