AI智能体与知识管理MCP服务

Seclai MCP Server

Connect AI-powered coding tools to Seclai using the Model Context Protocol. Manage your agents, knowledge bases, content sources, memory banks, evaluations, solutions, governance, alerts, models, and more directly from your editor or terminal.

Quick Start

Endpoint: https://mcp.seclai.com/mcp Transport: Streamable HTTP Auth: browser sign-in (OAuth), or an X-API-Key header

You need a Seclai account with API access.

Sign in from your client (recommended)

The server is an OAuth 2.1 authorization server with dynamic client registration and PKCE, so any client implementing the MCP authorization spec can register itself and open a browser sign-in. No API key to create, paste, or rotate, and no secret sitting in a config file.

Add the URL with no headers block at all and the client handles the rest. Most clients take this shape; each client's section below gives its exact format:

{
  "mcpServers": {
    "seclai": {
      "type": "streamable-http",
      "url": "https://mcp.seclai.com/mcp"
    }
  }
}

Claude Code, VS Code, Cursor and Codex CLI all support browser sign-in today. Claude (claude.ai and Desktop) adds the URL as a custom connector instead; see below. If a client reports an expired or invalid token, clear its stored credentials for the server and reconnect — it will re-register automatically.

GET /.well-known/oauth-protected-resource/mcp
  resource:              https://mcp.seclai.com/mcp
  authorization_servers: https://mcp.seclai.com/

GET /.well-known/oauth-authorization-server
  authorization_endpoint:          /authorize
  token_endpoint:                  /token
  registration_endpoint:           /register     (dynamic client registration)
  grant_types_supported:           authorization_code, refresh_token
  code_challenge_methods_supported: S256
  scopes_supported:                openid

API key

For clients without OAuth support, or for CI and scripted use, create a key at seclai.com → Account Settings → API Keys and send it as X-API-Key. Take your client's entry from its section below and add a headers object to it:

"headers": {
  "X-API-Key": "YOUR_API_KEY"
}

Codex takes http_headers = { "X-API-Key" = "YOUR_API_KEY" } in its TOML entry, and Claude Code's CLI takes --header "X-API-Key: YOUR_API_KEY".

Keys must be user-scoped; keys created recently are user-scoped automatically.

To target a specific organization, include the X-Account-Id header.

On the URL. https://mcp.seclai.com/mcp is the canonical resource the server advertises in its protected-resource metadata. The bare host also routes, but prefer the /mcp form — OAuth clients derive the token audience from the resource identifier.

Claude (claude.ai and Desktop)

Add Seclai to Claude as a custom connector:

1. Go to Customize → Connectors and click Add custom connector
2. Enter the URL https://mcp.seclai.com/mcp and click Add
3. Click Connect and sign in with your Seclai account

On Team and Enterprise plans, an organization Owner adds the connector under Organization settings → Connectors (Add → Custom), and each member then clicks Connect under Customize → Connectors to sign in with their own Seclai account.

Claude Code (CLI)

claude mcp add seclai \
  --transport http \
  "https://mcp.seclai.com/mcp"

Claude Code opens the browser sign-in on first use. Run /mcp inside Claude Code to check the connection or re-authenticate.

Or copy examples/claude-code.json to .mcp.json in your project root.

Cursor

Copy examples/cursor.json to .cursor/mcp.json in your project root.

Or add manually: Settings → MCP → Add new MCP server → set type to streamable-http and URL to https://mcp.seclai.com/mcp.

Windsurf

Copy examples/windsurf.json to ~/.codeium/windsurf/mcp_config.json.

VS Code (GitHub Copilot)

Copy examples/vscode.json to .vscode/mcp.json in your project, or run MCP: Open User Configuration for a user-level install. VS Code uses servers rather than mcpServers, and "type": "http":

{
  "servers": {
    "seclai": {
      "type": "http",
      "url": "https://mcp.seclai.com/mcp"
    }
  }
}

Kiro

Copy examples/kiro.json to .kiro/settings/mcp.json in your project, or ~/.kiro/settings/mcp.json for all projects.

Roo Code

Copy examples/roo.json to .roo/mcp.json in your project root. For a global install, use Roo's MCP Servers → Edit Global MCP panel.

Cline

Cline stores MCP settings in cline_mcp_settings.json inside its VS Code extension storage, so edit it through the UI rather than by path: open the Cline panel → MCP Servers → Configure MCP Servers, then add the block below (also in examples/cline.json). Cline names this transport streamableHttp; without a type it falls back to SSE:

{
  "mcpServers": {
    "seclai": {
      "type": "streamableHttp",
      "url": "https://mcp.seclai.com/mcp"
    }
  }
}

Gemini CLI

Add to .gemini/settings.json in your project, or ~/.gemini/settings.json globally (also in examples/gemini-cli.json). Gemini CLI names the field httpUrl, not url:

{
  "mcpServers": {
    "seclai": {
      "httpUrl": "https://mcp.seclai.com/mcp"
    }
  }
}

Codex CLI

Codex uses TOML at ~/.codex/config.toml, and can hold the OAuth credentials itself — see examples/codex.toml:

[mcp_servers.seclai]
url = "https://mcp.seclai.com/mcp"
auth = "oauth"

Then run codex mcp login seclai to complete sign-in. On older Codex builds that only discover stdio servers, add experimental_use_rmcp_client = true above the server block.

Antigravity

Copy examples/antigravity.json to ~/.gemini/config/mcp_config.json, or .agents/mcp_config.json in your workspace. Antigravity names the field serverUrl:

{
  "mcpServers": {
    "seclai": {
      "serverUrl": "https://mcp.seclai.com/mcp"
    }
  }
}

Other Clients

Any client supporting Streamable HTTP MCP transport works. Configure:

The URL field is not spelled the same everywhere — url in most clients, httpUrl in Gemini CLI, serverUrl in Antigravity — and VS Code uses servers where everyone else uses mcpServers.

Available Tools

Agents

Agent Runs

Agent Inputs

Call get_agent_attachment_references before staging uploads — it reports whether the agent accepts files and the names or patterns a run-time batch must satisfy.

Agent AI Assistant

Evaluations

Knowledge Bases

Knowledge Base Chat

Content Sources

Source Exports

Source Embedding Migrations

Memory Banks

Memory Bank AI

Solutions

Governance

Alerts

Models

Playground Experiments

Account & Organization

Resource Exports

Transfers

Agent Email — Domains

Agent Email — Inbound

MCP Clients

Seclai agents can call other MCP servers. These tools manage those saved connections — the Seclai server acting as an MCP client itself.

Human-in-the-Loop

Cloud Drives

Search

Resources

Usage Examples

Once connected, interact with Seclai through natural language:

"Show me all my Seclai agents"

"Create a new agent called 'Daily News Digest' with a schedule trigger and the summarizer template"

"Add a retrieval step before the display step in my Daily News Digest agent"

"Create a knowledge base called 'Podcast Archive' using my podcast sources"

"Show me all my content sources and change the news feed to poll hourly"

Agent Templates

When creating agents, specify a template for a pre-configured starting point:

Rate Limits

MCP calls are rate-limited per account based on your plan:

Exceeded calls return a retry_after value. Most AI assistants handle this automatically.

Troubleshooting

Links

• Full MCP Documentation
• API Keys
• Agent Concepts
• Agent Steps Reference
• REST API
• seclai.com

License

MIT