Connect the Talon.One MCP server Closed beta

Connect the Talon.One MCP server to your AI agent to give it read-only access to your Talon.One data.

Supported MCP clients

The Talon.One MCP server supports the following MCP clients:

• Claude Desktop
• Claude Code
• Cursor
• Microsoft Copilot
• Copilot Studio
• Gemini CLI
• ChatGPT CLI
• Codex CLI
• Most other stdio-compatible clients

Prerequisites

• You have Node.js installed on your computer.
• You have a Talon.One account. You sign in with your Talon.One credentials or Okta SSO.

Connect the MCP server

Each Talon.One environment provides its own MCP server URL. The server uses OAuth 2.0, so you authorize access in your browser instead of managing an API key. To connect an agent, determine your MCP server URL, add the configuration to your client's config file, and authorize access when your browser opens.

Important

OAuth 2.0 replaces API key authentication for the Talon.One MCP server. API key authentication still works, but use OAuth 2.0 for new clients, and migrate existing clients. To migrate a client, replace its API key configuration with the OAuth 2.0 configuration in your AI client config file.

1

Determine your MCP server URL

Your MCP server URL is based on your specific deployment address. To compose it, add /v1/mcp/entrypoint to the end of your deployment URL. Example: https://mycompany.europe-west1.talon.one/v1/mcp/entrypoint.

2

Configure your MCP client

The Talon.One MCP server supports most stdio-compatible MCP clients. The following steps cover the most commonly used ones. For any other client, see your MCP client's documentation.

Claude Desktop

To connect Claude Desktop to the Talon.One MCP server:

1. Open Settings > Developer.

2. Click Edit Config to open claude_desktop_config.json.

3. Add the following configuration to the file, replacing the URL with your MCP server URL:

   {
     "mcpServers": {
       "talon-mcp": {
         "command": "npx",
         "args": [
           "mcp-remote",
           "https://YOUR_DEPLOYMENT_URL/v1/mcp/entrypoint"
         ]
       }
     }
   }

4. Save the changes and restart Claude Desktop.

Cursor

To connect Cursor to the Talon.One MCP server:

1. Open Customize > MCPs.

2. Click + New or New MCP Server to open mcp.json in a new tab.

3. Add the following configuration to the file, replacing the URL with your MCP server URL:

   {
     "mcpServers": {
       "talon-mcp": {
         "command": "npx",
         "args": [
           "mcp-remote",
           "https://YOUR_DEPLOYMENT_URL/v1/mcp/entrypoint"
         ]
       }
     }
   }

4. Save the changes.

Microsoft Copilot

You can use Copilot Studio to create a custom agent and add the Talon.One MCP server to the agent as a tool. You can then publish the agent to Microsoft Copilot for your organization. The Talon.One MCP server supports OAuth 2.0 dynamic client registration (DCR). After you publish the agent, each user signs in with their Talon.One credentials the first time they call a Talon.One tool. For the setup steps, see Connect your agent to an existing MCP server in the Copilot Studio documentation.

3

Authorize access in your browser

After you save the configuration, the Talon.One sign-in page opens in your default browser. Sign in with your Talon.One credentials or Okta SSO to authorize access. Your MCP client loads the Talon.One tools after authorization completes.

After you connect the Talon.One MCP server, add skills to help your AI agent use the tools for your role.

Related pages

• Talon.One MCP server
• Talon.One MCP skills