Use Scalekit docs in your AI coding agent

AI coding agents like Claude Code and Cursor work from training data that can be months out of date. When you ask them to help integrate Scalekit, they may reference old APIs, deprecated patterns, or incorrect parameter names — leading to bugs that are hard to trace.

Context7 provides two ways to access live, version-accurate documentation:

• CLI — query docs directly from your terminal (recommended for most developers)
• MCP server — integrates with AI agents for automatic doc injection

Both methods pull the same up-to-date content. Choose CLI for direct control, or MCP server for seamless AI agent integration.

Scalekit’s full developer documentation is indexed on Context7 at context7.com/scalekit-inc/developer-docs, covering hundreds of pages and thousands of code snippets across SSO, SCIM, MCP auth, agent auth, and connected accounts.

Get accurate answers about Scalekit

Context7 retrieves relevant documentation from the indexed Scalekit docs and delivers it to you or your agent. The AI then answers using accurate, current content rather than training data.

Context7 provides three main capabilities:

• library — resolve library IDs and discover docs
• docs — fetch specific documentation sections
• MCP server tools for AI agent integration

1. Set up Context7

   Context7 can be set up via CLI or as an MCP server. Choose your method:

   CLI

   Install the Context7 CLI to query docs directly from your terminal.

   One-off installation via npx:

   npx ctx7 --help

   Global installation:

   npm install -g ctx7
   ctx7 --version

   Requires Node.js 18 or higher.

   The CLI provides three main capabilities:

   • Fetch docs — query specific documentation sections
   • Manage skills — generate AI agent skills for auto-invocation
   • Configure MCP — set up MCP server integration
   MCP Server

   Context7 is configured as an MCP server in your coding agent. You can also add it directly from context7.com. Choose your tool:

   Claude Code

   Run one of the following commands in your terminal:

   Local (stdio):

   claude mcp add --scope user context7 -- npx -y @upstash/context7-mcp

   Remote (HTTP):

   claude mcp add --scope user --transport http context7 https://mcp.context7.com/mcp

   To verify the server was added:

   claude mcp list

   Cursor

   1. Open Settings > Cursor Settings > MCP and click Add New Global MCP Server.

      Paste one of the following configs:

      Remote server:

      {
        "mcpServers": {
          "context7": {
            "url": "https://mcp.context7.com/mcp"
          }
        }
      }

      Local server:

      {
        "mcpServers": {
          "context7": {
            "command": "npx",
            "args": ["-y", "@upstash/context7-mcp"]
          }
        }
      }

   2. Restart Cursor.

   Claude Desktop

   The easiest way is to install Context7 directly from the Claude Desktop interface:

   1. Open Claude Desktop and go to Customize > Connectors.
   2. Search for Context7 and click Install.

   Alternatively, configure it manually via Settings > Developer > Edit Config and add to claude_desktop_config.json:

   {
     "mcpServers": {
       "context7": {
         "command": "npx",
         "args": ["-y", "@upstash/context7-mcp"]
       }
     }
   }

   Restart Claude Desktop after saving.

   Windsurf

   1. Open Settings > Developer > Edit Config and open windsurf_config.json.

   2. Add the following config and save:

      {
        "mcpServers": {
          "context7": {
            "command": "npx",
            "args": ["-y", "@upstash/context7-mcp"]
          }
        }
      }

   3. Restart Windsurf.

2. Query Scalekit docs

   Using CLI

   Querying Scalekit docs via CLI is a two-step process.

   Step 1 — Resolve Scalekit library:

   ctx7 library scalekit "How to set up SSO"
   ctx7 library scalekit "SCIM user provisioning"
   ctx7 library scalekit "MCP authentication setup"

   Expected result for library selection:

   Field	Description
   Library ID	/scalekit-inc/developer-docs
   Code Snippets	High (hundreds of indexed examples)
   Source Reputation	High
   Benchmark Score	Quality score from 0 to 100

   Step 2 — Fetch Scalekit docs:

   # SSO queries
   ctx7 docs /scalekit-inc/developer-docs "How to set up SSO with Scalekit"
   ctx7 docs /scalekit-inc/developer-docs "Configure SAML for enterprise SSO"
   
   # SCIM queries
   ctx7 docs /scalekit-inc/developer-docs "How to provision users with SCIM"
   ctx7 docs /scalekit-inc/developer-docs "Set up SCIM for Active Directory"
   
   # MCP auth queries
   ctx7 docs /scalekit-inc/developer-docs "Add MCP auth to my server"
   ctx7 docs /scalekit-inc/developer-docs "Configure agent authentication"
   
   # Connected accounts queries
   ctx7 docs /scalekit-inc/developer-docs "Configure connected accounts for GitHub OAuth"
   ctx7 docs /scalekit-inc/developer-docs "Set up Google OAuth integration"
   
   # JSON output for scripting
   ctx7 docs /scalekit-inc/developer-docs "SSO setup" --json
   
   # Pipe to other tools
   ctx7 docs /scalekit-inc/developer-docs "SCIM provisioning" | head -50

   Note

   Library IDs always start with /. Running ctx7 docs scalekit "SSO" will fail — always use the full ID: /scalekit-inc/developer-docs.

   Using MCP Server

   Once Context7 is running, add use context7 to any prompt where you want current Scalekit documentation injected automatically.

   General Scalekit queries:

   How do I set up SSO with Scalekit? use context7

   Show me how to provision users with SCIM using Scalekit. use context7

   Target Scalekit docs directly using the library path:

   use library /scalekit-inc/developer-docs for how to add MCP auth to my server

   Combine with version or feature specificity:

   How do I configure connected accounts for GitHub OAuth with Scalekit? use context7

3. Auto-invoke Context7 (optional)

   Configure your coding agent to always use Context7 for library and API questions — no need to add “use context7” manually each time.

   CLI

   Use ctx7 setup --cli to configure Context7 for AI coding agents. This installs a docs skill that guides the agent to use ctx7 library and ctx7 docs commands for Scalekit documentation.

   Setup commands:

   # Interactive setup (prompts for agent)
   ctx7 setup --cli
   
   # Direct setup for specific agents
   ctx7 setup --cli --claude       # Claude Code (~/.claude/skills)
   ctx7 setup --cli --cursor       # Cursor (~/.cursor/skills)
   ctx7 setup --cli --universal    # Universal (~/.config/agents/skills)
   
   # Project-specific setup (default is global)
   ctx7 setup --cli --project
   
   # Skip confirmation prompts
   ctx7 setup --cli --yes

   What gets installed — CLI + Skills mode:

   File	Purpose
   Agent skills directory	docs skill — guides the agent to use ctx7 library and ctx7 docs

   When the docs skill is installed, your AI agent will automatically use ctx7 commands to fetch accurate Scalekit documentation when asked about SSO, SCIM, MCP auth, or other Scalekit features.

   MCP Server

   Configure your coding agent to always use Context7 for library and API questions — no need to add “use context7” manually each time.

   Claude Code

   Add the following rule to your project’s CLAUDE.md file:

   Always use Context7 MCP when I need library or API documentation, code generation, or setup and configuration steps.

   This applies project-wide. For a global rule, add it to ~/.claude/CLAUDE.md.

   Cursor

   Open Settings > Cursor Settings > Rules and add:

   Always use Context7 MCP when I need library or API documentation, code generation, or setup and configuration steps.

4. Increase rate limits with an API key

   The free tier of Context7 has rate limits. For heavier usage or team environments, get a free API key from context7.com/dashboard and add it to your configuration.

   MCP Server
   Claude Code

   Local:

   claude mcp add --scope user context7 -- npx -y @upstash/context7-mcp --api-key YOUR_API_KEY

   Remote:

   claude mcp add --scope user --header "CONTEXT7_API_KEY: YOUR_API_KEY" --transport http context7 https://mcp.context7.com/mcp

   Cursor

   Remote server with API key:

   {
     "mcpServers": {
       "context7": {
         "url": "https://mcp.context7.com/mcp",
         "headers": {
           "CONTEXT7_API_KEY": "YOUR_API_KEY"
         }
       }
     }
   }

   Local server with API key:

   {
     "mcpServers": {
       "context7": {
         "command": "npx",
         "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]
       }
     }
   }

   Claude Desktop / Windsurf

   {
     "mcpServers": {
       "context7": {
         "command": "npx",
         "args": ["-y", "@upstash/context7-mcp", "--api-key", "YOUR_API_KEY"]
       }
     }
   }

   CLI

   Set an API key via environment variable for higher rate limits:

   # Set API key for current session
   export CONTEXT7_API_KEY=your_key
   
   # Add to ~/.bashrc or ~/.zshrc for permanent use
   echo 'export CONTEXT7_API_KEY=your_key' >> ~/.bashrc

   API keys start with ctx7sk. If authentication fails with a 401 error, verify the key format matches your method (HTTP header for MCP, environment variable for CLI).

   Note

   Most CLI commands work without authentication. Login (ctx7 login) is only required for skill generation and higher rate limits on documentation commands.

Note

For help with common issues including timeouts, module errors, rate limits, and proxy configuration, see the Context7 troubleshooting guide.