Skip to main content
Glama
mingovvv

tlc-portal-mcp

by mingovvv

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTAL_BASE_URLNo포탈 주소https://portal.example.internal
PORTAL_LOGIN_PATHNo로그인 진입 경로/login
PORTAL_TIMEOUT_SECONDSNoAPI 요청 타임아웃(초)15
PORTAL_MCP_SESSION_FILENo로컬 세션 저장 파일.portal-session.json
PORTAL_LOGIN_SUCCESS_URLNo로그인 성공 후 도달 URL/dashboard/landing

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
auth.loginC

브라우저를 열어 사용자가 직접 로그인하면 JWT를 자동 저장한다.

auth.import_vuexB

브라우저 localStorage['vuex'] 값을 붙여넣어 인증 상태를 가져온다.

auth.statusB

현재 인증 상태를 반환한다.

auth.clearA

저장된 인증 세션을 삭제한다.

leave.list_typesA

지원하는 휴가 유형 목록을 반환한다.

leave.get_balancesB

현재 잔여 휴가를 조회한다.

leave.list_requestsC

휴가 신청 내역을 조회한다.

leave.prepare_requestB

휴가 신청을 준비한다. 제출 전 확인 단계다.

leave.submit_prepared_requestB

준비된 휴가 신청을 포탈에 제출한다.

leave.cancel_requestB

기존 휴가 신청을 취소한다.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation4/5

Most tools target distinct resources and actions, especially within the leave namespace. The only possible confusion is between auth.login and auth.import_vuex, but their descriptions clearly separate browser-based login from importing an existing Vuex auth state.

Naming Consistency4/5

Tool names consistently follow a verb_noun pattern with clear namespace prefixes like auth and leave. auth.status is a minor deviation as a noun, but overall the naming is predictable and easy to navigate.

Tool Count5/5

Ten tools is a well-scoped size for a portal MCP server covering authentication and leave management. Each tool has a clear role, and the count feels neither bloated nor thin.

Completeness4/5

The leave workflow is well covered: types, balances, listing, preparing, submitting, and cancelling requests. Minor gaps include no direct request detail view or update/edit path, but cancel-and-recreate is a reasonable workaround.

Maintenance

ActivityInactive
ResponsivenessNo issues