From 01fff490dfb1187b648b988346b564b9d2c9d80d Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Mon, 3 Nov 2025 12:57:59 +0100 Subject: [PATCH 1/3] Add header-based auth to MCP server --- console/intelligence/mcp-server.mdx | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/console/intelligence/mcp-server.mdx b/console/intelligence/mcp-server.mdx index 0d974bf5..3be38368 100644 --- a/console/intelligence/mcp-server.mdx +++ b/console/intelligence/mcp-server.mdx @@ -129,7 +129,21 @@ If your agent doesn’t support connecting to remote MCP servers directly, use t ``` 1. Restart your AI agent. -1. Authenticate the request in your browser. +1. Authenticate the request in your browser. You can later revoke access on the Profile page of the Axiom Console. + +### Header-based authentication + +If your AI agent doesn’t support browser-based OAuth authentication, authenticate by passing headers directly: + +1. [Create a personal access token](/reference/tokens#personal-access-tokens-pat). +1. [Determine organization ID](/reference/tokens#determine-organization-id). +1. Configure your AI agent to use the server URL `https://mcp.axiom.co/mcp`. +1. Configure your AI agent to send the following headers with each request to the server URL: + + - **Authorization:** `Bearer PERSONAL_ACCESS_TOKEN` + - **x-axiom-org-id:** ORGANIZATION_ID + + If your AI agent only supports setting the Authorization header, pass the organization ID as a URL parameter: `https://mcp.axiom.co/mcp?org-id=ORGANIZATION_ID` From 8fe0c5f3fdfc85e41ee2cc9fdeaa31c38be19642 Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Mon, 3 Nov 2025 13:01:01 +0100 Subject: [PATCH 2/3] Update mcp-server.mdx --- console/intelligence/mcp-server.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/console/intelligence/mcp-server.mdx b/console/intelligence/mcp-server.mdx index 3be38368..66763d19 100644 --- a/console/intelligence/mcp-server.mdx +++ b/console/intelligence/mcp-server.mdx @@ -133,7 +133,7 @@ If your agent doesn’t support connecting to remote MCP servers directly, use t ### Header-based authentication -If your AI agent doesn’t support browser-based OAuth authentication, authenticate by passing headers directly: +If your AI agent doesn’t support browser-based OAuth authentication (for example, Agent Builder from OpenAI), authenticate by passing headers directly: 1. [Create a personal access token](/reference/tokens#personal-access-tokens-pat). 1. [Determine organization ID](/reference/tokens#determine-organization-id). From 935bc163f633b436648da74f1bea006e0381e428 Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Tue, 4 Nov 2025 10:25:55 +0100 Subject: [PATCH 3/3] Implement review --- console/intelligence/mcp-server.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/console/intelligence/mcp-server.mdx b/console/intelligence/mcp-server.mdx index 66763d19..8b9eaa55 100644 --- a/console/intelligence/mcp-server.mdx +++ b/console/intelligence/mcp-server.mdx @@ -141,7 +141,13 @@ If your AI agent doesn’t support browser-based OAuth authentication (for examp 1. Configure your AI agent to send the following headers with each request to the server URL: - **Authorization:** `Bearer PERSONAL_ACCESS_TOKEN` - - **x-axiom-org-id:** ORGANIZATION_ID + - **x-axiom-org-id:** `ORGANIZATION_ID` + + + Replace `PERSONAL_ACCESS_TOKEN` with the personal access token you have generated. + + Replace `ORGANIZATION_ID` with the organization ID. + If your AI agent only supports setting the Authorization header, pass the organization ID as a URL parameter: `https://mcp.axiom.co/mcp?org-id=ORGANIZATION_ID`