How to use AI in Investboard: A practical guide

A useful AI investing conversation starts with the rules you chose and the reasons you recorded. This guide shows how to bring both into Investboard's built-in AI or an external assistant, check a proposal, and return to your reasoning when it is time to review.

Choose your starting point

Use the route that fits the task in front of you. You can begin with a file and connect an assistant later.

The built-in assistant has its own portfolio tools. The external Investboard MCP connection exposes ten tools: seven for policy, status, checks and your records, plus three for portfolio holdings and analytics. Portfolio reads require portfolio:read and the matching feature access. An uploaded file gives an assistant only the text you share.

Investboard does not place, change or transmit orders. If your assistant also has a separate broker connection, that connection has its own permissions. Keep each proposed action attached to the tool that would perform it.

Before you start: check your mandate and data

Record your purpose, horizon, risk tolerance, allocation and review rules in your mandate. Complete the account setup and portfolio review presented by the product. Then verify the holdings, quantities, currencies and data dates in your portfolio. The portfolio-check guide explains that preparation.

If two screens disagree on a holding's value or the data is incomplete, resolve the discrepancy before relying on a numerical check. A fresh tool response can still contain older underlying evidence.

Active Free accounts support one MCP connection and the core policy, status, check and decision-recording tools. Premium adds unlimited connections and supported history, thesis and journal retrieval. Your assistant also needs the matching permissions; a subscription alone grants no connection access. See Free and Premium.

Step 1: Ask built-in AI about your data

Open AI Assistant in Investboard's app toolbar. If prompted, review the AI processing information and choose whether to allow it. Start with a question about data already available in your account.

Explain my current allocation. Separate measured facts from interpretation, give the data dates, and name any missing coverage. Tell me which displayed figures support your explanation.

Read the answer beside the relevant portfolio view. Check which scope and date it describes. If the figures do not match, ask for clarification rather than treating a fluent explanation as evidence.

Use AI at Investboard for the built-in assistant's scope and processing details. External MCP setup is a separate step below.

Step 2: Take your mandate with you as investing.md

For a conversation without an account connection:

1. Open Strategy → Overview → Brief.
2. Find Export your strategy for your AI and choose Download or Copy.
3. Check the file's composed_at date. Share the file or paste its contents into the assistant you choose.

The signed mandate also offers Download investing.md. The welcome certificate's Save as a text file downloads the same policy format; Copy link copies an owner-only page link, not the policy contents.

To add your own instructions, open Assistants → Instructions. Write Your additions and choose Save additions. The structured mandate takes precedence over this separately attributed text. Saved file lets you copy or download the document. An unsaved preview is labeled as a draft; a connected assistant receives saved additions, not unfinished editor changes.

Try this with your exported file:

Read this investing.md as my investment policy. State its composition date, then summarize my purpose, allocation bands, review rules and cooling-off terms. Quote my own additions separately. Ask me to clarify anything missing. Do not infer current holdings or permission to access my account from this file.

Completion check: the assistant identifies the date and distinguishes generated mandate rules from your additions. If you later amend the mandate, export and share a replacement. The file stays a snapshot; it does not enforce model behavior or keep itself current. Read about the investing.md format.

Step 3: Connect an assistant through MCP

MCP lets a compatible assistant call Investboard's supported tools after you authorize access.

1. In Investboard, open Assistants → Connections and choose your assistant.
2. Add a remote MCP connection in that assistant, using the server address that Investboard shows for it. The connection uses OAuth sign-in.
3. Sign in to the Investboard account you want to connect. Review the requested permissions before approving them.
4. Enable or invoke the connection in your conversation and ask it to read your policy.

For Claude, begin in Customize → Connectors and add a custom connector. Use OAuth sign-in, then enable the connector in the conversation. Team setup may require an owner. Follow Claude's current instructions.

For ChatGPT, open Plugins → Add custom MCP server, supply the server address and OAuth authentication, then install the resulting plugin and invoke it with @. Account and workspace policies apply. Follow OpenAI's current instructions.

Other clients need remote MCP with Streamable HTTP and OAuth support. The TradingAgents research bridge is not currently available to install.

Your first message can be:

Use Investboard's get_policy to read my current mandate and saved instructions. Summarize the rules with the returned composition date. Do not run a check yet. Ask me which change I want to examine.

Completion check: inspect the tool response, not just the assistant's claim that it is connected. It should contain your policy. The connection appears in Investboard after the assistant first calls it. A policy read alone creates no check in Activity.

What each permission allows

• policy:read: get_policy reads your policy; get_status reads the available plan state and freshness.
• check:run: check_action evaluates your proposal and saves a new check.
• reflection:read: get_reflection_history reads saved assistant checks, including an exact check ID. Premium is required.
• reflection:write: record_decision records the outcome you state for a check.
• record:read: get_own_record reads a current thesis projection; get_journal reads your journal. Premium is required.
• portfolio:read: get_portfolio_holdings, get_portfolio_analysis and get_portfolio_correlations read imported holdings, fund exposures and historical analytics. Each requires the matching feature access. Check the returned dates and coverage; these tools do not execute trades.

Step 4: Check a proposed change and record your decision

Describe the change completely, including its funding. A purchase funded from settled cash needs both the purchase and the cash reduction. A purchase funded by selling another holding needs both legs. Money added from outside the portfolio should be stated as new money.

For a hypothetical proposal, try:

Check this hypothetical change against my mandate: use €1,000 of settled cash to buy €1,000 of equities within the existing portfolio. Include the cash reduction and equity purchase as separate legs. Show the returned status, current and projected rule values, coverage, data dates and mandate version. Preserve the check_id. Do not place an order or record a decision.

The amount is an illustration of how to state funding, not a suggested investment. Where an actual proposal names a security, give its ISIN or clarify the listing rather than letting the assistant guess.

Read the result carefully. ok concerns the evaluated rules and evidence. breach identifies a rule conflict. cooling_off identifies a pause under your mandate. no_rule, unavailable and unclassified do not establish that the proposal is suitable or fully assessed. None predicts an investment return.

Completion check: find the saved check under Assistants → Activity and compare its reasons, dates and mandate version with the tool response. The saved verdict describes the evidence when that check ran. Calling check_action again creates a new check using then-available data.

When you have made your own decision, state it explicitly:

My decision for check_id [paste the returned ID] is deferred. Record that outcome with this note: “[my own reason].” Show the confirmed record and decision date. This statement is not an order instruction.

Supported outcomes are proceeded, abandoned and deferred. The outcome is recorded once. If the reply is interrupted, read that exact check back before attempting another write. The record documents what you reported; it does not prove a broker executed anything.

Step 5: Build your second brain for investing

Your investing second brain gives a future conversation something more reliable than a reconstructed memory of why you acted. The thesis capture and full journal-review workflow below requires Premium.

1. Open a security's dossier in Research, then choose Record thesis.
2. Write your own reason, a result that would change your view, and an optional expected observation. Keep captured Research facts separate from your interpretation.
3. Choose Save as draft while the view is unfinished. A draft creates no review reminder.
4. When ready, choose a future review date and Activate thesis. Activation records a version and its associated journal entry.
5. Use View saved thesis version to revisit that version. Update thesis can create a revision while the earlier activated version remains preserved.

Ask a permitted connected assistant to retrieve your current view:

Use get_own_record for ISIN [the instrument I specify]. Quote my statement and falsifier verbatim as my own words, with their recorded date, state and review date. If identity or access is unresolved, say so. Do not substitute your own thesis.

The tool returns a current projection, not an arbitrary historical version. Read an exact historical version in Investboard.

For a check that began with your assistant, choose Adopt into the journal in Activity. Review the prefilled text, edit it into your own reasoning, optionally add a falsifier and future review date, then confirm Save entry using the displayed hold control. The entry retains its stored link to the originating check.

Completion check: open the saved entry and follow View original mandate check. Compare the exact check with the one you adopted. Matching dates or tickers alone do not establish a relationship.

Step 6: Complete a due review

When a review is due, open Reflection → Journal → Review past reasoning.

1. Write what actually happened before revealing the original reasoning.
2. Choose Lock observation when that observation is ready.
3. Compare the revealed reasoning and falsifier with your observation. Write how sound the reasoning was, separately from the investment's outcome.
4. Choose Confirmed, Refuted or Still open, then deliberately confirm Record review.
5. Check the Review recorded receipt and open View saved entry and review.

When browser storage is available, an unfinished review is kept in that tab for up to 24 hours, with recovery wording after a reload. It is not saved to your account until confirmed. Keep the tab and account context intact while working.

A connected assistant can use get_journal to read supported entries and returned verdicts. It cannot write the observation, assessment or review verdict. The journal tool also does not return the full observation and assessment; open the saved review in Investboard to read those words.

Still open means a review was recorded and remains undecided. A missing verdict means no review was returned. Neither means the thesis was confirmed.

When a result is missing or unclear

• No connection appears: complete sign-in, enable the connection in the conversation and request a policy read. Check the account and connection limit.
• A tool is denied: inspect the required scope and plan access. Reconnect with the permission you intend to grant; do not treat denied access as an empty record.
• No thesis is found: distinguish an instrument resolved without a thesis from an unresolved identity or ambiguous ticker. Clarify the ISIN or listing.
• A check is unavailable: inspect coverage, freshness and the returned recovery guidance. Repair the underlying data before requesting a new check.
• Activity looks incomplete: assistant history covers assistant checks, not every check made inside Investboard. Use exact stored links to move between records.
• A save reply is uncertain: inspect the authoritative saved record before retrying. An item disappearing from a due queue alone does not prove a review was saved.

Keep control of access and shared information

Review and revoke external connections under Assistants → Connections. Revoking access stops future authorized reads and writes; it does not recall files or text already shared with another provider.

For a connection granted portfolio:read, the Portfolio analytics switch can disable those three read tools while leaving its other granted permissions available. Older connections need fresh OAuth approval for this scope; turning the switch on cannot grant access by itself.

The external assistant's own processing, retention and training terms apply to information it receives. Investboard's built-in AI processing commitments describe that built-in feature, not every external assistant. Leave unnecessary personal information out of free-text instructions and prompts.

For your next conversation, start with one task: read the rules, check the stated change, or retrieve your own recorded reasoning. Keep the tool response beside the explanation, and keep every decision in your own words.