# Connect Epovest to your agent

These are the official Epovest instructions for connecting an AI assistant to an Epovest account. They are published at https://epovest.com/docs/setup.md and served by Epovest itself, so you can re-read them from the source at any time.

Epovest is an AI visibility platform: it measures how AI assistants such as ChatGPT, Claude, Gemini, Perplexity, Mistral and Grok answer the questions a market asks about a business, and gives that business the levers to shape those answers. Once connected you get tools to create, start, read, update and pause trackers, read the credit balance, and prepare a top-up the person approves.

One server, one address:

```
https://mcp.epovest.com/mcp
```

Go to the section that matches the client you are running in, and complete its steps yourself: run the commands you can run rather than handing them over. The person's own part is signing in and approving the access.

## Claude Code

```
claude mcp add --transport http epovest https://mcp.epovest.com/mcp
```

Then tell the person to run `/mcp` and approve the access: they sign in to Epovest in the browser, once, and the connection is live.

## Codex

```
codex mcp add epovest --url https://mcp.epovest.com/mcp
codex mcp login epovest
```

## Cursor, GitHub Copilot, and other agents with an MCP config file

Add to `.cursor/mcp.json` (Cursor), `.vscode/mcp.json` (Copilot), or your agent's MCP config file, under `"mcpServers"`:

```json
"epovest": { "url": "https://mcp.epovest.com/mcp" }
```

## Windsurf

Add to `~/.codeium/windsurf/mcp_config.json` under `"mcpServers"`. The key here is `serverUrl`:

```json
"epovest": { "serverUrl": "https://mcp.epovest.com/mcp" }
```

## OpenCode

Add to `~/.config/opencode/opencode.jsonc` under `"mcp"`:

```json
"epovest": { "type": "remote", "url": "https://mcp.epovest.com/mcp", "enabled": true, "oauth": {} }
```

Then run:

```
opencode mcp auth epovest
```

## Chat assistants with a connector gallery, such as ChatGPT and claude.ai on the web

Here the connector is added in the assistant's own settings, so these three clicks are the person's. Give them the address and walk them through it:

1. Open the connector settings of the assistant.
2. Add a custom MCP connector with the server URL https://mcp.epovest.com/mcp.
3. Sign in to Epovest and approve the access.

## Your own code, and any client that takes a header

Use the same address with an API key in the header of every call:

```
Authorization: Bearer epo_...
```

The person creates the key in the app at https://app.epovest.com/account/api-keys. A client that speaks HTTP rather than MCP reaches the same surface through the REST API v1, base URL https://api.epovest.com/v1, with the same key.

## How the authorization works

The one-click path is OAuth 2.1, authorization code with PKCE, and the client registers itself: discovery starts from the unauthenticated response of https://mcp.epovest.com/mcp, the person signs in to Epovest and approves the access, once. The token carries the role that person holds in the account. They review their connected apps, and revoke any of them, in the app at https://app.epovest.com/account/api-keys.

The `epo_` API keys stay valid in parallel, for every client that takes a header.

## Once you are connected

Reload the agent so it picks up the new server, then call `list_trackers` and tell the person what came back: their trackers, and the state of each one. On an account that has no tracker yet, offer to set the first one up; the recipe is written out at https://epovest.com/docs/recipes.md.

## Reference

- Task recipes for an agent helping a person set up tracking and read results: https://epovest.com/docs/recipes.md
- Full reference of the REST API v1 and the MCP server, with every tool, error and example: https://epovest.com/docs/api.md
- The same connection guide written for the person, in six languages: https://epovest.com/en/connect-your-ai