Morningstar MCP Server

Connect trusted data to your AI workflows with the Morningstar MCP Server.

Authenticate

The Morningstar MCP Server requires authentication. How you authenticate depends on how you connect: AI clients such as Claude, ChatGPT and Copilot prompt you to sign in with your Morningstar credentials (OAuth), while your own code authenticates with a bearer token.

Before You Begin

You need a licensed Morningstar account. This applies whether you connect through a client, the Morningstar Plugin, or your own code.

Choose an Authentication Method

Method	Use it when	Credentials
OAuth	You connect through an AI client	Your Morningstar username and password, entered at sign-in
Bearer token	You connect from your own code, or your platform supports token-based authentication	A token obtained from the Authentication API

Authenticate with OAuth

Use OAuth when you add Morningstar to an AI client as a connector, app or tool.

Add the Morningstar MCP Server to your client. See Set Up Manually or Set Up with Plugin.
When prompted, sign in with your Morningstar credentials.
Once authenticated, start using Morningstar data by asking a question in your client.

Authentication by Platform

Platform	Supported authentication
Claude	OAuth. Users authenticate when connecting, from Add connectors or Settings → Connectors.
ChatGPT	OAuth, when connecting from Explore apps.
Copilot Studio	OAuth
Copilot App	OAuth, when connecting from Apps.
Microsoft Foundry	OAuth or token-based
Perplexity	See the Perplexity connection steps.

For Claude Enterprise accounts, the administrator adds Morningstar as a custom connector once for the whole account. Each user must still authenticate with their own Morningstar credentials.

Authenticate with a Bearer Token

Use a bearer token when you connect from your own code with an MCP client over Streamable HTTP, or when you choose token-based authentication in Microsoft Foundry.

Obtain a bearer token from the Authentication API.
Send the token in the Authorization header of every request to the server:

Authorization: Bearer <bearer_token_obtained_from_auth_api>

Example mcp.json Configuration

{
  "mcpServers": {
    "morningstar": {
      "url": "https://mcp.morningstar.com/mcp",
      "headers": {
        "Authorization": "Bearer <bearer_token_obtained_from_auth_api>"
      }
    }
  }
}

Treat your bearer token like a password. Don't commit it to source control or share it.

Troubleshooting

You are not prompted to sign in. Confirm the connector or tool was added with the server URL https://mcp.morningstar.com/mcp, then try connecting again.
Sign-in succeeds but requests are rejected. Confirm your Morningstar account is licensed for the data you're requesting.
Requests from your own code are rejected. Confirm the Authorization header uses the Bearer prefix and that the token is current. If it has expired, obtain a new one from the Authentication API.