Not signed in: your figures stay in this browser and are not saved to a Zeno FinLab account.
Zeno FinLab logo

Zeno FinLab

Zeno FinLab

Connect an AI Assistant

Use a compatible AI client to discover and invoke supported financial tools through Zeno FinLab’s remote MCP connection, subject to authorization and the client’s capabilities.

Connection endpoint

Production endpoint: https://zeno-fin.com/mcp

Open this guide on your chosen Zeno deployment to copy its endpoint.

The copyable address matches this deployment. On a preview, it is a preview address; use the production endpoint for the published service.

The registered tools list existing financial tool pages and calculate monthly savings contributions from supplied figures. They do not expose stored financial records, paid reports or payment actions. Educational estimates only—not financial, investment or tax advice.

Connect and authorize

A compatible client must complete Zeno’s supported OAuth authorization and consent flow. A normal Zeno website login is not a substitute for MCP OAuth authorization; signing in may be one step of the consent process.

Never share passwords, access tokens, client secrets or other credentials with support staff, or paste them into public pages.

Compatibility and verification

The implementation protects MCP tools with OAuth and requires the OAuth client claim. Prior server checks returned HTTP 200 for protected-resource metadata and HTTP 401 with an authentication challenge for unauthorized requests. Tool registration and input schemas have test coverage.

A complete external OAuth consent-to-tool-invocation round-trip remains unverified. The examples below are connection guidance, not verified compatibility claims for ChatGPT, Claude, Claude Code or any other client. Availability depends on the client and your account.

Other MCP clients

  1. Open your client’s MCP server or custom connector settings and create a remote MCP connection.
  2. Name it Zeno FinLab and paste the endpoint above.
  3. Complete the client’s sign-in, authorization and consent prompts. Review the requesting client before approving.
  4. Enable the connection and ask the assistant to use Zeno FinLab.

Follow your client’s current supported connection flow if its interface differs. Do not replace OAuth with a copied website session token.

Refresh and troubleshoot

Refresh after the app changes · Other MCP clients

Select Zeno FinLab in your client’s connector settings. Refresh the tool list, reload the server or reconnect. If the URL changed, paste the latest endpoint above. Start a new chat or session and ask the assistant to use Zeno FinLab.

Authorization failure is not a successful connection

HTTP 401 means that request was not authorized. It does not, by itself, establish that the service is broken. Repeating consent is not guaranteed to resolve it: confirm that your client supports the required OAuth flow and is using the intended endpoint.

A saved connector or successful website login alone does not establish success. Confirm that the client completes authorization, discovers the tools and receives a valid tool result. That full external journey has not yet been verified for Zeno FinLab.