Docs · AI assistants

Connect your AI assistant.

Hipsift includes an MCP server, so assistants like ChatGPT and Claude can find your data and run queries on it for you.

1. Sign in from ChatGPT or Claude

Add Hipsift as a connector with the address https://hipsift.com/mcp. Your assistant opens a Hipsift page where you sign in and choose what it can do: Read to ask questions, or Read and change to also add and refresh data, change schedules and transforms. No API key needed.

Claude

On claude.ai or in Claude Desktop, open Settings → Connectors, add a custom connector with the address https://hipsift.com/mcp, then connect and sign in to Hipsift. It then works in the Claude mobile apps too. If your organization manages Claude, an owner may need to add it first.

ChatGPT

In ChatGPT (on a paid plan), turn on developer mode in Settings, then create a connector with the address https://hipsift.com/mcp and OAuth sign-in, and sign in to Hipsift when asked.

Claude Code

Add the server, then run /mcp in Claude Code to sign in from your browser:

claude mcp add --transport http hipsift https://hipsift.com/mcp

Connected assistants are listed on the API Keys page, where you can disconnect one at any time. If you chose Read and later want changes, ChatGPT asks you to sign in again; in other assistants, disconnect and connect again, choosing Read and change.

2. Or use an API key

Sign in to Hipsift, open the API Keys page and create a key. It's shown once, so copy it somewhere safe. Pick read to ask questions. Pick write if you also want your assistant to add and refresh data, change schedules and transforms.

The server address is https://hipsift.com/mcp. Replace pfg_YOUR_API_KEY with your key.

Claude Code with a key

claude mcp add --transport http hipsift https://hipsift.com/mcp \
  --header "Authorization: Bearer pfg_YOUR_API_KEY"

Claude Desktop

Claude Desktop can also sign in as a connector (above). To use a key instead, it connects through mcp-remote, which needs Node.js. Add this to claude_desktop_config.json (Settings → Developer → Edit Config), then restart Claude.

{
  "mcpServers": {
    "hipsift": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://hipsift.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer pfg_YOUR_API_KEY"
      }
    }
  }
}

Cursor

Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project.

{
  "mcpServers": {
    "hipsift": {
      "url": "https://hipsift.com/mcp",
      "headers": {
        "Authorization": "Bearer pfg_YOUR_API_KEY"
      }
    }
  }
}

Any other MCP client

Use the Streamable HTTP transport with the URL https://hipsift.com/mcp. Clients that support MCP sign-in (OAuth) can sign in to Hipsift; otherwise send the header Authorization: Bearer pfg_YOUR_API_KEY.

3. Ask away

Try questions like:

“Which of my Hipsift sheets has my shop orders?”
“Total my orders by product and tell me the best seller.”
“Refresh my household budget once a day.”
“Find building permit data for Chicago and add it to Hipsift.”

What your assistant can do

Action	Access needed
Find your data List your sources, sheets and their columns, and check whether an import has finished.	`read`
Answer questions Run queries that filter, group and total your data, then explain the answer.	`read`
Browse Google Sheets See the Google spreadsheets you've picked in Hipsift, with their tabs and rows.	`read`
Explore open data Find public city and county data portals and search their datasets.	`read`
Add and refresh data Import a Google spreadsheet you've picked in Hipsift or an open-data dataset, or refresh a source now.	`write`
Keep data fresh Refresh a Google Sheets source every few hours, or stop refreshing it (Plus plan).	`write`
Clean up columns Apply a transform to a column, such as reading text as dollars or dates.	`write`

Imports run in the background. Your assistant checks their status and waits until the data is ready before querying it.

Troubleshooting

401: the key is wrong or was deleted, or the assistant was disconnected. Create a new key, or connect the assistant again.
403 insufficient_scope: the action needs a write key, or Read and change for an assistant that signed in.
403 paid_plan_required: scheduled refresh needs the Plus plan.
429 rate_limited: your assistant made too many requests in a minute. Wait a minute and ask again.
Use https://hipsift.com/mcp exactly, without www: assistants drop the key when they follow a redirect, and sign-in only works on that address.
To disconnect an assistant, disconnect it (or delete its key) on the API Keys page. It stops working straight away.

Prefer code? API keys also work with the Hipsift API.