Integration

Flock integration

Flock is a team messaging app (channels and direct messages). List the channels a user or bot belongs to, read a channel and its members with their public profiles, read the token owner's user profile or any user's public profile, and send a plain-text or FlockML message to a user or a channel. Creating channels, adding or removing members, fetching messages, contacts, and message attachments, mentions or custom sender names are not exposed. Authentication is a Flock token sent as the token query parameter: a bot token from the Flock developer dashboard, or a user token received when the user installs your app.

Connect Flock How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Flock.Built from the 6 Flock tools below, on the connection you add once.

What you can do with Flock

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Channel, 2 operations

get_channelGet channelGETGets one channel: id, name, member count and profile image. Fails with UnknownChannel when the channel cannot be found.
list_channelsList channelsGETLists the channels (groups) the token's user or bot is a member of: id, name, member count and profile image. Use a channel id with list_channel_members, get_channel or send_message.

Channel member, 1 operation

list_channel_membersList channel membersGETLists the members of a channel with their role (moderator or member), and their public profile (name, image) when showPublicProfile is true.

Message, 1 operation

send_messageSend messageGETPosts a real message, seen at once, to a user (u:...) or a channel (g:...): plain text or FlockML rich text. A bot posting to a channel must set onBehalfOf. Returns the message uid.

User, 1 operation

get_user_infoGet user infoGETGets the user the token belongs to: id, team, email, name, role, timezone and profile image. Only works for users who installed your app; for other users use get_user_public_profile.

User profile, 1 operation

get_user_public_profileGet user public profileGETGets the public profile (first name, last name, profile image) of any Flock user, by user id.

Use Flock from Claude Code, Cursor or Codex

Connect Flock in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Flock operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Flock

Create your workspace
Sign up free. Nothing to install.
Connect Flock once
Add your Flock connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.