Getting started
Quickstart
VISION3 exposes 39 tools over the Model Context Protocol. Every call runs as the signed-in analyst, so an assistant sees exactly what that analyst sees in the app, and nothing else.
Connect a client
One server address works for every client.
https://vision3.co.uk/mcpClaude
Settings → Connectors → Add custom connector. Paste the address, then sign in and approve.
ChatGPT
Settings → Apps & Connectors → Create. Paste the address, choose OAuth, then approve.
Cursor & others
Add a remote MCP server with the address. The client opens VISION3 sign-in on first use.
Claude Code
claude mcp add --transport http vision3 https://vision3.co.uk/mcpmcp.json
{
"mcpServers": {
"vision3": {
"url": "https://vision3.co.uk/mcp"
}
}
}Authentication
Clients register themselves, then redirect the analyst to VISION3 sign-in. The approval screen names the client requesting access, and the analyst approves or denies it. Registration alone grants nothing.
- Only tokens issued through the approval flow are accepted. Copied browser sessions return
401. - Passwords never reach the assistant.
- Private work (chats, reports, tasks, meetings) stays private to its owner; shared models and filings stay shared.
Limits & errors
| Response | Meaning |
|---|---|
401 | Missing, expired or unapproved token. The client should re-run sign-in. |
isError | The tool ran but could not answer, for example an unknown ticker or an unexpected parameter. The message says why. |
| Not held | VISION3 has no evidence for the request. Tools say so rather than filling the gap. |
Long documents return up to 50,000 characters per call; page with offset or jump with find. Research questions are asynchronous: poll every 30–60 seconds.
A first call
search_companiesto resolve the ticker other tools expect.ask_vision3with a research question. It returns arunIdstraight away.get_research_answeruntil the cited answer lands, usually within one to five minutes.