Malt MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| authenticateA | Log in to Malt interactively. Opens a browser window to the Malt login page. The user must log in manually (email/password only -Google OAuth won't work). Waits up to 5 minutes, then the session is saved for future calls. |
| close_sessionA | Close the browser and free resources. Call this when you're done with Malt tools. The next tool call will reopen the browser automatically if needed. |
| get_profileB | Get a Malt freelance profile. |
| get_statisticsA | Get your Malt freelance statistics. Returns Super Malter points, visibility stats (favorites, search appearances, profile views), project reviews/rating, and keyword rankings. |
| get_missionsA | Get your Malt inbox: conversations and project offers. Returns a list of conversations and project offers sorted by date, with client name, company, last message, and status. |
| get_mission_detailsA | Get details of a specific mission conversation. Click on a conversation matching the given name and extract the project offer details: title, description, preferences, skills, and message history. |
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 6 tools
All six tools have clearly distinct purposes: authentication, session management, mission listing, mission details, profile retrieval, and statistics. No overlap or confusion.
Tool names follow a consistent pattern using lowercase and underscores. Verbs like 'authenticate' and 'close' are appropriately paired with nouns where needed (e.g., get_mission_details, get_missions).
With six tools, the set is well-scoped for a freelance platform. Each tool serves a necessary function without redundancy or bloat.
The tools cover the core user journey: login, browsing missions, viewing details, checking profile and stats. The set is complete for its intended read-oriented scope.