Skip to main content
This guide demonstrates how to write an MCP server, add Oauth based authentication to it using Okta as the identity provider, and then integrate it with the TrueFoundry AI Gateway. The setup below explains both the user authentication and machine-to-machine authentication scenarios:
  • User Authentication: Authenticate specific users through the AI Gateway using the Authorization Code flow with refresh tokens
  • Machine-to-Machine Authentication: Enable programmatic access without user interaction using the Client Credentials grant flow
The entire code for the steps described below can be found in this Github link: https://github.com/truefoundry/getting-started-examples/tree/main/calculator-oauth-mcp-server

Guide to creating the MCP server and adding Oauth

1

Write a basic MCP Server and test it locally

Let’s start by writing a basic MCP server that provides a get_me tool.
server.py
Run the server locally:
Your MCP server will be available at http://localhost:8000/mcp. Test the server using this Python script:
test.py
This MCP server is running without any authentication. Enable OAuth next by registering the server in Okta, then adding JWT verification to the code.
2

Register the MCP server in Okta

Create an authorization server, OAuth app, access policy, and scopes in Okta. Follow Okta app setup and collect:
  • OAUTH_ISSUER and OAUTH_JWKS_URI (from the authorization server)
  • OAUTH_AUDIENCE
  • CLIENT_ID and CLIENT_SECRET (for TrueFoundry; the MCP server itself only needs issuer, JWKS, and audience to verify tokens)
3

Modify MCP server code to add Oauth Token verification

Create a .env file to add the environment variables and modify the server.py file to add the JWT verification.
4

Get the token and call the MCP server in test.py (Machine-to-Machine authentication)

In Step 1, we had a script to test the MCP server locally. After adding the Oauth token verification to the MCP server in the previous step, we need to modify the script to get the token and then call the MCP server. If you call the MCP server without a token, it will return a 401 Unauthorized error.
test.py
The test.py script above contains the code to get the Okta token and then call the MCP server.
The OAUTH_WELL_KNOWN_URL enables the MCP server to expose the /.well-known/oauth-authorization-server endpoint, which allows the AI Gateway to auto-discover OAuth configuration details. This endpoint redirects to your Okta authorization server’s well-known endpoint.
This is exactly how you will be doing Machine-to-Machine authentication to the MCP server. Code snippets to get the token in different ways are outlined below:
Response:
When using a custom authorization server, you can use custom scopes defined in your authorization server. Make sure to include the audience parameter matching the audience configured in your authorization server.
5

Host the MCP server and get the endpoint URL

Now that we have tested the MCP server locally, we will add it to the AI Gateway to enable user authentication and allow the MCP server to be accessed via the AI Gateway. To add the MCP server to the AI Gateway, we need to get the endpoint URL of the MCP server. Hence, we need to host the MCP server on a public URL.
If you are using the TrueFoundry AI Deployment product, this can be done by creating a service deployment, choosing your Github repository containing the MCP server code above. Otherwise, you can host it on a VM or a Kubernetes cluster or any hosting provider of your choice.
Remember to add the environment variables for the MCP server:
The MCP server only needs these environment variables to validate OAuth tokens. It doesn’t need the Client ID or Client Secret since it’s only validating tokens, not generating them.
After deployment, you will have the endpoint URL of the MCP server. Let’s consider it https://calculator-oauth-mcp-server.example.com for the rest of the steps. After deploying, check once using the test.py script above by changing the MCP server URL to the deployed URL. You should be able to fetch the tools from the MCP server.
6

Add the MCP server to the TrueFoundry AI Gateway

You will need to have a MCP server group to be able to add the MCP server to the TrueFoundry AI Gateway. Please refer to the Getting Started guide to create a MCP server group.
  1. In your MCP Server Group, click Add MCP Server
  2. Select Remote MCP
  3. Configure the server:
    • Name: oauth-mcp-server
    • Description: OAuth-authenticated MCP server with Okta
    • URL: Your deployed service endpoint (e.g., https://calculator-oauth-mcp-server.example.com/mcp).
    • Transport: streamable-http
    • Authentication Type: Select OAuth2
  4. In the OAuth2 configuration section, provide the Okta credentials:
    • OAuth2 Client ID: Your Okta application client ID
    • OAuth2 Client Secret: Your Okta application client secret
The AI Gateway will automatically discover the OAuth2 Authorization URL, Token URL, and other configuration details from your MCP server’s /.well-known/oauth-authorization-server endpoint once you provide the MCP server URL.You can optionally configure:
  • OAuth2 Scopes: The scopes are prefilled, but you can change them if needed to use your custom scopes.
  • Include offline_access in the scopes to enable refresh tokens. This allows the AI Gateway to automatically refresh expired access tokens without requiring users to re-authenticate.
  • You can store the client id and secrets in truefoundry secrets and reference them by FQN in the configuration.
  1. Set access control: Select teams or users who should have access to this MCP server.
Managers of the MCP Server Group automatically have access to all servers in the group.
  1. Click Save to add the MCP server
    • The server will appear in your MCP Server Group
    • Users can now connect and use the server through the AI Gateway
7

Test the MCP server in the Playground

  1. Navigate to the Playground in the AI Gateway.
  2. Click Add Tool/MCP Servers
  3. Find your calculator-oauth-mcp-server in the list
  4. Click Connect Now to initiate OAuth authorization
  1. You’ll be redirected to Okta to authorize access
  2. Click Allow to grant access
  3. You’ll be redirected back to the AI Gateway
  4. The AI Gateway will store your OAuth tokens securely and refresh them automatically when they expire
  5. You’ll see the add and subtract tools from your MCP server
  6. Select the tools and click Done
  7. Try sending a prompt like Add 1 and 2. Use the tools provided
  8. The tool will return the result from your MCP server

Okta setup for On-Behalf-Of (OBO) token exchange

For Okta authorization servers, native app, API Services app, Token Exchange grant, and the manual curl check, see Okta app setup. Gateway-side manifests and troubleshooting are in Scenario 7: Okta OBO Token Exchange.