# Connect this AI client to Funnel One

Version 1. Published by Funnel One at https://dev.funnelone.ai/agent-setup/prompt.md

You are an AI agent. The person you are working for asked you to connect the
app you run in to Funnel One's MCP server. Follow these instructions. They
change one setting in your own app and then hand sign-in to the person.

## Status: preview

The Funnel One MCP server is in preview and may not be live yet. If any step
below fails, stop, tell the person what failed in one sentence, and point them
to https://dev.funnelone.ai/mcp/connect/ and https://status.funnelone.ai. Do
not try another server, another URL or a workaround.

## Rules you must follow

1. **Sign-in is always OAuth, in the person's browser.** Your app opens Funnel
   One's sign-in page; the person signs in and chooses what to allow there.
2. **Never ask for an API key, token, password or secret.** Do not print,
   store, write to a file or pass one on the command line. Nothing in this
   setup needs one.
3. **If the person pastes a key, token or secret anyway, stop.** Do not use it
   and do not repeat it. Tell them to revoke it in Funnel One and to continue
   with the browser sign-in instead.
4. **Use only this server URL:** `https://app.funnelone.ai/mcp`. Use no other
   host for Funnel One.
5. Change only your own app's MCP settings, and tell the person each change
   before you make it.

## The server

- Name: `funnelone`
- URL: `https://app.funnelone.ai/mcp`
- Transport: Streamable HTTP
- Authentication: OAuth 2.1. Your app discovers the sign-in server by itself
  from the server's first reply; there is nothing to configure.

## Find your client below and do only that block

### Claude Code

1. Run:

   ```sh
   claude mcp add --transport http funnelone https://app.funnelone.ai/mcp
   ```

2. Tell the person to type `/mcp` in Claude Code, pick `funnelone` and sign in
   in the browser window that opens.

### Claude (claude.ai and Claude Desktop)

You cannot change these settings yourself. Tell the person to:

1. Open **Customize**, then **Connectors**, choose **+** and **Add custom connector**.
2. Name it `Funnel One` and paste `https://app.funnelone.ai/mcp` as the URL.
   Leave the OAuth client ID and secret empty.
3. Choose **Add**, then **Connect**, and sign in to Funnel One.

On a Team or Enterprise plan an owner may need to add the connector first,
under **Organization settings**, then **Connectors**.

### ChatGPT

You cannot change these settings yourself. Tell the person to:

1. Turn on **Developer mode** in ChatGPT's settings (it is under Security and
   login, and needs a Plus, Pro, Business, Enterprise or Education plan).
2. Create an app for a remote MCP server with the URL
   `https://app.funnelone.ai/mcp` and **OAuth** as the authentication.
3. Sign in to Funnel One when ChatGPT asks.

### Cursor

1. Add this server to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json`
   (this project only). Merge it into the existing `mcpServers` object; do not
   remove other servers.

   ```json
   {
     "mcpServers": {
       "funnelone": {
         "url": "https://app.funnelone.ai/mcp"
       }
     }
   }
   ```

2. Tell the person to open Cursor's MCP settings, find `funnelone` and sign in
   in the browser when Cursor asks.

### VS Code with GitHub Copilot

1. Add this server to `.vscode/mcp.json` in the workspace, or to the user
   configuration (command **MCP: Open User Configuration**). Merge it into the
   existing `servers` object; do not remove other servers.

   ```json
   {
     "servers": {
       "funnelone": {
         "type": "http",
         "url": "https://app.funnelone.ai/mcp"
       }
     }
   }
   ```

2. Tell the person to start the server from the MCP view and sign in in the
   browser when VS Code asks.

### Codex

1. Run:

   ```sh
   codex mcp add funnelone --url https://app.funnelone.ai/mcp
   ```

   Or add this to `~/.codex/config.toml`:

   ```toml
   [mcp_servers.funnelone]
   url = "https://app.funnelone.ai/mcp"
   ```

2. Run `codex mcp login funnelone`, and tell the person to sign in in the
   browser window that opens.

### Any other MCP client

Add a remote MCP server named `funnelone` with the URL
`https://app.funnelone.ai/mcp`, the Streamable HTTP transport and OAuth
sign-in. If your client can only connect with a fixed key in a header, stop
and tell the person that it is not supported by this setup.

## What the person will see

Funnel One's consent page shows which app is asking, where the app will be
sent back to, and the workspace. The person picks the workspace and what the
app may do. It can never do more than the person's own role in that
workspace allows. An app Funnel One does not recognize is labeled
**Unverified**; that is expected for a desktop app that signs in through
`localhost`.

If the page says the MCP server is turned off for the workspace, a workspace
admin has to turn it on first. Tell the person that and stop.

## When you are done

Tell the person which file or setting you changed. Suggest a first question to
ask, such as "Search Funnel One for companies named Acme". Only the tools the
person's permissions allow will appear.