# Connect your AI agent to MyDataValue These setup steps are written for the assistant being connected. They connect it to the user's myDataValue account over MCP in three parts: the section for the assistant in use, the sign-in, then [a check](#verify-the-connection) that the assistant can reach the user's own properties. A team whose Connections page shows **AI assistants** finds the setup prompt there: the user copies it into the assistant they want to connect, and that assistant fetches this page. Server name: `mydatavalue`. Server URL: `https://api.mydatavalue.com/mcp`. Transport: Streamable HTTP. Authentication: OAuth in the user's browser. No API key, client secret or local server installation is needed. ## Before you start - **The client.** The assistant's own environment usually shows which client is in use; the user is asked which app to connect only when it is unclear. Each client has its own native MCP setup: [Claude on the web or desktop](#claude-on-the-web-or-desktop), [Claude Code](#claude-code), [Codex](#codex) or [another assistant](#another-assistant). A web chat cannot edit the user's local configuration. - **An existing connection.** A myDataValue connection that already points to this server is reused. Unrelated configuration stays as it is, and a connection to a different server is replaced only after the user agrees. - **Who does what.** The assistant does the configuration steps its tools allow and guides the user through the rest. The user signs in, chooses the team and approves permissions in the browser, so setup never needs a password, authorization code or token pasted into chat. - **Two separate gates** can block setup, each with its own fix: - **Adding a connector** is decided by the assistant's own workspace (for Claude, see [Claude on the web or desktop](#claude-on-the-web-or-desktop)), never by myDataValue. - **Team access** is settled on the myDataValue consent screen shown after sign-in. It lists every team the signed-in account belongs to, with a start-trial button on a team that has no access yet and a Join link on a pending invitation (shown once the account's email address is confirmed). What the consent screen offers is the first thing to read when diagnosing. A team absent from it means the account is not a member: a team admin can invite that address, or the user can sign in with the account that is. The screen settles membership; it cannot restore access a team has used up. A team that already used its trial cannot regain access there, so if the team stays unselectable after using what the screen offers, the user's myDataValue contact has to restore access. ## Claude on the web or desktop myDataValue is listed in Claude's connector directory, which is the shortest route: 1. Open the [myDataValue listing](https://claude.ai/directory/mydatavalue) and click **Connect**. 2. The user signs in to myDataValue and approves the team on the consent screen. 3. Enable the connector in the conversation's tools, then [verify the connection](#verify-the-connection). On a Claude Team or Enterprise plan the workspace Owner controls which connectors members can use, so a member who cannot add myDataValue from the listing asks their Owner. If the listing is not available, a custom connector reaches the same server. ### Add a custom connector On a Claude Team or Enterprise plan only an Owner can add a custom connector, under **Organization settings → Connectors**. Members see no option to add one, and the prefilled link in step 1 does nothing for them. Such a user asks their Claude workspace Owner to add the connector with the name and URL in step 2, then continues from **Customize → Connectors** once it appears there. This is a Claude workspace setting that myDataValue cannot change, and it is not the [team access](#before-you-start) settled on the consent screen. 1. Open [Claude's connectors](https://claude.ai/customize/connectors) and add a custom connector. This [prefilled setup link](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=MyDataValue&connectorUrl=https%3A%2F%2Fapi.mydatavalue.com%2Fmcp) supplies the name and URL. 2. Use the name `MyDataValue` and URL `https://api.mydatavalue.com/mcp`. If an Authentication choice is shown, select **Always required / OAuth** rather than **None**. Leave optional client ID and client secret fields blank; myDataValue supports automatic client registration. 3. Connect and let the user complete myDataValue sign-in and consent. Enable the connector in the conversation's tools, then [verify the connection](#verify-the-connection). Remote connectors need a publicly reachable server. Claude's web and desktop connectors cannot reach a development server on the user's localhost. ## Claude Code A connector added to the user's Claude account from [Claude's connector directory](https://claude.ai/directory/mydatavalue) is also available in Claude Code when it is signed in with that account. Otherwise `claude mcp add` is the route. With terminal access, `claude mcp get mydatavalue` shows the existing entry. If there is none, this adds it: ```sh claude mcp add --transport http --scope user mydatavalue "https://api.mydatavalue.com/mcp" ``` The user then runs `/mcp` in Claude Code, selects `mydatavalue` and authenticates in the browser. If the tools are not yet available, reconnecting or starting a fresh session loads them; then [verify the connection](#verify-the-connection). ## Codex The current Codex client's MCP server settings show whether the server is configured, and so does `codex mcp list` with terminal access. If the `mydatavalue` server is absent, these commands add it and start the login: ```sh codex mcp add mydatavalue --url "https://api.mydatavalue.com/mcp" codex mcp login mydatavalue ``` The user completes the browser sign-in. An existing entry at the correct URL needs only the login, and only when it is unauthenticated. Restarting the MCP connection or starting a fresh Codex session loads the tools; then [verify the connection](#verify-the-connection). Without the CLI, a Streamable HTTP server named `mydatavalue` at `https://api.mydatavalue.com/mcp` is added in the client's MCP settings and authenticated there. The [official Codex MCP instructions](https://developers.openai.com/codex/mcp) cover a client that presents different controls. A hosted chat that cannot access the local configuration cannot change it. ## Another assistant Its official instructions for remote MCP with OAuth apply. A product that does not support adding a custom server cannot connect; a client with its own section here ([Claude](#claude-on-the-web-or-desktop), [Claude Code](#claude-code) or [Codex](#codex)) can. A local proxy or invented settings do not work around that limitation. ## Verify the connection Use the connected myDataValue tools to list the user's properties or listings. Show the result and identify the selected team when the tools provide it. An empty portfolio is a valid result: the connection works and the team has no properties yet. Saving the configuration, or seeing public market counts alone, does not show that the connection works. | What happens | What to check | | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | No account tools appear | That OAuth completed and the connector is enabled in this conversation. | | Claude shows only public market counts | The connection is unauthenticated: check its Authentication setting. A connector set to **None** that cannot be edited is removed and re-added with authentication enabled. | | The tools need a new session | The user starts one and asks "List my properties." | Setup ends once the connection is verified; it does not require changing prices, promotions or other account data. The connection is a standing consent. It lasts until it is revoked, with no periodic re-authorization, and it works while the signed-in user remains a member of that team and the team has access to myDataValue. A team whose Connections page shows **AI assistants** revokes it there; for any other team, its myDataValue contact revokes it. Client controls can change. When a step differs from the user's client, the official [Claude connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp), [Claude Code MCP guide](https://code.claude.com/docs/en/mcp) and [Codex MCP instructions](https://developers.openai.com/codex/mcp) are the reference.