Connection guide

Connect the PrimeSync AI Studio plugin.

PrimeSync AI Studio is an MCP plugin that adds strategy-building and validation tools to your AI assistant. Use the same production endpoint in any client that supports MCP Streamable HTTP and OAuth 2.1 with PKCE. The client must support dynamic client registration, authorization-code flow, refresh tokens, and resource-bound access tokens.

PrimeSync AI Studio analytical MCP tools require a Studio subscription: USD 25/month or USD 250/year, with 50 shared analysis jobs per calendar month. Your AI provider's plan requirements and usage limits still apply.

Plugin connection URL (MCP)https://ai.primesync.me/mcp/v1Endpoint contract v1 · MCP protocol 2026-07-28 · OAuth required

Before you connect

  1. Read the public tool manifest and confirm that the tools match your intended work.
  2. Add the endpoint through your client's MCP or connector settings. Choose OAuth when the client asks for authentication.
  3. PrimeSync will show the requested permissions separately. Uncheck any scope you do not want to grant.
  4. Test with a throwaway strategy first. Never include broker keys, exchange keys, account credentials, or live order instructions.
  5. Open Account & activity to see tool-call metadata or revoke a connection at any time.

If a tool fails or keeps asking you to generate

A saved connector can retain an older tool list after the service is updated. Refresh its tools, or reconnect the same MCP URL when your client has no refresh option. The current service exposes separately named research and memory operations, alongside strategy building, static audits, backtest imports and Monte Carlo. Inspect the public tool manifest for the current list. You do not need to enable memory to build or validate a strategy.

The builder must accept strategyProperties and candidate code. The audit must accept approvedBlueprint and approvedBlueprintHash. If those fields are absent, the client has an outdated definition. A legacy audit can still return an unverified static review; it cannot establish approval or qualify a final candidate.

When a blueprint is ready, the connected AI authors the code and submits it for audit in the same interaction. An authoring contract is not generated code. Compilation, backtests and fresh exports remain external evidence; Studio does not run TradingView.

Omitting the simulation count uses up to 30,000 simulations within the compute budget, with the actual count and any reduction disclosed. Explicit counts are never silently reduced, and trades are never truncated to fit. Supply the original trade count to check dataset completeness. Inspect the current input and output schemas if a client reports an argument error.

ChatGPT

Visit the homepage and click Open in ChatGPT. Follow the connection steps and authorize with the Whop account used for your Studio subscription. For manual MCP setup, use the production endpoint above with Streamable HTTP and OAuth.

Claude

Open Settings → Connectors, add a custom connector, enter the production endpoint above, and select Connect. Claude uses dynamic client registration, PKCE S256, and its hosted callback at https://claude.ai/api/mcp/auth_callback.

Official Claude connector guide ↗

Connection FAQ

Does my subscription include MCP access?

Active PrimeSync AI Studio subscriptions include analytical MCP access and 50 shared analysis jobs per calendar month across ChatGPT and Claude. Paid access and analysis metering are enabled. Website question credits are counted separately.

Which email should I use?

Open Account & activity and check that the displayed Whop email matches the account used to purchase Studio. Then return to the homepage and click Open in ChatGPT. Your ChatGPT or Claude email can differ from your Whop email.

What if Whop says “Authorization request is invalid”?

Close the failed authorization page and start a fresh connection from the homepage's Open in ChatGPT link. Sign in with your Studio purchase account. If it still fails, contact support with a screenshot, your Whop purchase email or order ID, and the approximate time of the attempt. Never send passwords, authorization codes, or tokens.

Permissions

strategies:build

New strategies, indicators, experiments, models, conversions, and logic-preserving repairs.

strategies:audit

Rule-to-code audit of supplied Pine Script or Python.

strategies:validate

TradingView result analysis, Monte Carlo, and robustness validation.

Open AI Strategy mode

Starts from a blank trader-owned model. It may propose genuinely different architectures and evidence-backed hypotheses, but it never inserts PrimeSync.me logic, presets, thresholds, sessions, risk values, arrows, or levels unless you explicitly request and approve them.

Preserve Existing Logic mode

Starts from complete code you supply. Repairs and conversions protect the approved logic, visuals, alerts, levels, sizing, timing, and order behavior outside the exact change scope you authorize.

Finished-result boundary

Generated Pine or Python is a candidate. A compatibility comparison remains provisional. The final analytical result uses final_candidate_selection only after caller-attested code/data fingerprints, folds, untouched holdout, realistic cost stress, parameter sensitivity, compilation, fresh exports, costs, and mapping all pass; if no candidate is robustly better, the unchanged baseline remains preferred. PrimeSync does not independently compile code or prove code-to-export provenance.

Verification stages

PrimeSync separates STATIC PASS, STATIC REVIEW REQUIRED, COMPILE REPORTED BY USER, BACKTEST EVIDENCE ACCEPTED, and ROBUSTNESS REVIEWED. Static inspection never claims that TradingView compiled or executed the code.

Research comparisons

Lowest drawdown and highest win rate rank by those metrics, after the disclosed acceptance checks. Net P&L uses the supplied P&L column within each dataset. Balanced and robustness objectives expose their fixed formulas. Filtered training trades are reconstructed candidates: their descriptive Monte Carlo results do not establish a probability of beating a baseline. Fresh code-specific exports over the same declared evaluation period are still required.

Backtest import

For Pine, compile the exact blueprint-hash-marked code in TradingView and export a fresh List of Trades CSV. For Python, provide one row per closed trade and confirm syntax plus execution of that exact code. Then call primesync_import_backtest and carry its dataset fingerprint together with the candidate ID, code version, audited code-content fingerprint, and parameter set. Evidence acceptance requires matching blueprint hashes, a clean static pass, reported runtime validation, a fresh export, confirmed costs, matching effective Properties and mapping, valid chronology, and no parser warnings.

Private continuity

The full research ledger stays client-managed. Optional memory can save confirmed preferences and minimal strategy summaries under your authenticated account. It never automatically saves code, CSVs, or complete conversations. Remembered results are not fresh validation evidence.

Alert support

Studio can help your connected AI add Pine Script alert logic to a strategy or indicator using the conditions you approve. Specify which events should trigger an alert, when it should fire, and which message fields you need. Alert setup is available on request; it is not automatically included in every strategy build.

Preserve Existing Logic mode protects existing alerts outside your approved changes. The static audit includes basic checks for matching alert and chart-arrow conditions. These checks do not verify every alert path or confirm live notification delivery.

  1. Ask for the alert events, timing and message content you want. Distinguish a confirmed signal from an order fill when defining the trigger.
  2. Compile and apply the completed script in TradingView. Create an alert there, select the appropriate script condition, and configure its delivery settings.
  3. Test the notification and compare its timing and content with the expected chart event before relying on it.

TradingView runs the alerts and handles their delivery. The MCP does not monitor live prices, create or activate alerts in your TradingView account, or send notifications itself.

Example request: “Add alerts for my approved entry conditions. Include the symbol, timeframe and direction, preserve my strategy rules, and explain how to activate and test the alerts in TradingView.”

Strategy Properties: P0–P4 or Custom

Approve the account and execution model before applying a strategy. These Properties profiles are independent of PrimeSync Max's V1–V12 entry profiles. Studio offers them when requested; it does not insert PrimeSync trading logic into a new strategy.

Reference simulation settings — fees are per side
ProfileMarketCapitalOrder sizeCommissionSlippageLong / short margin
P0 · LegacyUniversal comparison1,000,000 · chart currency100% of equity0%0 ticks0% / 0%
P1ES, NQ, CL, GC200,000 USD1 contract3 USD / contract2 ticks20% / 20%
P2MNQ, MES, MGC10,000 USD1 contract0.96 USD / contract2 ticks20% / 20%
P3US stocks10,000 USD100% of equity0.02%2 ticks50% / 50%
P4CFDs100,000 USD · 50,000 alternative100% of equity0%0 ticks20% / 20%

All five reference profiles use pyramiding 1, calculation on bar close, no recalculation after fills, next-tick order processing, Bar Magnifier off, and limit-fill assumption 0. These are starting assumptions; confirm every override. P0 disables margin checks. P0 and P4 are comparison-only models and omit realistic costs. They do not reproduce prop-firm loss rules or guarantee an earlier equity curve.

  1. Confirm the exact symbol/feed, timeframe, session, test dates and account currency. Select a reference profile or supply every Custom value.
  2. Approve capital, order sizing and its authority, fees, slippage, margin and execution. Percent of equity is allocation, not risk at the stop. An order's qty can override the default order size.
  3. Studio binds the snapshot to the blueprint and provides a Pine declaration for the connected AI to incorporate. An Inputs dropdown cannot rewrite TradingView's Properties tab. Existing code changes remain limited to the scope you approve.
  4. Compile the exact code, verify the effective Properties in TradingView, then export fresh trades. Send strategyProperties, propertiesConfirmed and the approved Properties fingerprint with the CSV. A trades CSV alone cannot confirm these settings.
  5. Carry the importer's Properties fingerprint into each candidate. Final selection requires confirmed, matching configurations with realistic costs; mixed settings need a comparable rerun. Existing callers without a snapshot can inspect provisional results but cannot complete final selection.

For futures, the emulator's approximate margin requirement is price × point value × quantity × margin percentage / 100. A 10,000 USD P2 account can still be too small for a particular MNQ price. Futures and CFDs can produce different trades because of contract value, feed, session, fees and fill assumptions; increasing capital only addresses funding eligibility.

Example request: “Use P2 for my MNQ strategy. Confirm its Properties and any overrides, preserve my entry logic, and carry the applied settings through the audit, CSV import and Monte Carlo comparison.”

Hosted safety limits

CSV structure and research or Monte Carlo work are bounded before computation. One request may resample at most 25,000,000 aggregate trade observations across every baseline, candidate, and cost-stress path. Oversized requests return a specific safe limit and recovery action rather than silently truncating trades or risking a hosted timeout.

Optional personal memory

Studio tools work without optional memory. Analytical tools require a Studio subscription; imports and memory operations do not consume analysis jobs. To use the individually named memory tools, reconnect if necessary and select the optional memory:manage permission. It is unchecked by default. Then explicitly ask Studio to remember the preferences or project summary you choose; granting permission alone does not turn memory on.

For example: “Remember that I prefer Arabic, beginner explanations, and Pine Script.” For a temporary override: “Use Python for this request only.” Say “Continue my strategy” to resume; if several summaries exist, Studio asks which one. Use Account memory controls to inspect, export, reset, or turn off and erase memory. Correction is also available through the preference-update and project-update tools.

To continue without memory, carry the exported project's requestContext into the next request. It contains the preferences and portable summary in the input format. Deleting server memory does not delete copies you exported. If supplied baseline code differs from the remembered version, Studio asks you to supply the current source or confirm a temporary branch.

Preferences guide communication and candidate comparison; risk, sessions, and execution still need strategy-specific approval. Custom objective weights express your intent; a tool without that weighted objective asks you to choose a supported metric. Fixed onboarding questions and summary labels are available in English, Arabic and Hebrew. The connected AI translates open-ended details and renders code-comment style without changing tested code. Raw code and complete evidence must still be supplied when required.

Connection limit

Each PrimeSync account can keep up to three active OAuth connections. Revoke an old device or client from Account & activity before adding another.

Ask PrimeSync questions

Free visitors have 5 website questions per month. An active monthly or annual Studio subscription includes 100 website questions per month. Connect the Whop account that owns your Studio subscription. Question allowances reset on the first day of each UTC calendar month and are separate from the 50 monthly Studio analysis jobs.

MCP access

Signing in or joining the Whop community does not by itself activate a paid Studio plan. PrimeSync Basic, Pro and Max memberships and website question credits are separate from Studio subscriptions.

Studio analytical MCP tools require an active Studio subscription and share a 50-job monthly allowance across ChatGPT and Claude. CSV imports and memory operations do not consume analysis jobs. Studio analyses do not consume website-assistant question credits. Standard connection security and rate limits still apply.

Studio analysis allowance

The monthly and annual Studio plans each provide 50 analysis jobs per calendar month, shared across ChatGPT and Claude under the same Whop user ID. The account email used by your AI client does not have to match. Allowances reset at 00:00 UTC on the first day of the month; unused jobs do not roll over and annual subscriptions do not release 600 jobs upfront.

One completed code build returned by Studio, static audit report, dataset research job, or Monte Carlo run counts as one job. Connected-AI code must be submitted back to Strategy Builder for static checking and a usage receipt before delivery; writing code only in chat cannot update the server counter. A Pine-and-Python build in one request counts once. Code builds with failed static checks remain uncharged; warnings are disclosed and do not mean compilation or backtesting passed. A single Monte Carlo comparison containing several candidates counts once. Separate analytical stages count separately: a build, audit and Monte Carlo run can use three jobs.

CSV imports, memory operations, clarifying questions, generation instructions without code, missing-data responses and tool errors do not consume analyses. An audit that correctly identifies problems is a completed report. An identical analytical request with the same effective inputs in the same month is not counted twice. Changing inputs or parameters creates a new job.

Running jobs temporarily reserve capacity. Failed jobs release it; interrupted reservations expire after five minutes. At the limit, new analytical jobs stop without any automatic overage charge. Ask PrimeSync includes a 25-job top-up for USD 10 when checkout is activated. Each purchase requires your approval in Whop; use the same Whop account as Studio. A checkout return is not payment confirmation. Purchased jobs are added only after a verified successful payment, carry forward, and are used after the monthly allowance. Active Studio access is still required. A refunded pack is withheld pending any necessary support reconciliation. View completed, running and available jobs in Account & activity.

Studio paid access and analysis metering are enabled. Sign in with the Whop account that owns your Studio subscription. Studio checks the membership at each analytical request; an unavailable verification service returns an error rather than guessing that a purchase is valid. Cancellation at period end retains access while the membership remains valid; expired or revoked access does not reset or erase prior usage.