Manage your community with an AI agent

Connect Claude, Claude Code, Codex or another MCP agent to Guild, choose its permissions, and let it run your Discord, Telegram and web3 community.

You can manage a guild with an AI agent by connecting it to Guild's MCP server at https://mcp.guild.xyz/mcp. Claude, Claude Code, Codex, Cursor and other AI agents that support remote MCP servers can connect to it. Once it's connected, you can ask the agent in plain language to create roles, set requirements such as "holds 1 of our NFTs on Base", attach Discord roles, Telegram groups and points as rewards, edit pages, read analytics and moderate your guild's chat. The server is free on every plan and in beta. A connection manages one guild, only with the permissions you approve, and agents can't create or delete guilds.

What an agent can do

An agent works with the same building blocks you do in the admin panel: roles, requirements and rewards. With the right permissions it can:

  • create, edit and delete roles, their requirements and their rewards, including Discord role, Telegram, points, secret, NFT, form and voting rewards
  • build a progression path, where each role requires the one before it
  • create and edit pages, change their layout and role order, and choose who can see them
  • turn a page into a feed, announcements or a chat, post in it as you, and resolve reports or mute and ban members there
  • create, edit and archive quests, create a quest leaderboard and read its standings
  • create forms and review the submissions
  • read member analytics and the audit log
  • read point balances (Read member data) and grant or deduct points (Moderate members)
  • create proposals, edit your launch page and change referral settings

Connecting a Discord server or Telegram group for the first time means adding Guild's bot there, which an agent can't do for you. Add the first Discord or Telegram reward yourself in the admin panel (see Discord roles and Telegram groups). After that, the agent can use that server or group in other roles.

Connect your agent

You need a guild that you own or administer. If you don't have one yet, create it at /create: agents can't create guilds.

In your guild, choose Manage guild, then open Agents. Under Connect your AI assistant, pick your assistant and follow the two steps it shows:

  • Claude: in Claude, open Settings, then Connectors, add a custom connector with the link https://mcp.guild.xyz/mcp, then press Connect and sign in to Guild.
  • Claude Code: run claude mcp add --transport http guild https://mcp.guild.xyz/mcp, then type /mcp in Claude Code, choose guild and sign in.
  • Codex: add [mcp_servers.guild] with url = "https://mcp.guild.xyz/mcp" to ~/.codex/config.toml, then run codex mcp login guild.
  • Other: add the same link wherever your assistant connects to MCP servers, and sign in to Guild when it asks. This is the route for ChatGPT and any other assistant that supports remote MCP servers with OAuth sign-in.

Approve the connection

When you sign in from the agent, Guild opens a consent page on guild.xyz. It names the app asking for access and where it will return you. Guild may first ask for a second factor or a fresh sign-in.

  1. Under Permissions, tick what the agent may do:

    • Read guilds: read settings, pages, roles, requirements, rewards, forms, spaces, analytics and the audit log.
    • Manage guilds: change settings, pages, roles, requirements, rewards, forms and spaces, and post in the guild's spaces as you.
    • Read member data: read members, their timelines, form submissions and space conversations, which include personal data.
    • Moderate members: review form submissions and moderate spaces, which means resolving reports, muting and banning.

    The two member permissions are never ticked in advance, so you only grant them on purpose.

  2. Under Guild this app manages, pick one guild.

  3. Open Actions this app can never take if you want the full list, then press Connect app.

On the Agents page these permissions are shown as Read, Manage, Member data and Moderation.

Keep it safe

  • Grant the least you need. Read guilds alone is enough to have an agent review your roles and suggest changes. Add Manage guilds when you want it to make the changes.
  • Ask for a plan first. Try "Plan the roles for our holders, but don't create anything until I approve." Deleting a role takes it and its rewards away from members, so check any deletion first.
  • Check what it did. Changes to guild settings, roles, points and form reviews appear in the Audit log, marked as made by the agent for you. Changes to pages, requirements, reward settings, spaces and proposals aren't in the audit log yet.
  • Revoke when you're done. Connected agents on the Agents page lists every connection with its permissions, who made it and when it was last used. You can take permissions away from your own connections, or press Revoke. A revoked agent stops working within 15 seconds; the changes it already made stay.

Whatever you allow, an agent can never create or delete a guild, change its owner, admins, plan or verification, manage API keys or agent connections, vote, join or leave guilds, fill in forms, or claim roles or complete quests for you. It also stops working in a guild if you stop being an owner or admin there.

Frequently asked questions

Which AI assistants work with Guild?

Claude, Claude Code and Codex have their own steps on the Agents page. ChatGPT, Cursor and other agents that support remote MCP servers with OAuth sign-in use the same link.

Does it cost anything?

No. The Guild MCP server is free on every plan, including Free. An agent still works within your plan: member analytics, for example, need Pro. The server is separate from the REST API, whose keys need the Pro plan; see Plans.

Can one agent manage several guilds?

A connection manages exactly the guild you picked when you approved it, and that can't be changed later. To manage another guild, connect the agent again and pick that guild.

Can the agent see my members' personal data?

Only if you tick Read member data when you approve it. Without it, the agent can still read analytics and the audit log, but not individual members, their form submissions or space conversations.

Can I use it from a script or CI, without a browser?

Yes. On the Agents page, open For developers and press Access token. Name it, pick its permissions and an expiry of 30, 90 or 365 days (90 at most with a member permission), then send it as a Bearer token to the server URL. The token works for that guild only and is shown once. See Agents for the full reference.

All Guild docs