Server URL, transport, and authentication for the Agntix MCP server.
The Agntix MCP server is a remote MCP server. Any client that speaks the Model Context Protocol can connect to it over HTTP and authenticate with an organization API key.
Confirm the production MCP endpoint for your deployment before publishing. The host follows the same
convention as the rest of the platform (api.agntix.ai, app.agntix.ai, status.agntix.ai); update
this value if your environment differs.
The MCP server uses the same credentials as the REST API — see Authentication for how to create a key.
Method
Header forwarded upstream
When to use
API Key (recommended)
x-api-key: pk_live_…
Server-to-server, local dev, scripts
Bearer JWT
Authorization: Bearer <token>
First-party apps with an existing Clerk session
The scopes on the key apply to every tool call. A chat:read key can only invoke read tools; write/delete tools return 403 Forbidden.
An API key grants access to your whole organization. Store it in your client’s secret/credential
field — never paste it into a shared config that gets committed to git. Prefer a scoped, dedicated
key for MCP usage.
Once configured, ask your assistant to list its Agntix tools, or have it run a read-only action such as “list my Agntix agents.” A successful response confirms the server URL and key are correct. A 401 means the key is missing or invalid; a 403 means the key lacks the scope for that tool.See the Client Setup page for step-by-step configuration of Claude Desktop, Cursor, and other clients.