AZMX AI · Connectors
The agent reaches your stack, not the other way around.
Seventeen MCP servers curated and signed. Bring your own MCP via a single file. Eleven AI providers via BYOK. Every connector runs locally on your machine — under per-call approval, recorded in your audit log.
17MCP connectors curated
11AI providers · BYOK
∞Bring-your-own MCP
AI providers
Eleven providers. Bring your own key.
AZMX never bills you for AI inference. You pay your provider directly — at their list price, with their privacy contract, on your account.
OpenAIGPT-4o · o1
AnthropicClaude 3.7 · 4.x
GoogleGemini 2.5
GroqLlama · Mixtral
CerebrasLlama 3 fast
xAIGrok 4
DeepSeekV3 · R1
Azure OpenAITenant-rooted
NVIDIA NIMOn-prem GPU
OllamaFully local
LM StudioFully local
OpenAI-compatSelf-hosted
MCP catalog
Seventeen curated MCP servers.
Each catalog entry is signed, integrity-hashed, and pinned to a known version. Trust prompts surface the verbatim command + hash before first launch.
PostgresSchema · query · plan
MySQLSchema · query
RedisCache · streams
MongoDBCollection ops
Kuberneteskubectl wrapper
AWSMulti-service
GCPMulti-service
GitHubPRs · issues
GitLabMRs · CI
LinearIssues · cycles
JiraTickets · epics
SlackMessages · search
NotionPages · DBs
StripePayments
SentryErrors · events
DatadogMetrics · logs
OpenTelemetryTraces
everythingReference
How MCP works in AZMX
Standards-compliant. Trust-gated. Yours.
- stdio + HTTP transportsBoth transports supported. stdio for local processes (most servers). HTTP for hosted endpoints (CDN-fronted servers like Anthropic's reference set).
- Per-tool approvalEvery MCP tool has Inherit · Auto · Confirm · Block. Set once, applies to every future call. Or change at any time from Settings → Connectors.
- Integrity hash on installEvery catalog server has its command + version pinned. Workspace MCP files (.azmx/mcp.json) require trust on first run; the hash is recorded; subsequent edits prompt re-trust.
- Resources + prompts surfaceMCP resources appear in the @mcp picker. MCP prompts surface as /
. . Both are read-only by default — they never bypass the approval gate. - Bring your ownDrop a single .azmx/mcp.json into your repo. Trust the integrity hash on first launch. The agent treats it as a first-class connector.
Plug AZMX into what you already run.
Browse the curated catalog, drop a workspace MCP file, or bring your own provider key. The trust gate is the same across all of them.