Skip to main content

Connect your agent

Use the same server address in every compatible client:

https://dievio.com/api/mcp

Choose Streamable HTTP for the transport and OAuth for authentication. Your client opens Dievio in the browser. Sign in, select your personal or team account, review permissions, and approve the connection.

The MCP / Agents page also has client-specific setup instructions and connection management.

Codex​

In MCP settings, add a remote server named Dievio, choose Streamable HTTP, and enter the server URL. Save and authenticate when prompted.

For the Codex CLI:

codex mcp add dievio --url https://dievio.com/api/mcp
codex mcp login dievio

Alternatively, add the server to your Codex configuration and then run the login command:

[mcp_servers.dievio]
url = "https://dievio.com/api/mcp"

See the official Codex MCP guide.

Claude​

Open Customize → Connectors, add a custom connector named Dievio, and enter the server URL. Select Connect to authorize it, then enable the connector for the conversation where you want to use it.

For a managed team or enterprise workspace, an owner may first need to add the connector for the organization. Each person still signs in with their own Dievio account.

See the official Claude custom connector guide.

Claude Code​

Run:

claude mcp add --transport http dievio https://dievio.com/api/mcp

Open Claude Code, run /mcp, select Dievio, and complete browser authentication. See the official Claude Code MCP guide.

ChatGPT​

For ChatGPT on the web, enable Developer mode in Settings → Security and login if your account or workspace permits it. Open Plugins, add a developer-mode connection named Dievio, enter the MCP URL, and use OAuth. Complete the Dievio browser authorization, then enable the connection for your conversation.

If your desktop client provides Settings → MCP servers, add the same URL as a Streamable HTTP server and select Authenticate.

Custom connection availability depends on your client and workspace policy. See the official ChatGPT connection guide.

Other clients​

Your client must support remote Streamable HTTP, OAuth authorization-code flow with PKCE, and dynamic client registration. Enter the server URL in its remote MCP settings.

Clients that accept this mcpServers format can use:

{
  "mcpServers": {
    "dievio": {
      "type": "http",
      "url": "https://dievio.com/api/mcp"
    }
  }
}

Configuration formats vary by client. A local stdio-only client cannot connect directly with this configuration.

Check your connection​

Ask your assistant:

Show my connected Dievio account, available credits, and supported search filters. Do not run a paid search yet.

The agent should use get_account and get_search_filters. Check that the selected account or team is the one you intended.

To disconnect, open MCP / Agents, find the connection, and select Revoke access. To use a different account or different permissions, authorize a new connection and revoke the old one if it is no longer needed.

Troubleshooting​

  • No authorization window: verify the full /api/mcp URL and remote OAuth support in your client; select its authenticate/login action.
  • No tools after connecting: refresh the client's MCP connection or start a new conversation after authorization.
  • Access denied: inspect the granted permissions and current team membership. Reauthorize to request a missing permission.
  • Wrong credits or missing lists: check the account returned by get_account; the connection is tied to the account chosen during consent.
  • Expired or revoked connection: authenticate again. Do not paste your Dievio password or API key into the conversation.
  • Search still running: use get_search_job with the existing job ID. Starting another search creates another paid operation.