cogny clicommunityfirst 15 calls free

discord read from the shell.

List the guilds and channels your bot can see, read channel message history, enumerate members, and post messages — from Bash over the Discord MCP. Turn community chatter into JSON for sentiment and topic analysis.

1. sign up, free for the first calls (uses your git email)npx @cogny/cli init --agent claude-code
2. see every Discord toolcogny tools list
3. call any tool from bash, no MCP wiringcogny tools call mcp__Discord__list_guild_channels --input '{…}'

Start free @cogny/cli on npm

01two paths

you're a person

Skimming a busy Discord by hand to gauge what your community cares about is endless scrolling. The CLI pulls channel history as JSON so an agent can summarize themes, sentiment, and feature requests. Connect Discord once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.

Start Solo

you're an agent

Sign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Discord tool over JSON-RPC. The first 15 calls are free.

npx @cogny/cli init --agent claude-code

02tools call

real Discord tools.

Tool names as the Discord MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.

mcp__Discord__list_guild_channels

List the channels in a server.

cogny tools call mcp__Discord__list_guild_channels \ --input '{"guild_id":"1099900000000000000"}'

example response

[
  {
    "id": "1099900000000000010",
    "name": "general",
    "type": 0
  },
  {
    "id": "1099900000000000011",
    "name": "feature-requests",
    "type": 0
  },
  {
    "id": "1099900000000000012",
    "name": "support",
    "type": 0
  }
]

mcp__Discord__get_channel_messages

Read recent messages from a channel.

cogny tools call mcp__Discord__get_channel_messages \ --input '{"channel_id":"1099900000000000011","limit":2}'

example response

[
  {
    "id": "m901",
    "author": {
      "username": "devkat"
    },
    "content": "A CLI for the analytics MCP would be huge",
    "timestamp": "2026-06-15T18:22:00Z"
  },
  {
    "id": "m900",
    "author": {
      "username": "priya"
    },
    "content": "+1, want to script reports from cron",
    "timestamp": "2026-06-15T18:19:40Z"
  }
]

mcp__Discord__list_guild_members

Enumerate members (requires the members intent).

cogny tools call mcp__Discord__list_guild_members \ --input '{"guild_id":"1099900000000000000","limit":2}'

example response

[
  {
    "user": {
      "id": "5001",
      "username": "devkat"
    },
    "joined_at": "2026-01-04T09:00:00Z",
    "roles": [
      "contributor"
    ]
  },
  {
    "user": {
      "id": "5002",
      "username": "priya"
    },
    "joined_at": "2026-02-11T14:30:00Z",
    "roles": []
  }
]

03tools list

the rest of the surface.

A sample of the other Discord tools. Run cogny tools list --json for every tool and its input schema.

mcp__Discord__get_current_user
mcp__Discord__list_guilds
mcp__Discord__get_guild
mcp__Discord__get_channel
mcp__Discord__send_message

04then a verdict

calls from a script. verdicts from cogny.

Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.

worked
Moved the number. Every measured win has a share card.
partial
Some of it did.
didn't work
On the record anyway, so it isn't proposed again.
inconclusive
Not enough data to call.

How the loop works

05questions

questions.

Is this an official Discord CLI?: No — it is the Cogny CLI calling the Discord MCP over the cogny-mcp-proxy. You add a bot token once in Cogny; the CLI then reads guilds, channels, messages, and members from Bash. Discord Inc. is not affiliated.
What can the bot actually see?: Whatever the bot has access to. Reading a channel needs View Channel + Read Message History, and `list_guild_members` needs the privileged members intent enabled on the bot — same rules as any Discord bot.
Can it post, not just read?: Yes — `send_message` posts to a channel the bot can write to. The rest of the surface (guilds, channels, messages, members) is read tools for community analysis.

06related

Building an agent? The full tool map for every server is one fetch: /cli/llms.txt

discord, then a verdict.

Start free All CLIs