Connect Codex to Oviond so you can use AI-assisted workflows with your Oviond account.
This article is for technical team members using Codex for reporting operations or internal tooling who want Codex to work with Oviond through MCP.
You will need:
access to your Oviond account,
permission to authorize the connection,
access to the AI client or developer tool named in this article,
the Oviond MCP server URL: `https://api.oviond.com/mcp`.
Only use the hosted Oviond MCP URL. Do not try to run Oviond MCP as a local stdio server.
Open the area in Codex where you add a custom MCP server or connector. Use Codex’s MCP configuration flow for adding a remote HTTP MCP server.
Use this URL:
`https://api.oviond.com/mcp`
Name the connector Oviond if your tool asks for a name.
When Codex asks to connect, complete the Oviond sign-in and authorization flow in the browser.
Ask the AI client to do a safe read-only check first, such as listing your Oviond clients or showing available Oviond actions.
Codex should show Oviond as a connected MCP server or connector. After authorization, the AI client can use supported Oviond MCP tools for clients, projects, pages, widgets, templates, themes, users, automations, and other account workflows.
Check that the MCP URL is exactly `https://api.oviond.com/mcp` and that your AI client supports remote HTTP MCP servers with OAuth.
Sign out and try again. Make sure you are signing in with the Oviond account you want the AI client to access.
Check that you authorized the correct Oviond account. Also check whether the client or project exists in Oviond.
Start with a read-only request. For example: “List my Oviond clients.” Do not begin with delete, bulk update, or publish-style actions.
Send Oviond support:
the AI client you are using,
whether you used MCP or the REST API,
the exact point where setup failed,
the error message if one appeared,
whether authorization opened in the browser,
a screen capture that does not show private tokens or API keys.
