Chronograph
Interact with your Chronograph data directly in Claude
About Chronograph
Chronograph connects private-investment portfolio data to assistant workflows. Its connector lets users query portfolio information, analyze investments, search entities, retrieve performance metrics, and access Chronograph help documentation from programmatic portfolio context.
Connection details
https://ai.chronograph.pe/mcp- Transport
- Streamable HTTP
- Authentication
- OAuth
Setup
claude mcp add chronograph --transport http https://ai.chronograph.pe/mcpFrequently asked questions
What is the Chronograph remote MCP server?
The Chronograph remote MCP server is a hosted Model Context Protocol endpoint at https://ai.chronograph.pe/mcp, so AI assistants can connect to it without installing or running anything locally. Chronograph connects private-investment portfolio data to assistant workflows. Its connector lets users query portfolio information, analyze investments, search entities, retrieve performance metrics, and access Chronograph help documentation from programmatic portfolio context.
How do I connect to the Chronograph MCP server?
Add the endpoint https://ai.chronograph.pe/mcp to any MCP-compatible client such as Claude Code, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Does the Chronograph MCP server require authentication?
Yes. Chronograph uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Which transport does the Chronograph MCP server use?
Chronograph exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.
More remote MCP servers
%20-%20Annette%20Faynburd.svg)
.svg)
