Skip to main content

Set up the YipitData MCP server

YipitData's Research & Metrics MCP server gives AI agents access to the YipitData research you already subscribe to: report text and metadata, the data behind report charts, Key Metrics time series, and the publishing calendar. This guide covers getting the entitlement enabled in YipitData, installing the server from MintMCP's recommended servers, and connecting each user with their own YipitData Portal login, so every response is limited to the products that user is entitled to.

Prerequisites​

  • A MintMCP admin account
  • A YipitData subscription that includes the Research & Metrics MCP entitlement. Your YipitData account representative enables it per user (see Enable the entitlement in YipitData)
  • A YipitData Portal login for each user who will connect

Enable the entitlement in YipitData​

YipitData controls access to the MCP server through the same entitlements that govern the Portal, so there is nothing to switch on in a YipitData admin console:

  1. Contact your YipitData account representative and ask them to enable the Research & Metrics MCP entitlement for each user who will connect through MintMCP.
  2. Confirm which products those users are entitled to, because the server returns only reports and metrics from entitled products. A user who cannot open a report in the YipitData Portal cannot reach it through MCP either.

YipitData's Research & Metrics MCP documentation lists the AI clients it supports directly and the data it exposes, so use it to confirm with your representative that your entitlement covers connecting through a gateway.

Add YipitData to MintMCP​

YipitData supports OAuth 2.1 with dynamic client registration, so MintMCP registers itself as an OAuth client automatically and there are no client credentials to configure.

  1. In MintMCP, go to MCP store and open the Recommended servers tab.
  2. Select YipitData to open the configuration panel. The server URL, the OAuth authorization method, and the Per-user credentials connection type are pre-set from the catalog.
  3. Click Install.

When users first connect, MintMCP redirects them to the YipitData Portal login. They sign in with their YipitData username and password, complete multi-factor authentication if their account requires it, and approve the authorization prompt.

What the connector exposes​

YipitData maintains the list of tools its MCP server exposes and adds capabilities over time, so check the Research & Metrics MCP documentation for the current set. The server lets an agent search and fetch research reports, browse the coverage universe, pull the data behind report exhibits, look up upcoming publications, and query Key Metrics, both the current grid and historical time series.

Every call runs as the signed-in YipitData user, so an agent sees exactly the reports and metrics that user is entitled to and nothing more.

Security considerations​

  • Each user authenticates individually through OAuth, so MintMCP's audit log attributes every tool call to that user's YipitData identity and YipitData applies that user's entitlements on every request.
  • YipitData research is licensed content. Use tool customization and gateway access policies to limit which teams can connect, and keep your YipitData license terms in mind when agents pass report content into other systems.
  • Shared credentials are not recommended, because a single login would run every user under one person's entitlements and drop per-user attribution.
  • Access follows the user's YipitData account, so removing the entitlement or deactivating the user in YipitData ends what an agent can reach through MintMCP.

Troubleshooting​

  • The login page appears but sign-in fails: the user's YipitData Portal credentials are wrong or their account is locked. Have them sign in at the YipitData Portal directly first, then reconnect.
  • Sign-in succeeds but the server returns an authentication or entitlement error: the Research & Metrics MCP entitlement is not enabled for that user. Contact your YipitData account representative.
  • A report or metric the user expects is missing: the user's YipitData products do not include it. The server only returns entitled content, so check whether the user can open the same report in the YipitData Portal.
  • Rate limit errors: YipitData applies a per-user request limit to the MCP endpoint. Agents that page through many reports in one session can hit it; retry after a short pause.

For setup, access, or connection issues, YipitData asks that you email integrations-support@yipitdata.com with the client you are using, the error message, whether the user could authenticate through the Portal login, and whether they can open the relevant report in the Portal.

Next steps​