# Quickstart {#quickstart}


The intended clients are Codex CLI and Claude Code. These steps are not an installed-client acceptance record. Claude Code, and automatic login against the current read-only catalog, have not been accepted on the published service. The confirmed deployed Codex read used explicit read scopes on an earlier catalog. Do not treat these commands as proof that the URL-only flow works at `https://mcp.elova.dev/mcp`.

Claude Desktop, Cowork, and claude.ai connectors are not supported.

The intended flow has no API key and no client secret. The client is expected to open a browser so you can sign in with your existing Elova account and approve the connection there.


## Server address {#server-address}


The published server address is:

```text
https://mcp.elova.dev/mcp
```

**Your account → AI access** shows the MCP server address for the installation you are signed into. Use that address if it is different. The sign-in host for the published service is `https://auth.elova.dev` (realm `elova`). You do not type that host yourself. The client discovers it.

Confirm the installed commands before you rely on them:

```sh
codex --version
codex mcp add --help
claude --version
claude mcp add --help
```


## Codex CLI {#codex-cli}


Add the HTTP server:

```sh
codex mcp add elova --url https://mcp.elova.dev/mcp
```

Adding the server may open the browser immediately. If it does not, start sign-in:

```sh
codex mcp login elova
```


## Claude Code {#claude-code}


Add the HTTP server:

```sh
claude mcp add --transport http elova https://mcp.elova.dev/mcp
```

Open Claude Code's `/mcp` controls and authenticate Elova.


## Approve the connection {#approve-the-connection}


1. Sign in with the Elova account you already use, or confirm a recent session.
2. Review the client name. A name supplied by the client is not proof of who operates that client. Continue only for the connection you started.
3. Select 1–50 workspaces, at least one read permission, and an expiry of 1, 7, or 30 days.
4. Acknowledge that the client may process or retain the returned data.
5. Select **Allow {client name} access**. **Deny** cancels the connection.

Return to the client and request its tool list. The repository catalog has nine tools and no aliases for former names. That catalog is not yet a production-accepted release. A refresh asks the connected server what it currently offers. It does not deploy `0.3.0`. If the published service still serves an earlier list, refreshing cannot add the nine names.


## Try a read {#try-a-read}


These prompts are examples. They do not change anything.

- "Which workspaces can this connection read?"
- "List the n8n instances in the example workspace and tell me when execution collection last succeeded."
- "How many retained executions succeeded in the last 7 days in Europe/Berlin?"

The client must use the local workspace ID from `get_many_workspaces` or from Elova. A workspace name is a label, not a selector.


## Remove it later {#remove-it-later}


Open **Your account** from the account email in the sidebar. In **AI access → Connected clients**, select **Remove access** and confirm. Removal stops future reads. It does not delete data the client already received.

Signing out of the Elova browser does not remove a connection.