For in-house AI platforms, Microsoft Copilot Studio, server-side automation, and MCP clients that don't support OAuth, you can authenticate using an MCP API token.
Step 1: Generate a token
Sign in to Tracxn
Go to Integrations → AI Integration → Tracxn MCP
Click Manage to open the Tracxn MCP Authentication page
Click Generate MCP token and copy the token (you'll only see the full token once — store it securely)
Step 2: Configure your MCP client
Configure your MCP client to send the token in the Authorization header:
None:
Authorization: Bearer <your-token>
Most MCP clients accept this in their configuration. For example:
json
{
"mcpServers": {
"tracxn": {
"url": "https://platform.tracxn.com/mcp",
"headers": {
"Authorization": "Bearer <your-token>"
}
}
}
}
Common use cases
In-house AI platforms — your engineering team integrates an MCP client into your internal AI infrastructure using the API token
Microsoft Copilot Studio — build an agent in Copilot Studio configured with your API token
Server-side automation — programmatic access where browser-based OAuth isn't practical
Token management
Tokens are tied to your Tracxn user account and inherit your account's permissions
If you suspect a token has been compromised, regenerate it from the Tracxn MCP Authentication page — the previous token will be invalidated immediately
Manage your token from Integrations → AI Integration → Tracxn MCP → Manage