Getting started

There are two ways in: through an AI assistant (MCP) or from your own code (REST). Both use the same Cycles IQ account and the same limits.

With an AI assistant

Claude (claude.ai, the desktop and the mobile apps)

Open Cycles IQ in Claude's connector directory, or find it under Customize > Connectors in Claude.
Choose Connect. The Cycles IQ sign-in opens at auth.cyclesiq.com. Sign in, or sign up with e-mail and password or with Google. A new account is free and starts with the 30-day trial.
Back in Claude, switch the connector on in a chat and ask in plain language.

Without the directory, the same works as a custom connector: under Customize > Connectors choose Add custom connector and enter the address https://api.cyclesiq.com/mcp.

Three prompts to start with:

"What can the Cycles IQ connector do, and what does my plan allow?"
"Here are 300 daily closes: (your numbers). What is the dominant cycle, and where is it in its phase?"
"Store these values as my dataset 'sales', then scan it for cycles between 10 and 150 bars and show the three strongest."

Claude asks before it uses a tool for the first time. Fourteen of the fifteen tools only read or calculate. One writes: store_dataset creates a dataset of yours or replaces the one with the same name. See MCP tools.

Claude Code

claude mcp add --transport http cycles-iq https://api.cyclesiq.com/mcp

Then type /mcp in Claude Code, choose cycles-iq and authenticate: the same sign-in opens in your browser.

ChatGPT, Cursor and other MCP clients

Add a remote MCP server with the address https://api.cyclesiq.com/mcp (streamable HTTP). A client that supports the OAuth sign-in opens it for you.

If you already have an API key, a developer tool can connect without the browser sign-in: it sends the key in the header X-API-Key with every request. The key belongs to your account, so the plan, the limits, the count and your datasets are the same as with the sign-in. Create a key on the API page of the app, https://app.cyclesiq.com/account/api. Claude's own apps (web, desktop and mobile) send no headers: there, use the sign-in.

Claude Code:

claude mcp add --transport http cycles-iq https://api.cyclesiq.com/mcp --header "X-API-Key: YOUR_KEY"

Cursor (~/.cursor/mcp.json) and other clients that take a JSON configuration:

{
  "mcpServers": {
    "cycles-iq": {
      "url": "https://api.cyclesiq.com/mcp",
      "headers": { "X-API-Key": "YOUR_KEY" }
    }
  }
}

VS Code (.vscode/mcp.json) asks for the key once and keeps it out of the file:

{
  "inputs": [
    { "type": "promptString", "id": "cyclesiq-key", "description": "Cycles IQ API key", "password": true }
  ],
  "servers": {
    "cycles-iq": {
      "type": "http",
      "url": "https://api.cyclesiq.com/mcp",
      "headers": { "X-API-Key": "${input:cyclesiq-key}" }
    }
  }
}

A client that takes only an address can carry the key in it, the form older integrations use:

https://api.cyclesiq.com/mcp?api_key=YOUR_KEY

An address with a key ends up in browser histories, logs, screenshots and shared links, and anyone who has it uses your account. Use this form only where no header is possible, and replace the key on the API page if the address was shared. (A client can also pass the key in each tool's api_key parameter; then the key becomes part of the conversation, so prefer the header.)

Keep the key out of shared files, repositories and chats. A key calls the tools; it cannot create keys or change your account, and you revoke or replace it on the API page.

Where the data comes from

Cycles IQ analyses the series you give it. It provides no market data. The assistant brings the numbers: values you paste, a file, another connector (a market-data connector, for example), or a dataset you stored earlier. An analysis needs more than 100 values, oldest first.

From your own code

Sign up at app.cyclesiq.com and confirm your e-mail address.
Create an API key on the API page of the app.
Ask for your plan and limits:

curl -H "X-API-Key: YOUR_KEY" https://api.cyclesiq.com/api/me/limits

Analyse a series of your own (a JSON array of more than 100 numbers, oldest first):

curl -X POST "https://api.cyclesiq.com/api/cycles/CycleExplorer" \
  -H "X-API-Key: YOUR_KEY" -H "Content-Type: application/json" \
  -d "[101.2, 102.4, 101.9, ...]"

The answer names the dominant cycle: its length, amplitude and phase, and the bars to the next top and low. Concepts explains how to read it. Every route with its parameters is in the API reference at https://api.cyclesiq.com/apidocs.

An analysis that cannot be made is answered with an error status, never with a result of zeros. For a series you send: 400 when it is too short (send more than 100 values) or no cycle passes the limits (widen the length range or lower the Bartels limit). For a market analysed by id: 404 when it has no data, too little data or no cycle in the range; 400 for a bad date. The reason is in the body. Such a call costs no tokens.

The key can also travel as Authorization: Bearer YOUR_KEY, or as ?api_key=YOUR_KEY in the address, the form of older integrations. Prefer a header: an address with a key ends up in logs and browser histories.

MCP tools: what each tool does, with example prompts.
Plans and limits: the 30-day trial, the Free plan and what each plan allows.
FAQ: short answers to the questions asked most.

The answers are measurements and projections of cycles, not investment advice.

Answers of Cycles IQ are measurements and projections of cycles, not investment advice. Questions: support.