Connect LinqProtocol to Codex or Claude
Give your AI workspace secure access to your LinqProtocol deployments, logs, metrics, networking, and VM controls. Setup takes a few minutes and uses your existing dashboard account.
Hosted connector
Connect securely without running another server on your computer.
Existing account
Authorize with the same login you already use on the dashboard.
You keep control
Wallet transactions always return to you for review and signature.
Coming soon
A one-click LinqProtocol plugin for Codex is on the way. Until then, experienced users can add it manually through Developer mode.
Add a custom connector
Claude connects through the production LinqProtocol MCP server. Use these exact values in the custom connector form.
LinqProtocolhttps://mcp.central.linqprotocol.com/mcptpc_5DWgQzDkSyJ1HcttvfQovVUse the production MCP URL shown above. Do not substitute a Codex-specific endpoint.
- 1Open Settings, then Connectors, then Add custom connector.
- 2Enter LinqProtocol as the connector name and paste the MCP server URL shown here.
- 3Open the OAuth or advanced authentication settings.
- 4Enter the public OAuth Client ID shown here.
- 5Leave Client Secret empty.
- 6Add the connector and select Connect.
- 7Sign in with the same account used on the LinqProtocol dashboard.
- 8Approve access, then enable LinqProtocol under Search and tools.
- 9Start a new conversation after connecting.
What your agent can help with
Tools are permission-scoped and only operate on deployments available to your account.
Manage deployments
List deployments, inspect services, and start, stop, or restart supported workloads.
Investigate issues
Read logs, metrics, readiness information, and diagnostics without jumping between screens.
Configure networking
Review routes, expose application ports, and manage platform or custom domains.
Prepare transactions
Build deployment and renewal handoffs for review and signing in your own wallet.
Authorization and safety
- The connector never asks you to paste a dashboard password or wallet seed phrase.
- Disruptive controls should be confirmed before the agent runs them.
- Deployment and renewal transactions are prepared as browser handoffs for you to sign.
After connecting
Start a fresh conversation, then try: “Show me the status of my LinqProtocol deployments.” If tools do not appear, disconnect and reconnect the server before opening another new chat.