claude-desktop-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MODE | No | Mode of operation: full, gateway, or search. | full |
| MCP_LOG_FILE | No | If set, append structured JSONL events to this file. | |
| MCP_LOG_LEVEL | No | Log level: info or debug. | info |
| MCP_SERVER_NAME | No | Server name reported to the client. | claude-desktop-mcp |
| MCP_SEARCH_TOP_K | No | How many tools the search tool returns. | 5 |
| MCP_LIST_PAGE_SIZE | No | Max items per page for list operations. | 50 |
| MCP_SEARCH_TOOL_NAME | No | Name of the search tool. | x_amz_bedrock_agentcore_search |
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 |
|---|---|
| orders_list_ordersA | List customer orders, optionally filtered by customer or status, with pagination. |
| orders_get_orderA | Retrieve full details of a single customer order by its order ID, including line items, totals, status, and shipping. |
| orders_create_orderB | Create a new customer order from a list of product line items. |
| orders_update_orderA | Update mutable fields on an existing order such as shipping address or internal notes. |
| orders_cancel_orderA | Cancel an order that has not yet shipped. |
| orders_refund_orderB | Issue a full or partial refund against a paid order. |
| orders_track_orderA | Get the current shipment tracking status and carrier events for an order. |
| orders_search_ordersA | Search orders by free-text query across customer name, email, product, or order number. |
| orders_get_order_invoiceA | Fetch the invoice document and billing breakdown for an order. |
| users_list_usersB | List user accounts, optionally filtered by role or status. |
| users_get_userA | Retrieve a single user account by user ID. |
| users_create_userC | Create a new user account. |
| users_update_userB | Update profile fields on an existing user account. |
| users_delete_userA | Permanently delete a user account. |
| users_search_usersA | Search user accounts by name, email, or username. |
| users_get_user_profileA | Get the extended public profile for a user, including avatar and bio. |
| users_reset_user_passwordB | Trigger a password reset email for a user account. |
| users_set_user_roleB | Change the access role assigned to a user. |
| files_list_filesC | List files in a folder, optionally filtered by MIME type. |
| files_get_file_metadataA | Retrieve metadata for a file such as name, size, owner, and timestamps. |
| files_upload_fileB | Upload a new file from base64 content or a source URL. |
| files_download_fileA | Download the binary content of a file. |
| files_delete_fileB | Move a file to trash, or delete it permanently. |
| files_move_fileB | Move a file to a different folder. |
| files_copy_fileC | Create a copy of a file. |
| files_search_filesA | Search files by name or full-text content. |
| files_share_fileA | Create a shareable link or grant a user access to a file. |
| github_list_repositoriesA | List Git repositories for a user or organization. |
| github_get_repositoryA | Get details about a single Git repository. |
| github_create_issueB | Open a new issue on a repository. |
| github_list_issuesA | List issues on a repository, filtered by state. |
| github_get_issueA | Get a single issue by number. |
| github_create_pull_requestB | Open a pull request from a head branch into a base branch. |
| github_list_pull_requestsB | List pull requests on a repository. |
| github_merge_pull_requestB | Merge an open pull request. |
| github_list_commitsC | List commits on a branch. |
| github_get_commitA | Get details and diff stats for a single commit. |
| slack_send_messageB | Send a message to a Slack channel or user. |
| slack_list_channelsC | List Slack channels in the workspace. |
| slack_get_channelA | Get metadata for a single Slack channel. |
| slack_create_channelC | Create a new Slack channel. |
| slack_list_messagesB | List recent messages in a channel. |
| slack_set_statusA | Set the authenticated user's status text and emoji. |
| slack_upload_snippetB | Upload a text snippet or file to a channel. |
| slack_invite_userB | Invite a user to a channel. |
| weather_get_current_weatherB | Get current weather conditions for a location. |
| weather_get_forecastB | Get a multi-day weather forecast for a location. |
| weather_get_alertsA | Get active severe-weather alerts and warnings for a location. |
| weather_get_historical_weatherA | Get historical weather observations for a location on a past date. |
| weather_get_air_qualityA | Get the current air quality index and pollutant breakdown for a location. |
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 50 tools
Each tool has a distinct domain prefix and action-object pairing, making them clearly separable. Even within similar operations (e.g., users_set_user_role vs users_update_user), the intent is unambiguous.
All tools follow a consistent {domain}_{verb}_{object} naming convention in lowercase snake_case. Verbs like list, get, create, update, delete are used uniformly across domains.
With 50 tools spanning six different domains, the server is overloaded. While each domain is well-covered, the overall count exceeds what an agent can efficiently navigate and would be better split into separate servers.
Each domain provides comprehensive CRUD and lifecycle operations. Minor gaps exist, such as GitHub lacking a single-PR detail fetch or Slack lacking message deletion, but core workflows are fully supported.