Connect your agent
Use ASNOMIC from your AI.
Connect your AI to inspect two bounded monitoring paths: ASNOMIC-qualified built-in market evidence and, for explicitly entitled principals, approved externally computed decimal observations. MT5 is the first read-only reference adapter, not a trading connection. The table below says exactly what works, what is still being built, and what has not been qualified.
Recommended now
Claude chat
Claude chat is the fastest supported route today. Add ASNOMIC as a remote custom connector, then keep working in a normal conversation.
Claude Free permits one custom connector. Pro and Max users can add it themselves. Team and Enterprise require an owner to add it for the organization first.
Read Anthropic’s connector guide ↗- 01
Open Claude’s connectors
In Claude on the web, open Customize → Connectors. Choose +, then Add custom connector.
- 02
Add ASNOMIC
Name the connector ASNOMIC and paste the public server address. Leave Advanced settings empty; ASNOMIC registers the connector during sign-in.
https://asnomic.com/mcp
- 03
Connect your Beta account
Choose Connect, sign in with the Google account used for your ASNOMIC Beta seat, and review the read and execute permissions before approving.
- 04
Enable it in a conversation
Use + → Connectors in Claude and turn on ASNOMIC for that conversation. Start by asking Claude to inspect capabilities; creating a monitor still requires a separate exact human approval in ASNOMIC.
Use ASNOMIC to inspect my monitoring capabilities. Report the supported instruments, cadences, modes and current limits. Do not create or activate a monitor.
Local development
Codex app and command line
Connect directly from your development environment. ASNOMIC uses a short-lived local callback for sign-in; no token needs to be copied into a terminal or chat.
ASNOMIC qualified the Codex CLI path through dynamic registration, Google sign-in, the 127.0.0.1 callback, issuer validation, an authenticated tool call and a fresh-process reconnect. Codex documents the same MCP configuration for its app and IDE extension.
Read OpenAI’s MCP guide ↗- 01
Add ASNOMIC
In a terminal, add ASNOMIC as a Streamable HTTP MCP server. Codex app, CLI and IDE extension share this local configuration.
codex mcp add asnomic --url https://asnomic.com/mcp
- 02
Sign in
Start OAuth login. Codex opens ASNOMIC in your browser and returns authorization to a temporary 127.0.0.1 port on this device.
codex mcp login asnomic --oauth-client-registration dcr
- 03
Review and approve
Sign in with the Google account that owns your Beta seat. Confirm that the page says Codex and shows a 127.0.0.1 redirect before approving read and execute access.
- 04
Use it from Codex
Open Codex or restart the local client, check /mcp, then ask ASNOMIC to inspect capabilities. Monitor activation still requires separate exact approval in ASNOMIC.
Use ASNOMIC to inspect my monitoring capabilities. Do not create or activate a monitor.
Current coverage
MCP support is only the first check.
An app also has to complete ASNOMIC OAuth, preserve the principal across sessions, and reconnect safely. “Needs qualification” means the vendor documents the right protocol, but ASNOMIC has not proved that complete path.
| Agent | What its vendor supports | ASNOMIC today |
|---|---|---|
| AgentClaudeWeb chat, Desktop, mobile | Vendor supportRemote custom connectors on Free, Pro, Max, Team and Enterprise. Free allows one custom connector. | ASNOMIC todayUSE NOW Best current route. Claude’s hosted connector uses a public HTTPS callback that matches ASNOMIC’s present sign-in policy. Official documentation ↗ |
| AgentChatGPTWeb chat | Vendor supportRemote MCP tools are supplied through installed plugins. | ASNOMIC todayPLUGIN IN PROGRESS ASNOMIC’s ChatGPT plugin is not published yet. Pasting the MCP URL into ordinary ChatGPT web chat does not connect it. Official documentation ↗ |
| AgentCodexCodex app, CLI and IDE extension | Vendor supportDirect Streamable HTTP MCP and OAuth are supported and shared by local Codex clients. | ASNOMIC todayUSE NOW Qualified with Codex CLI dynamic registration, Google sign-in, a 127.0.0.1 callback, issuer validation, authenticated tool use and reconnect. The local Codex clients share this configuration. Official documentation ↗ |
| AgentClaude CodeCLI | Vendor supportRemote HTTP MCP and OAuth are supported through claude mcp and /mcp. | ASNOMIC todayNOT YET ASNOMIC now accepts secure native loopback callbacks, but the complete Claude Code sign-in, tool call and reconnect path has not yet been qualified. Official documentation ↗ |
| AgentCursorDesktop editor | Vendor supportRemote Streamable HTTP MCP with OAuth is documented. | ASNOMIC todayNEEDS QUALIFICATION Protocol support is promising, but ASNOMIC has not verified Cursor’s registration and reconnect flow. Contact us before relying on it. Official documentation ↗ |
| AgentVS Code / CopilotEditor chat and agent sessions | Vendor supportRemote HTTP MCP and OAuth are documented. | ASNOMIC todayNEEDS QUALIFICATION ASNOMIC has not qualified its OAuth callback and session continuity in VS Code. Client support alone is not proof of a working account connection. Official documentation ↗ |
| AgentGemini CLICLI | Vendor supportRemote Streamable HTTP MCP and OAuth are documented. | ASNOMIC todayNEEDS QUALIFICATION ASNOMIC now accepts secure native loopback callbacks, but the complete Gemini CLI sign-in, tool call and reconnect path has not yet been qualified. Official documentation ↗ |
| AgentWindsurf CascadeDesktop editor | Vendor supportStreamable HTTP MCP and OAuth are documented. | ASNOMIC todayNEEDS QUALIFICATION ASNOMIC has not verified sign-in, tool calls and reconnect behavior in Windsurf. Official documentation ↗ |
| AgentCustom agentAny MCP client or SDK | Vendor supportRequires public Streamable HTTP plus MCP OAuth discovery, PKCE and Dynamic Client Registration. | ASNOMIC todayNEEDS QUALIFICATION It may work with an exact HTTPS redirect or a standards-compliant local loopback callback. Verify the complete sign-in and reconnect flow before giving it to a user. Official documentation ↗ |
Public MCP address
https://asnomic.com/mcpDo not paste passwords, Google tokens, or access tokens into a chat. A supported client discovers ASNOMIC OAuth from this address and opens sign-in itself.
See the guide before you sign in.
Connecting uses the Google account that owns your ASNOMIC Beta seat.
After connection
Give your AI the question you want watched.
ASNOMIC keeps checking after the conversation ends. The agent must show a preview, and you approve the exact monitor before it starts.
Read access inspects capabilities and your state. Execute access permits supported actions within your allowance. It never removes human approval.
A draft stays on this device until you copy it to your AI. Leave out credentials and personal information.
Preview the starter message
Help me turn this thesis into an ASNOMIC monitor: [describe the evidence I want watched] Inspect current monitoring capabilities first. Ask me for missing details and define measurable conditions using supported instruments and cadences. Show a preview with the mode, duration, alert behavior and maximum promotional credit cost. Do not activate anything until I complete ASNOMIC’s human approval. Do not treat alerts as trade instructions.
Disconnecting and stopping are different.
Manage ASNOMIC connection permissions ↗ to revoke OAuth access and refresh tokens. Removing a connector in an AI app may not revoke its ASNOMIC grant. Disconnecting does not stop existing monitors; use Stop monitoring on each monitor.