ManifoldBT Docs

com.manifoldbtPublished by manifoldbt.comOfficial publisherv0.8.0Updated Nov 7, 2026

Docs for writing manifoldbt backtests: DSL rules, signatures, examples and error fixes.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Read-only documentation server for the manifoldbt backtesting library, giving an assistant DSL rules, API signatures, examples and error explanations.

What you can do
  • Search the manifoldbt docs for DSL rules, indicator and API signatures, config fields and execution semantics
  • Explain engine error messages: what they mean, what caused them and how to fix them
  • Check which documentation version is covered and which licence tier each feature needs
  • List topics and return a complete runnable backtest script plus rule and fill-behaviour references
When to use it
Use it when writing or debugging manifoldbt backtest code or DSL expressions, or when the engine returns an error whose message names a rule rather than the mistake. It is a reference only, so it does not replace running backtests locally.
Requirements
A remote streamable HTTP endpoint; no package, account, API key or environment variable is declared. Backtests themselves run on the user's own machine with manifoldbt installed and the user's own data store.
Before you install
The documentation covers manifoldbt 0.32.0 only; older installed versions are not addressed. The server holds no engine or market data, so it cannot compile, validate or backtest anything, and it only reads documentation.

Installation

In SourceWeft

  1. Open ManifoldBT Docs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.manifoldbt%2Fdocs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "manifoldbt-docs": {
      "type": "http",
      "url": "https://mcp.manifoldbt.com/mcp"
    }
  }
}

Tools

4

search_docs

Search the manifoldbt documentation: DSL rules and pitfalls, indicator and API signatures, config fields, execution semantics (which price a stop or target fills at, which fee each fill pays, what a reversal counts as, which ddof an indicator uses), how to read result metrics honestly, and worked examples. Ask in natural language ('how do I reference another symbol', 'what happens when a bar gaps through my stop', 'is this Sharpe meaningful') or by name ('symbol_ref', 'warmup_bars').

Parameterslimitqueryrequired

explain_error

Explain an error returned by the manifoldbt engine: what it means, what caused it, and how to fix it. Paste the message verbatim. Use this before changing code in response to an engine error -- these messages name a rule rather than the mistake, and guessing wastes a round trip.

Parametersmessagerequired

get_capabilities

Which manifoldbt version this documentation covers, and which of the THREE licence tiers each feature needs. Check before writing code around sweeps, walk-forward, cross-exchange, the GPU or the tick layer: the first three refuse on Community, the last two on anything below Researcher -- and the two Researcher gates raise different exception types.

Takes no parameters.

list_topics

START HERE. Returns a complete, runnable backtest script (open a store, strategy, config, fees, run, read the metrics) plus the stateful-band, bracket-exit, higher-timeframe and cross-asset variants -- then the list of rules the engine enforces and of what a fill actually does (which fee a stop pays, where a gapped bracket fills, what a reversal counts as). One call replaces the eight searches every first script otherwise needs.

Takes no parameters.

Version history

1
  1. v0.8.0LatestNov 7, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.