Skip to main content
Glama
hmumixaM

USCardForum MCP Server

by hmumixaM

login

Authenticate with USCardForum to access member-only features like reading notifications, bookmarking posts, and subscribing to topics. Supports optional two-factor authentication for account security.

Instructions

Authenticate with USCardForum credentials.

Args:
    username: Your forum username
    password: Your forum password
    second_factor_token: 2FA code if you have 2FA enabled (optional)

IMPORTANT: Only use this if you need authenticated features like:
- Reading notifications
- Bookmarking posts
- Subscribing to topics

Most read operations work without authentication.

Returns a LoginResult with:
- success: Whether login succeeded
- username: Logged-in username
- error: Error message if failed
- requires_2fa: Whether 2FA is required

The session remains authenticated for subsequent calls.

Security note: Credentials are used only for this session
and are not persisted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesYour forum username
passwordYesYour forum password
second_factor_tokenNo2FA code if you have 2FA enabled

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if failed
successYesWhether login succeeded
usernameNoLogged-in username
requires_2faNoWhether 2FA is required

Implementation Reference

  • MCP tool handler for 'login'. Decorated with @mcp.tool(), defines input schema via Annotated Fields, calls DiscourseClient.login, returns LoginResult.
    @mcp.tool()
    def login(
        username: Annotated[
            str,
            Field(description="Your forum username"),
        ],
        password: Annotated[
            str,
            Field(description="Your forum password"),
        ],
        second_factor_token: Annotated[
            str | None,
            Field(default=None, description="2FA code if you have 2FA enabled"),
        ] = None,
    ) -> LoginResult:
        """
        Authenticate with USCardForum credentials.
    
        Args:
            username: Your forum username
            password: Your forum password
            second_factor_token: 2FA code if you have 2FA enabled (optional)
    
        IMPORTANT: Only use this if you need authenticated features like:
        - Reading notifications
        - Bookmarking posts
        - Subscribing to topics
    
        Most read operations work without authentication.
    
        Returns a LoginResult with:
        - success: Whether login succeeded
        - username: Logged-in username
        - error: Error message if failed
        - requires_2fa: Whether 2FA is required
    
        The session remains authenticated for subsequent calls.
    
        Security note: Credentials are used only for this session
        and are not persisted.
        """
        return get_client().login(
            username, password, second_factor_token=second_factor_token
        )
  • Pydantic model for LoginResult, used as output type for the login tool. Includes fields for success status, username, error, 2FA requirement, and factory method from API response.
    class LoginResult(BaseModel):
        """Result of a login attempt."""
    
        success: bool = Field(..., description="Whether login succeeded")
        username: str | None = Field(None, description="Logged-in username")
        error: str | None = Field(None, description="Error message if failed")
        requires_2fa: bool = Field(False, description="Whether 2FA is required")
    
        class Config:
            extra = "ignore"
    
        @classmethod
        def from_api_response(
            cls, data: dict[str, Any], username: str
        ) -> "LoginResult":
            """Parse from raw API response."""
            if "error" in data:
                return cls(success=False, error=data["error"])
            if data.get("second_factor_required"):
                return cls(success=False, requires_2fa=True, username=username)
            return cls(success=True, username=username)
  • Imports all server tools including 'login' from server_tools modules. Importing the decorated functions registers them with the global mcp instance from server_core.py.
    from uscardforum.server_tools import (
        analyze_user,
        bookmark_post,
        compare_cards,
        find_data_points,
        get_all_topic_posts,
        get_categories,
        get_current_session,
        get_hot_topics,
        get_new_topics,
        get_notifications,
        get_top_topics,
        get_topic_info,
        get_topic_posts,
        get_user_actions,
        get_user_badges,
        get_user_followers,
        get_user_following,
        get_user_reactions,
        get_user_replies,
        get_user_summary,
        get_user_topics,
        list_users_with_badge,
        login,
        research_topic,
        resource_categories,
        resource_hot_topics,
        resource_new_topics,
        search_forum,
        subscribe_topic,
    )
  • DiscourseClient.login method called by the tool handler. Delegates to AuthAPI.login for the actual HTTP request and session management.
    def login(
        self,
        username: str,
        password: str,
        second_factor_token: str | None = None,
        remember_me: bool = True,
    ) -> LoginResult:
        """Login to the forum.
    
        Args:
            username: Forum username
            password: Forum password
            second_factor_token: Optional 2FA token
            remember_me: Remember session (default: True)
    
        Returns:
            Login result with success status
        """
        return self._auth.login(
            username, password, second_factor_token=second_factor_token, remember_me=remember_me
        )
  • Imports global mcp for tool decorator and get_client() which provides the shared DiscourseClient instance.
    from uscardforum.server_core import get_client, mcp
    
    
    @mcp.tool()
    def login(
        username: Annotated[
            str,
            Field(description="Your forum username"),
        ],
        password: Annotated[
            str,
            Field(description="Your forum password"),
        ],
        second_factor_token: Annotated[
            str | None,
            Field(default=None, description="2FA code if you have 2FA enabled"),
        ] = None,
    ) -> LoginResult:
        """
        Authenticate with USCardForum credentials.
    
        Args:
            username: Your forum username
            password: Your forum password
            second_factor_token: 2FA code if you have 2FA enabled (optional)
    
        IMPORTANT: Only use this if you need authenticated features like:
        - Reading notifications
        - Bookmarking posts
        - Subscribing to topics
    
        Most read operations work without authentication.
    
        Returns a LoginResult with:
        - success: Whether login succeeded
        - username: Logged-in username
        - error: Error message if failed
        - requires_2fa: Whether 2FA is required
    
        The session remains authenticated for subsequent calls.
    
        Security note: Credentials are used only for this session
        and are not persisted.
        """
        return get_client().login(
            username, password, second_factor_token=second_factor_token
        )
Behavior5/5

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

With no annotations provided, the description carries full burden and delivers comprehensive behavioral information. It explains the session persistence ('The session remains authenticated for subsequent calls'), security handling ('Credentials are used only for this session and are not persisted'), return structure details, and authentication requirements including optional 2FA.

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

Conciseness4/5

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

Well-structured with clear sections (purpose, args, usage guidelines, returns, behavioral notes). Every sentence adds value, though the bulleted lists could be slightly more concise. The information is front-loaded with the core authentication purpose stated immediately.

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

Completeness5/5

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

Given this is a critical authentication tool with no annotations but with output schema, the description provides complete context. It covers purpose, parameters, usage scenarios, return values, session behavior, and security considerations - everything needed to understand and use this tool effectively.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful context by explaining the optional nature of second_factor_token ('if you have 2FA enabled') and grouping all parameters under an 'Args:' section, which provides organizational value beyond the schema's individual parameter descriptions.

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

Purpose5/5

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

The description clearly states the specific action ('Authenticate with USCardForum credentials') and resource ('credentials'), distinguishing it from all sibling tools which are various read operations. It establishes this as the authentication entry point for the forum system.

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

Usage Guidelines5/5

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

Explicitly states when to use ('if you need authenticated features like: Reading notifications, Bookmarking posts, Subscribing to topics') and when not to use ('Most read operations work without authentication'). Provides clear alternatives by naming specific sibling tools that require authentication versus those that don't.

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/hmumixaM/uscardforum-mcp4'

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