Skip to main content
Glama

discord_login

Authenticate to Discord using a token to enable AI assistants to interact with Discord servers, channels, and messages through the MCP-Discord server.

Instructions

Logs in to Discord using the configured token

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenNo

Implementation Reference

  • The primary handler function for the 'discord_login' tool. Parses input args using DiscordLoginSchema, checks if already logged in, uses provided or existing token to login the Discord client, waits for 'ready' event using waitForReady helper, updates context, and returns success/error text response.
    export const loginHandler: ToolHandler = async (args, context) => {
      DiscordLoginSchema.parse(args);
      try {
        // Check if client is already logged in
        if (context.client.isReady()) {
          return {
            content: [
              {
                type: 'text',
                text: `Already logged in as: ${context.client.user?.tag}`,
              },
            ],
          };
        }
    
        // Use token from args if provided, otherwise fall back to the client's token
        const token = args.token || context.client.token;
    
        // Check if we have a token to use
        if (!token) {
          return {
            content: [
              {
                type: 'text',
                text: 'Discord token not provided and not configured. Cannot log in. Please check the following: 1. Provide a token in the login command or make sure the token is correctly set in your config or environment variables. 2. Ensure all required privileged intents (Message Content, Server Members, Presence) are enabled in the Discord Developer Portal for your bot application.',
              },
            ],
            isError: true,
          };
        }
    
        // If token is provided in args, update the client's token
        if (args.token) {
          context.client.token = args.token;
        }
    
        // Attempt to log in with the token and get the ready client
        const readyClient = await waitForReady(context.client, token);
        // Update the context client with the ready client
        context.client = readyClient;
        return {
          content: [
            {
              type: 'text',
              text: `Successfully logged in to Discord: ${context.client.user?.tag}`,
            },
          ],
        };
      } catch (err) {
        error(
          `Error in login handler: ${err instanceof Error ? err.message : String(err)}`
        );
        return handleDiscordError(err);
      }
    };
  • Zod schema defining the input for discord_login tool: optional 'token' string.
    export const DiscordLoginSchema = z.object({
      token: z.string().optional(),
    });
  • src/tool-list.ts:42-52 (registration)
    Tool registration entry in the exported toolList array, providing name, description, and inputSchema matching the Zod schema for MCP list_tools response.
    {
      name: 'discord_login',
      description: 'Logs in to Discord using the configured token',
      inputSchema: {
        type: 'object',
        properties: {
          token: { type: 'string' },
        },
        required: [],
      },
    },
  • Helper function used by the handler to login the client and wait for the 'ready' event with timeout handling, proper event listener cleanup, and error propagation.
    const waitForReady = async (
      client: Client,
      token: string,
      timeoutMs = 30_000
    ): Promise<Client> => {
      return await new Promise<Client>((resolve, reject) => {
        const timeout = setTimeout(() => {
          reject(new Error(`Client ready event timed out after ${timeoutMs}ms`));
        }, timeoutMs);
    
        if (client.isReady()) {
          clearTimeout(timeout);
          resolve(client);
          return;
        }
    
        const readyHandler = () => {
          info('Client ready event received');
          clearTimeout(timeout);
          client.removeListener('error', errorHandler);
          resolve(client);
        };
    
        const errorHandler = (err: Error) => {
          clearTimeout(timeout);
          client.removeListener('ready', readyHandler);
          reject(err);
        };
    
        client.once('ready', readyHandler);
        client.once('error', errorHandler);
    
        info('Starting login process and waiting for ready event');
        client.login(token).catch((err: Error) => {
          clearTimeout(timeout);
          client.removeListener('ready', readyHandler);
          client.removeListener('error', errorHandler);
          reject(err);
        });
      });
    };
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions authentication via token but doesn't disclose behavioral traits like whether this establishes a session, what permissions the token needs, error handling for invalid tokens, rate limits, or what 'logged in' state enables. For an authentication tool with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple authentication tool and front-loads the core purpose immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of authentication (no annotations, no output schema, 0% schema coverage), the description is incomplete. It doesn't explain what successful login enables, return values, error conditions, or dependencies. For a tool that likely gates access to other Discord operations, this leaves critical gaps for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions 'token' as the authentication method, which aligns with the single parameter in the schema. However, it doesn't explain what format the token should be (e.g., bot token, user token), where to obtain it, or whether it's optional (schema shows required:[]). The description adds basic meaning but doesn't fully compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Logs in') and target ('to Discord'), specifying the authentication method ('using the configured token'). It distinguishes from siblings by focusing on authentication rather than message/channel operations. However, it doesn't explicitly differentiate from potential alternative login methods.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a token first), whether this should be called before other Discord operations, or what happens if already logged in. With many sibling tools for Discord operations, this is a significant gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IQAIcom/mcp-discord'

If you have feedback or need assistance with the MCP directory API, please join our Discord server