Skip to main content
Glama
rhettlong

USCardForum MCP Server

by rhettlong

login

Authenticate to access USCardForum features like notifications, bookmarks, and subscriptions using your forum credentials with optional 2FA support.

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

  • The primary MCP tool handler for the 'login' tool. Defines input schema via Annotated Fields, comprehensive documentation, and delegates execution to the shared DiscourseClient instance.
    @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 defining the output schema for login results, including success status, username, error messages, and 2FA requirement.
    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)
  • Explicit import of the 'login' tool (line 38) along with all other server tools, which triggers registration via @mcp.tool() decorators when the server starts.
    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, providing a unified interface that delegates to AuthAPI.login().
    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
        )
  • Core AuthAPI.login() implementation handling HTTP POST to /session.json with CSRF token, 2FA support, and session state 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
        """
        token = self.fetch_csrf_token()
    
        data: dict[str, Any] = {
            "login": username,
            "password": password,
            "remember": remember_me,
        }
        if second_factor_token:
            data["second_factor_token"] = second_factor_token
    
        headers = {
            "Accept": "application/json",
            "Content-Type": "application/json",
            "Referer": f"{self._base_url}/login",
            "X-CSRF-Token": token,
            "X-Requested-With": "XMLHttpRequest",
        }
    
        payload = self._post("/session.json", json=data, headers=headers)
        result = LoginResult.from_api_response(payload, username)
    
        if result.success:
            # Verify session and get username
            session = self.get_current_session()
            if session.current_user:
                self._logged_in_username = session.current_user.username
            else:
                self._logged_in_username = username
    
        return result
Behavior5/5

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It excellently describes key behavioral traits: the session remains authenticated for subsequent calls, credentials are not persisted, it returns a structured LoginResult with specific fields, and it handles optional 2FA. This provides comprehensive behavioral context beyond basic functionality.

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?

The description is well-structured with clear sections (purpose, parameters, usage guidelines, return values, behavioral notes). While slightly longer than minimal, every sentence serves a purpose - no redundant information. The front-loading of the core purpose is effective.

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 that this is an authentication tool with no annotations but with comprehensive output schema (implied by the Returns section), the description provides complete context. It covers authentication scope, session persistence, security considerations, return structure, and usage guidelines - everything needed for an agent to understand and use this tool correctly.

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 100%, so the schema already documents all parameters thoroughly. The description repeats the parameter information in the Args section but doesn't add significant semantic value beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 identifies the resource (forum authentication). It distinguishes this tool from all sibling tools which are various read operations, making the purpose unambiguous and well-differentiated.

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?

The description provides explicit guidance on when to use this tool ('Only use this if you need authenticated features like: - Reading notifications - Bookmarking posts - Subscribing to topics') and when not to use it ('Most read operations work without authentication'). It effectively contrasts with sibling tools that don't require authentication.

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/rhettlong/uscardforum-mcp'

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