praveenmanikandan/spera

Create, edit, repair, and compile structured Spera custom nodes through the remote Spera MCP server. Use when a user asks Claude Code, Codex, or Cursor to build or modify a Spera custom node. Requires spera-foundations, progressive SDK discovery, canonical source and field hashes, create-once persistence, explicit compilation, and a five-real-compile limit; never claims behavior verification or deploys bots.

Create, edit, fork, repair, compile, and configure reusable Spera graph modules through the remote Spera MCP server. Use when a user asks Claude Code, Codex, or Cursor to build or modify a Spera module. Requires spera-foundations, exact revisions, repair-in-place, and module ports only after a clean compile; never deploys or operates bots.

Create, edit, fork, repair, and compile Spera strategy graphs through the remote Spera MCP server. Use when a user asks Claude Code, Codex, or Cursor to build or modify a Spera strategy. Requires the spera-foundations rules, exact artifact revisions, state tokens, idempotency, repair-in-place, and a verified compile receipt; never deploys or operates bots.

Deliver a verified Spera strategy across authoring, exact-revision backtesting, project knowledge, and artifact documentation through the remote Spera MCP server. Use when Claude Code, Codex, or Cursor must complete a strategy handoff with durable cross-client continuity and evidence receipts. Composes the dedicated Spera skills and stops before deployment or bot lifecycle actions.

Safely connect to Spera, inspect authorized projects and artifacts, resume durable workflows, and enforce Spera MCP authorization, revision, citation, receipt, retry, polling, and stopping rules. Use for Spera MCP setup or shared behavior behind strategy, module, custom-node, backtest, project-knowledge, documentation, or delivery workflows in Claude Code, Codex, or Cursor. Never use it for bots, Fleet, deployment, exchange credentials, or trading lifecycle actions.

Run bounded quick or durable deep backtests for exact Spera strategy revisions through the remote Spera MCP server. Use when a user asks Claude Code, Codex, or Cursor to test, evaluate, inspect trades/equity, poll, resume, or cancel a Spera backtest. Requires spera-foundations, exact revisions, normalized settings, bounded polling and pagination, and evidence-qualified summaries; never deploys or operates bots.

Read, research, create, and revise project-scoped Markdown knowledge through the remote Spera MCP server. Use when Claude Code, Codex, or Cursor must inspect a project manifest, answer from project files with revision-pinned citations, update an ordinary Markdown file, or propose and accept a protected STRATEGY.md change. Requires spera-foundations, exact paths and revisions, receipts, and explicit acceptance for STRATEGY.md; never deploys or operates bots.

Read and update exact Spera strategy, module, or custom-node documentation through the remote Spera MCP server. Use when Claude Code, Codex, or Cursor must document an artifact with optimistic revision safety, project citations, and receipt-grounded compile or backtest claims. Requires spera-foundations and a single verified documentation write; never fabricates evidence or deploys bots.