Connect your agent to Flick

For AI agents

Everything an agent needs is in this block.

Flick remote MCP server (Streamable HTTP): https://api.joinflick.co/mcp

Auth, pick one
1. OAuth. Add the URL above as a remote MCP server or custom connector in
   your host app. A browser sign in prompt appears for the human.
2. Agent API key. Ask a Flick workspace admin to create one in Flick under
   Settings then Agents. Send it on every request as
   Authorization: Bearer fk_...
3. No Flick account yet. You can sign your user up yourself:
   POST https://api.joinflick.co/api/agent-signup with {"email": ...},
   ask your user for the 6 digit code from their inbox, then
   POST https://api.joinflick.co/api/agent-signup/verify with
   {"email": ..., "code": ...}. The response contains your api_key,
   trial credits are granted, and next_steps walks you through onboarding.

Read tools: flick_get_workspace_status, flick_list_accounts,
flick_list_research_findings, flick_get_account_brief,
flick_list_manual_leads, flick_list_plays
Write tool: flick_add_manual_leads (needs the flick.leads.write scope,
adds leads by LinkedIn profile URL, spends workspace credits)

Suggested first calls: initialize, then tools/list, then
flick_list_accounts, then flick_list_research_findings for one account.
Machine readable map: https://joinflick.co/llms.txt
Technical reference: https://api.joinflick.co/docs

Interactive agents

Claude, ChatGPT, Cursor, and any other MCP client. Paste one URL and sign in.

Claude

Open claude.ai and go to Settings, then Connectors.
Choose Add custom connector and paste https://api.joinflick.co/mcp.
Sign in to Flick when the browser prompt appears.

ChatGPT

Open ChatGPT settings and go to Connectors.
Add a custom connector with https://api.joinflick.co/mcp.
Sign in to Flick when the browser prompt appears.

Cursor and other MCP clients

Any client that supports Streamable HTTP and OAuth works.

{
  "mcpServers": {
    "flick": { "url": "https://api.joinflick.co/mcp" }
  }
}

Claude Code and Codex

Your agent can run these itself.

claude mcp add --transport http flick https://api.joinflick.co/mcp

codex mcp add flick --url https://api.joinflick.co/mcp

Sign up through your agent

No Flick account yet. Your agent asks Flick to email you a code, you read the code back, and setup finishes with your trial credits ready.

POST https://api.joinflick.co/api/agent-signup
{"email": "you@company.com", "company_name": "Acme", "company_domain": "acme.com"}

A 6 digit code lands in your inbox. Tell it to your agent.

POST https://api.joinflick.co/api/agent-signup/verify
{"email": "you@company.com", "code": "123456"}

The response contains the agent api_key, your workspace, your trial
credits, and next_steps for onboarding. A sign in link for the
dashboard is in the same email.

Prefer doing it yourself? Start free in the app.

Headless agents

Scripts and scheduled jobs authenticate with an agent API key.

In Flick, open Settings, then Agents. Workspace admins can create keys.
Name the key and choose whether it can add leads. Read access is the default.
Copy the key when it appears. Flick shows it once and stores only a hash.

curl -s https://api.joinflick.co/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $FLICK_AGENT_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The same key also works against the JSON API at https://api.joinflick.co/api/*.

Quickstart prompt

Connect to the Flick MCP server and summarize the accounts with new research
findings this week. Cite the evidence for each finding.

Access and limits

Read tools return persisted projections that Flick already compiled for your workspace. Nothing your agent reads triggers providers or spends credits. The one write tool adds leads by LinkedIn profile URL. It sits behind a separate scope you grant per key and it spends workspace credits like a lead added in the app.