Start building free
Connect your assistant

Build strategies by asking.

Pick the app you already use. Approve once. Then ask — it builds, compiles, and backtests in your Spera account.

Pick your app

Connect VS Code

One click opens VS Code with the Spera server already filled in. You approve, then reload the window.

Install in VS Code

  1. Click Install in VS Code. VS Code opens and pre-fills the Spera server.

  2. Sign in to Spera and approve the permissions.

  3. Reload the window, then start a new chat.

You’re done when The MCP panel shows Spera as connected.

Then ask this
What Spera projects do I have?

Spera tools appear, and the assistant lists your projects — or says you have none.

Button did nothing, or you use Insiders?

The install link opens VS Code Stable. This command does the same thing from a terminal and writes to your user profile — swap code for code-insiders on Insiders.

code --add-mcp '{"name":"spera","type":"http","url":"https://api.spera.bot/mcp?mode=authoring"}'

Need a free Spera account first? Create one. The connector has nothing to attach to without it.

02·After you connect

Ask. It lands.

You ask in VS Code. Spera builds, compiles, and backtests the strategy in your account.

You ask

In VS Code

Build an EMA 20/50 crossover on BTC/USDT 4h and backtest it.

It lands

EMA 20/50 crossover

BTC/USDT · 4h

  • compiled · 0 errorsreceipt kind artifact_compiled
  • backtested · exact revisionreceipt kind backtest_completed
  • documented · citedreceipt kind documentation_applied

Each step returns a receipt you can check, then opens in the builder. See a full run.

Never crosses: Deploy a bot · Read exchange keys · Move money. No tool for these exists on the server.

You describe a strategy in your AI app. It arrives in your Spera account as a real strategy — compiled, backtested, and documented, each step returning a receipt you can check. Bot deployment, exchange keys, and moving money never cross the connection, because no tool for them exists on the server.

03·What you grant

Ten permissions. None can trade.

These are the exact strings on the sign-in screen. Hold this page next to the dialog and check that they match.

No scope exists for
  • Deploying a bot or starting live trading
  • Reading or using your exchange API keys
  • Moving, withdrawing, or spending money
  • Reaching any account except your own
  • spera:context:read

    See which projects and artifacts you have

  • spera:artifact:read

    Open a strategy, module, or custom node

  • spera:artifact:write

    Create and edit them

  • spera:backtest:run

    Start a backtest on an exact revision

  • spera:backtest:read

    Read the trades and metrics that come back

  • spera:backtest:cancel

    Stop one it started

  • spera:knowledge:read

    Read your project knowledge files

  • spera:knowledge:write

    Write them (STRATEGY.md needs your approval)

  • spera:documentation:read

    Read artifact documentation

  • spera:documentation:write

    Write artifact documentation

Approving is per-account and revocable at any time. Read each one in full.

04·Go deeper

The manual.

Eight pages, in reading order — for after you are connected, or when something does not.

What the connector isPlain language, and the hard boundariesConnect your assistantEvery client, including the ones not listed aboveWhat you're approvingEach permission in plain languageWhat to ask forPrompts that work, and what it checks before startingWhat you see in chatResult cards, the trust ladder, and the text versionThree things worth doing firstBuild, branch, and hand over a strategy end to endEvery toolAll of them, grouped, with the permission each needsTroubleshootingNothing appeared, unauthorized, or read-only
Read the manual