SerenQuantDocs
Sign up
Sign up
© 2026 SerenQuant. All rights reserved.
DocsPrivacyTermsStatusSupport
Docs
Documentation
Start here
Overview
Guide library
GuidesGetting Started: APIGetting Started: MCPAuth + Workspace ScopesAccount and Workspace ManagementMarkets workspaceMarkets Symbol WorkspaceMarket Guides and Beta ScopeFutures ReadinessResearch WorkflowResearch Workbench, Pipeline, and ExperimentsResearch Specialist MethodsResearch Context SurfacesBacktests Run LifecycleBacktests Run Detail and CompareStrategy Sweeps and OptimizerExecution WorkflowProviders and BenchmarkingSettings and Runtime ConfigAgent WorkbenchNews WorkflowDatasets WorkflowGlobal Language SelectionMFA Getting StartedMFA Recovery + Device LossMFA Trusted DevicesMFA API ReferenceLLM Market Analysis LoopStrategy Generation + Backtest LoopPromotion + Risk Guardrails
Reference
API ReferenceMCP Reference
Lifecycle
Changelog
  1. Docs/
  2. Guides/
  3. Getting Started: MCP
Public docs

Guide: Getting Started MCP

Integrate LLM agents with SerenQuant MCP resources and tools safely.

Before you start

  • Issue or select an MCP service-account token that only includes the scopes your agent actually needs.
  • Keep your workspace header ready alongside the bearer token so MCP calls resolve the right tenancy context.
  • The live gateway endpoints are /api/v1/mcp/messages for JSON-RPC and /api/v1/mcp/sse for event streaming.
  • Start with live read-only tools and resources before you allow any higher-risk autonomous actions.

1. Initialize the MCP session

Send an initialize request first so the server returns workspace context and advertised capabilities.

cURL
TypeScript
Python
curl --request POST \
  --url "$SERENQUANT_BASE_URL/api/v1/mcp/messages" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer $SERENQUANT_API_TOKEN" \
  --header "X-Workspace-Id: $SERENQUANT_WORKSPACE_ID" \
  --header "Content-Type: application/json" \
  --data '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "initialize",
  "params": {}
}'

2. Call a read-only tool

After initialize, make one safe tools/call request so you can confirm scope, routing, and payload handling end to end.

cURL
TypeScript
Python
curl --request POST \
  --url "$SERENQUANT_BASE_URL/api/v1/mcp/messages" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer $SERENQUANT_API_TOKEN" \
  --header "X-Workspace-Id: $SERENQUANT_WORKSPACE_ID" \
  --header "Content-Type: application/json" \
  --data '{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "markets.snapshot.get",
    "arguments": {}
  }
}'

What success looks like

  • Initialize returns a workspace_id plus the methods your client can rely on.
  • Your first tools/call request completes without expanding scopes or switching to higher-risk write tools.
  • You can now move into /docs/mcp to inspect live vs beta status, bridge metadata, and exact schemas per item.
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "workspace_id": "ws-123",
    "capabilities": {
      "methods": ["tools/list", "tools/call", "resources/list"]
    }
  }
}

Next steps

Open MCP Reference

Browse methods, tools, resources, rollout status, and bridge examples per item.

Review Auth Model

Check how service-account tokens, workspace headers, and protected flows interact.

Check Release Notes

Watch for contract changes before you promote agent workflows or long-lived integrations.

Last updated

Mar 24, 2026

Feedback

Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.

Open feedback issue
Previous
Getting Started: API
Next
Auth + Workspace Scopes
On this page

Jump to the section you need without losing your place.

  • Before you start
  • 1. Initialize the MCP session
  • 2. Call a read-only tool
  • What success looks like
  • Next steps
Last updated

Mar 24, 2026

Feedback

Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.

Open feedback issue