Skip to main content
MCP keys use the nsk_mcp_ prefix and enforce dedicated rate limits and security boundaries separate from standard gateway API keys.

Key Format

Every Neosantara MCP key adheres to the following structure:
Example: nsk_mcp_4f8b9e2a1c3d4e5f6a7b8c9d0e1f2a3b

Supported Authentication Headers

The MCP endpoint (https://api.neosantara.xyz/v1/mcp) accepts keys via either of the following headers:
or

Creating Keys via Dashboard

  1. Navigate to the Neosantara Dashboard.
  2. Click Create MCP Key.
  3. Provide a descriptive label (for example: [MCP] Cursor IDE).
  4. Copy and store the key securely; it is displayed only once.

Creating Keys via API

Tier Quotas & Rate Limits

The MCP gateway applies rate limiting backed by sliding Redis counters to maintain server stability:
  1. RPM Limit: Request volume per minute per MCP API key.
  2. Daily Requests: Daily request volume quota per MCP API key across a 24-hour window.
  3. Active Key Limit: Each user account may provision up to 5 active MCP keys.
  4. Summary Token Guard: Maximum output tokens allowed when running audit summary tools (mcp_summary_max_tokens).

Next Steps