Bring your saved reasons, thesis history and source evidence into a conversation with your assistant. Catch up on what changed or test a particular claim, while TickerTrac keeps the record.
1. Open your TickerTrac account
Save a company or Investment theme and your reason for following it. Your assistant can then work with that thesis and its retained evidence.
2. Connect your assistant
In an assistant that supports remote MCP connections with OAuth, add this server URL. Follow the TickerTrac sign-in screen and choose read access to begin.
https://api.tickertrac.com/mcpThese are preview workflow packages. Availability and setup vary by host and account. Use the optional workflow downloads below if your host accepts custom packages. Downloading a package does not connect your account; you still choose access at sign-in.
3. Try a review
Both packages include these two workflows. You can also paste a prompt into your connected assistant.
Review what changed
Use TickerTrac to review up to three of my saved theses. Ask which ones if needed. Compare retained changes with each exact thesis version, cite permitted evidence, and separate what strengthened, weakened or remains uncertain. State the time window and any missing coverage. Do not save changes or start research.
Check one piece of evidence
Use TickerTrac to check a saved source against one of my theses. Ask me which thesis and source. Retrieve the exact version and permitted passages, then explain what the source supports, contradicts or leaves unresolved. Keep source facts separate from your interpretation. Do not save changes or start research.
After trying it, return to Assistant connections to tell us whether the evidence review helped. Missing evidence is reported as missing; your assistant should not fill it in.
Choose how changes are saved
Saved-record write access lets your assistant prepare changes. By default, it provides a direct review link: inspect the before/after changes and select Approve and apply once. TickerTrac saves the batch and returns its versions and receipt. Reads need no repeated review.
You can separately enable an optional permission in Assistant connections. Choose one connection, one watchlist, allowed additions or appends, an expiry and a daily operation limit. Permitted batches can then save without another review; each retains the permission rules and version history. Position weights, thesis replacement, investment-theme changes and research remain outside this permission.
Create themes and choose monitoring
Separate setup tools can create a private Investment theme, link the companies you specify and select monitoring. Your assistant provides one exact review with the affected companies, account selection totals and future checks. Approval saves that setup together. These actions require explicit batch approval and cannot use a standing note-editing permission.
Local connector setup
If your assistant supports local stdio MCP, use Python 3.11 or later. In Assistant connections, expand Create a local access key and create a named read key, or a key for approved changes. The key is shown once and can be revoked.
Install the local connector
Download the TickerTrac connector from this site. These commands create a separate environment on macOS or Linux and install the connector and its dependencies.
python3 -m venv .tickertrac-mcp
.tickertrac-mcp/bin/python -m pip install https://tickertrac.com/downloads/tickertrac-mcp.zipOn Windows:
py -m venv .tickertrac-mcp
.tickertrac-mcp\Scripts\python.exe -m pip install https://tickertrac.com/downloads/tickertrac-mcp.zipConfigure your local assistant
Use your assistant's local MCP configuration format. This example uses a read key; replace the executable path and keep the key in the host's private configuration.
On Windows, the executable is .tickertrac-mcp\Scripts\tickertrac-mcp.exe; escape backslashes in JSON.
{
"mcpServers": {
"tickertrac": {
"command": "/absolute/path/to/.tickertrac-mcp/bin/tickertrac-mcp",
"env": { "TICKERTRAC_READ_KEY": "<your-scoped-read-key>" }
}
}
}For approved changes, use TICKERTRAC_WRITE_KEY instead, with the matching approved-change key. Never put a key in a conversation, command argument, shared file or support message. Connect only an assistant you trust to receive the private records you request.
Costs and control
Saved-record tools start no research and preserve monitoring selections. Explicit setup approval can enable future scheduled AI checks under your existing account allowances and spend limits. It does not dispatch immediate research, historical replay or company matching. Existing account request limits apply; your assistant's own model charges are separate.
Manage or revoke connections, keys and bounded permissions in Assistant connections or Settings. Revocation stops future access but cannot remove records an assistant already received. Existing record history is preserved when you save a new version.