FunPay MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FUNPAY_PROXY | No | Proxy URL, e.g., socks5://localhost:1080 | |
| FUNPAY_LOCALE | No | Locale: ru, en, or uk | ru |
| FUNPAY_TIMEOUT | No | HTTP timeout in seconds | 15 |
| FUNPAY_GOLDEN_KEY | Yes | Value of the golden_key cookie (required) | |
| FUNPAY_USER_AGENT | No | User-Agent of the browser with an active FunPay session | Chrome 124 Linux |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_meD | – |
| get_userD | – |
| get_balanceD | – |
| get_chatsD | – |
| get_chat_historyD | – |
| send_messageD | – |
| get_salesD | – |
| get_orderD | – |
| refundD | – |
| get_my_lotsD | – |
| get_lot_fieldsD | – |
| save_lotD | – |
| delete_lotD | – |
| get_categoriesD | – |
| get_subcategoriesD | – |
| raise_lotsD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Most tools are clearly distinct, such as get_me vs get_user and get_chats vs get_chat_history. However, get_sales and get_order could be confused since both relate to transactions, and get_my_lots vs get_lot_fields might be ambiguous without clear descriptions.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., get_balance, send_message, delete_lot). Even exceptions like refund and raise_lots still adhere to the pattern, creating a predictable and uniform naming scheme.
With 16 tools, the server is slightly above the ideal 3-15 range, but the breadth is justified by the need to cover user, order, lot, chat, and category management. No tools feel redundant, and the count is not overwhelming.
The toolset covers core marketplace workflows well: user profiles, balance, refunds, sales/orders, lot CRUD (save/delete/get), and categories. Missing operations like explicit lot search or order creation are minor gaps, as buyers would normally initiate these actions.